GB2536482A

GB2536482A - Emergency calling device

Info

Publication number: GB2536482A
Application number: GB1504678.2A
Authority: GB
Inventors: Naomi Eavis Alexandra; Alexandra Bowey Hellen; Tillett Marcus; Baker Simon
Original assignee: Alcove Ltd
Current assignee: Alcove Ltd
Priority date: 2015-03-19
Filing date: 2015-03-19
Publication date: 2016-09-21
Also published as: GB201504678D0

Abstract

A mobile communication device for connecting to a communication network, the device being arranged to make an outgoing call over a network only in response to the detection by the device of an extended user interaction with the device. In this way, the device may be arranged to make the outgoing call when it receives a prolonged interaction or a series of quick interactions. This may help avoid the outgoing call being made inadvertently. This may help minimise false alerts. Aspects of the invention include: the interaction comprises a single interaction for a length of time greater than a predetermined threshold time; the device is an emergency calling device; the device being constrained to call a single number; the device being arranged to provide feedback to a user in response to an interaction being detected; the device being arranged to change the feedback through at least a portion of the interaction; the device being arranged to automatically retry making the outgoing call until an outgoing connection can be made; the device being arranged to automatically answer the incoming call after a predetermined time period has elapsed after receiving the incoming call; the device being a watch.

Description

EMERGENCY CALLING DEVICE

This invention relates to mobile communication devices. In particular the invention relates to mobile communication devices for use as emergency calling devices.

In some circumstances it is useful, or perhaps necessary, to provide care for vulnerable people. This may be provided at a care home, or by a care worker visiting a person at their own home. In these cases, the care worker will visit periodically to check on the person. Conventionally, a person may also seek assistance from a care worker by using an assistance system (commonly known under the umbrella term of telecare).

A conventional telecare system comprises a pendant with a button and a base unit. 15 The pendant is often worn on a cord around a person's neck. The base unit will typically be fixed to a wall within the person's home. The base unit is connected to the home telephone line. When the button on the pendant is pressed, the pendant tells the base unit to call an emergency number via the home telephone line. This might be the number of a monitoring centre, manned by call centre operators.

The base unit has a speaker and microphone allowing the operator to speak with the person wearing the pendant. The operator can assess the situation and arrange a home visit if necessary.

The pendant/base unit will operate with a given range, allowing the person some freedom of movement away from the base unit. However, when the pendant button is pressed, the person may not be close enough to the base unit to be able to hear the operator, or to speak to them. This may distress the person. A care worker may then be sent to the person's home to check on them.

There is a need for an improved assistance system.

According to a first aspect of the present invention, there is provided a mobile communication device for connecting to a communication network, the device being arranged to make an outgoing call over the network only in response to the detection by the device of an extended user interaction with the device.

The extended user interaction may be such that the device can distinguish an inadvertent or accidental interaction from a deliberate interaction.

The extended user interaction may be a single interaction for a length of time greater than a predetermined threshold time. The extended user interaction may be multiple interactions, such as a series of interactions, over a length of time greater than a predetermined threshold time and/or with less than a predetermined threshold time between the interactions.

The device may be arranged to take no action in response to interactions which are not extended user interactions. In other words, the device may be arranged so that it will not make the outgoing call when it detects an interaction which is not an extended user interaction. To put it another way, the device may be arranged so that no outgoing call is made until the device detects the extended user interaction.

In this way, the device may be arranged to make the outgoing call when it receives a prolonged interaction or a series of quick interactions. The device may be arranged to ignore a single short interaction such that no outgoing call is made. This may help avoid the outgoing call being made inadvertently. This may help minimise false alerts.

The device may be an emergency calling device. The emergency calling device may be for use as part of an assistance system, for example for a vulnerable person to seek help or assistance. Thus, avoiding inadvertent calls being made with the device may help reduce or minimise demands put on monitoring and response time and/or care worker time.

The device may be constrained so as to be capable of calling only one number, for example an emergency number. The emergency number may connect to a monitoring centre staffed by care workers. In other words, the device may be restricted to only making an outgoing call to a single number. The device may be configured so that the number that is called cannot be designated by means of the user interface of the device.

The device may comprise an interface for receiving the user interaction. The user interaction may be receivable by the interface over at least a portion of the interface.

The device may comprise a touch-sensitive portion, for example a touch screen. Suitably, the interface may comprise the touch-sensitive portion. Suitably, the touch-sensitive portion is arranged to respond to surface contact.

Suitably the touch-sensitive portion is one of a resistive touch screen and a capacitive touch screen. The capacitive touch screen may allow the device to detect an interaction such as an extended user interaction which might not be detected by a resistive touch screen. Thus the capacitive touch screen may enable the detection of an interaction that requires less force and/or manual dexterity to apply. Suitably the touch-sensitive portion may enable the detection of an interaction that requires less force and/or manual dexterity to apply than a conventional pendant button.

The device may be arranged to detect an interaction by a user in response to the user interacting with a predetermined portion of the interface. The predetermined portion of the interface may be a portion of the touch-sensitive portion. The predetermined portion may be visually different from the remainder of the interface. For example, the predetermined portion may be configured as a portion of the interface with a high contrast to the remainder of the interface.

The predetermined portion may be at least 20% of the area of the interface, preferably at least 30% of the area of the interface, and more preferably at least 40% of the area of the interface. The predetermined portion may be at least 50% of the area of the interface. The predetermined portion may be substantially all of the area of the interface. In other words, the device may be arranged to detect the extended interaction in response to receiving an interaction by substantially any portion of the interface. The predetermined portion may be designated by a visual and/or tactile marker. The predetermined portion may be an area of a touch-sensitive display of the device, in which case the visual marker may be displayed on the touch-sensitive display. The device may be configured so that the visual marker changes in appearance, for example in colour and/or size whilst a user makes continual contact with the predetermined portion. The predetermined portion may be presented at different locations on the device at different times.

The device may be arranged to provide feedback to a user when an interaction is detected. The feedback may be one or more of visual, tactile and audible. For example, the device might do at least one of the following: light up, flash, vibrate and make a noise. The feedback may be configurable, for example by a user.

The device may be arranged to provide the feedback during at least a portion of the interaction. Suitably the device may be arranged to provide the feedback for the duration of the interaction. The feedback may be one of continuous and intermittent.

The feedback may change through at least a portion of the interaction. The change may be progressive. This may inform a user that the device has detected the interaction, and that it continues to detect the interaction.

Suitably, the feedback may be progressive at least until the device detects the 20 extended user interaction. Suitably the feedback may change on detection of an extended user interaction. This may inform a user that the device has detected an extended user interaction.

According to a second aspect of the present invention, there is provided a mobile communication device for connecting to a communication network, the device being arranged to make an outgoing call over the network, and the device being arranged to automatically retry making the outgoing call until an outgoing connection can be made.

According to a third aspect of the present invention, there is provided a mobile communication device for connecting to a communication network, the device being arranged to make an outgoing call over the network, and the device being arranged to automatically retry making the outgoing call until at least one of a time limit and a retry limit is reached.

S

The device may be arranged to retry making the outgoing call without making a user aware that it is retrying to make the outgoing call and/or without the user initiating the retrying.

The device may be arranged to detect a dropped call and in response to automatically try to reconnect the dropped call. In other words, the device may be arranged to distinguish a dropped call, for example where a connected call is lost, from a call that is terminated, for example where a call is deliberately ended such as by one party to the call. Suitably the device may be arranged to continue trying to reconnect the dropped call until the call can be reconnected. The device may be configured to, when it is engaged in a call that it has initiated and it detects that that call has been dropped, automatically re-establish a call to the same endpoint.

According to a fourth aspect of the present invention, there is provided a mobile communication device for connecting to a communication network, the device being arranged to receive an incoming call over the network, and the device being arranged to automatically answer the incoming call.

In other words, the device may be arranged to answer the incoming call without requiring any interaction by a user with the device. This can mean that the device is arranged to automatically enable a microphone and/or a speaker on the device. This can allow voice communication, such as two-way voice communication, to be made using the device.

Suitably, the device may be arranged to automatically answer the incoming call after a predetermined time period has elapsed after receiving the incoming call. The predetermined time period may be configurable, for example by a user.

Suitably the device may be arranged to provide a notification to a user of an incoming call before the call is automatically answered. In other words, the notification may be provided during at least a portion of the predetermined time period. Suitably the device may be arranged to provide the notification to a user of the incoming call for the duration of the predetermined time period. The notification may be one of continuous and intermittent.

The notification may be one or more of visual, tactile and audible. For example, the device might do at least one of the following: light up, flash, vibrate and make a noise. The notification may be configurable, for example by a user.

The device may be arranged to accept an incoming call from a particular number where a permissions list authorises that particular number. The device may be arranged to reject an incoming call from another number where the permissions list does not authorise that other number. The permissions list may authorise a number where the permissions list comprises that number. Suitably, the device may comprise the permissions list.

The device may be arranged to accept an incoming call where the incoming call comprises a permission portion. The device may be arranged to accept the incoming call in response to the permission portion. The permission portion may comprise an access code. In other words, the device may be arranged to allow connection of incoming calls from any number, where the incoming call comprises the permission portion. This may allow a person to call the device from a number that is not typically used, and/or may not, for example, be authorised by the permissions list.

The behaviour of the device may be configurable in dependence on the number from which the incoming call is received. In other words, the device may be arranged to adapt its behaviour for incoming calls from different numbers.

The device may comprise one or more profiles arranged to configure the device. The profile may be linked to a number from which an incoming call can be made. The profile may be configurable, for example by a user.

The incoming call may comprise an instruction to the device which is arranged to configure the device. That is to say, the device may be configurable in response to an instruction received by the device as part of an incoming call.

Thus, the device may be arranged to alter its behaviour based on the number from which an incoming call is received, and/or based on an instruction received as part of the incoming call.

The device may be arranged so that a call cannot be disconnected by the interface of the device. Here, the call may be at least one of an incoming call and an outgoing call. The device may be arranged so that an incoming call from a first number cannot be disconnected by the interface. This may prevent the disconnection of an emergency call.

The device may be arranged so that an incoming call from the first number is automatically answered by the device. This may allow an emergency call to always be answered.

The device may be arranged so that an incoming call from a second number is answered in response to the device detecting an answer interaction by a user. The answer interaction may be pressing an answer button on the device, such as an answer button on the interface.

The device may be arranged so that an incoming call from the second number can be disconnected in response to the device detecting a disconnection interaction by a user. The disconnection interaction may be pressing a disconnection button on the device, such as a disconnection button on the interface.

At least a portion of the interface may comprise at least one of the answer and disconnection buttons. The answer and disconnection buttons may be the same portion of the interface. Suitably the touch-sensitive portion may comprise at least one of the answer and disconnection buttons. At least one of the answer and disconnection buttons may be visually different from the remainder of the interface.

The device may be arranged so that the predetermined portion of the interface is always able to receive a user interaction. In this way, the device is always able to detect an extended user interaction and, for example, make an emergency call.

The device may be arranged to communicate regularly with a remote device. The remote device may be a server. The regular communications may be sent at regular time intervals, for example once every 5 minutes. Suitably the time interval may be configurable.

The device may be arranged to send information as part of the regular communications. The information may comprise the status of a battery of the device. The information may comprise data from one or more other element of the device, such as GPS data, accelerometer data and so on.

The device may be arranged to display reminders. The reminders may be displayed on the interface. The reminders may comprise one or more of text and images. The device may be arranged to dismiss the reminders on detection of an interaction by a user.

The device may be arranged to log one or more of the time, duration and number of any incoming and outgoing calls. The device may be arranged to log one or more of the time a reminder is received by the device and/or displayed on the device and the time a reminder is acknowledged by a user.

The device may be provided as a personal item, such as an item of jewellery. The device may be provided as a watch, such as a wristwatch. In this way, the device can be provided as an item that a person would normally carry with them. The device may have functionality additional to its communication functionality. For example, where the device is a watch, it may be arranged to keep and tell the time.

According to a fifth aspect of the present invention, there is provided an emergency calling system comprising the mobile communication device according to any aspect above and a remote device. The remote device may be a server.

The server may comprise the permissions list. The server may comprise the one or more profiles arranged to configure the device. The server may be arranged to receive the regular communications from the device. The server may be arranged to log these regular communications. The server may be arranged to issue an instruction in response to information in the regular communications. For example, where the information comprises a low device battery indication, the instruction may be for a care worker to visit the person to ensure that the battery is recharged.

The server may be arranged to send the reminders to the device. The server may be arranged to log one or more of the time, duration and number of any incoming and outgoing calls made using the device. The server may be arranged to log one or more of the time a reminder is received by the device and the time a reminder is acknowledged by a user.

According to a sixth aspect of the present invention, there is provided a method of making an outgoing call over a communication network from a mobile communication device for connecting to the network, the method comprising the steps of: detecting an interaction with the device; determining whether the interaction is an extended user interaction; and only in response to determining that the interaction is an extended user interaction, making an outgoing call over the network.

The step of determining whether the interaction is an extended interaction may comprise determining a duration of the interaction. The interaction may be determined to be an extended interaction when the duration exceeds a predetermined threshold duration.

As part of the step of determining the duration of the interaction, the method may comprise the step of starting a time count in response to the detected interaction. The time count may be compared to a clock signal. The clock signal may be obtained from one of the device, the communication network and a remote device.

Any one or more feature of any aspect above may be combined with any one or more feature of any other aspect above. Any apparatus feature may be rewritten as a method feature, with the necessary changes being made in the wording. These have not been written out in full here merely for the sake of brevity.

The present invention will now be described by way of example with reference to the accompanying drawings. In the drawings: Figure la shows an example of a mobile communication device; Figure 1 b shows an example of an interface of a mobile communication device; Figure 2a shows an example process of making an outgoing call; Figures 2b and 2c show examples of changes in an interface of a mobile communication device; Figures 3a and 3b show other example processes of making an outgoing call; Figure 4 shows an example process of receiving an incoming call; Figure 5 shows an example process of disconnecting a call; and Figure 6 shows an example process of notifying a user of a reminder.

A mobile communication device, such as an emergency calling device, can be provided as part of an assistance system, for example a telecare system. In such a system, a vulnerable person can carry the mobile communication device with them, allowing them freedom of movement whilst retaining the ability to call for help when needed. Such freedom of movement can enhance the person's independence and/or quality of life.

A mobile communication device 100 is shown schematically in figure 1. The device comprises an interface 102. In this embodiment the interface 102 comprises a capacitive touch-sensitive screen for displaying images and receiving touch inputs or interactions. The interface comprises a display portion 104 for displaying images and an input portion 106 for receiving interactions. It will be understood that these areas may be one of separated, contiguous, overlapping or coexisting.

The device 100 comprises a motor 108 for generating vibrations. The device comprises a speaker 110 and a microphone 112 for voice communication, such as two-way voice communication. The device further comprises communications modules (not shown) for making and receiving calls over a communications network, such as a mobile telecommunications network, for example a cellular telephone network.

A call means a communication over the communication network between the device and another apparatus. The call may comprise a voice call, such as a two-way voice call. The call may comprise data transmission. The call may use circuit switching. The call may use packet switching.

In one example, the device enables calls to be made and received over a cellular network.

In this way, the device 100 enables a person to make and receive calls directly. An advantage of the device 100 over a conventional pendant is that it is the device 100 itself that can make and receive the calls, rather than simply instructing another device (i.e. the fixed base unit) to do this. Thus the device 100 provides a much greater flexibility of movement than the pendant, and the assistance available is not restricted to a person's home. The device 100 allows a person to engage in a voice call whether they are inside or outside their home. The device 100 enables a call such as a voice call to be much clearer. As an example, this may be because the user will be close to the device 100 since it can be worn on the wrist as a wristwatch. Thus the user would be much closer to the device 100 than they would typically be to the fixed base unit of a conventional system.

The device 100 may be, or may form part of, a watch. This means that the device can be carried unobtrusively. This may be important to a person who does not want others to know that they are carrying an emergency calling device. In one embodiment the watch is a smart watch, comprising a touch-screen interface. In one example, the smart watch comprises a SIM card to enable it to connect to a cellular network.

Referring to figure 1 b, in one arrangement the interface 102 comprises a button 114. The button 114 is always present on the interface, so that assistance can be sought by the person at any time, quickly and easily; assistance can be sought without having to navigate through a series of commands. In one example, the device 100 has a restricted functionality such that, for example, since there is no need for other options and/or commands to be available to a user, the button 114 remains present and the device 100 does not allow navigation away from the button 114. The button 114 is visibly highly contrasting with the remainder of the interface 102, for example the button 114 is a large red button. This ensures that it can easily be located by a user. The button 114 comprises text (here "Help") to further identify the button 114.

The button 114 is located at a predetermined portion of the interface 102. Interacting with this predetermined portion of the interface 102 is associated with pressing the button 114.

In some embodiments the person may wish the device 100 to be more discreet. In these cases the button 114 may not be visibly present on the interface 102.

However, the predetermined portion of the interface 102 is always present. This means that assistance can be sought by interacting with the predetermined portion whether or not the button 114 is visible. The device 100 may be arranged so that even if one of a 'sleep' mode and a screensaver is enabled, the predetermined portion is able to receive the user interaction. Suitably the device may prevent the enabling of at least one of a sleep mode and a screensaver.

Whilst the predetermined portion is always able to receive an interaction, such as an extended interaction, in one example the device is arranged to ignore the interaction if the device is already engaged in an emergency call. In one example, if the device is engaged in a non-emergency call and the extended interaction is detected, the device is arranged to terminate the non-emergency call and to initiate an emergency call.

In the following, the term 'button' will be used to refer to the predetermined portion of the interface 102, whether or not the button is actually visible.

The capacitive touch screen allows a person to interact with the interface 102 of the device 100 without requiring the ability to apply pressure to the interface 102. It can also reduce the manual dexterity needed to interact with the device. This can enable a person with low manual dexterity and/or the inability to apply pressure with, for example, fingers of a hand, to effectively operate the device 100.

The capacitive touch screen may also reduce accidental presses since contact through, for example, the sleeve of a coat may not be recognised by the capacitive touch screen. However, in some examples, it will be desirable for the device 100 to recognise contact through, for example, the sleeve of a coat. This is so that a user can activate the device 100 without needing to worry about whether any clothing is covering the device 100. In these examples, the touch screen is capable of recognising any contact, such as by comprising a resistive touch screen (instead of or in combination with a capacitive touch screen).

The device 100 is arranged to make an outgoing call to a single, emergency, number when the button 114 receives the extended interaction. In other words, the device is restricted to calling just that single number. This avoids complexity when emergency assistance is needed. This emergency number will typically be the number of a monitoring centre staffed by call centre operators who can muster emergency responders as required.

Conventionally, a pendant with a button will allow the simple detection of the button being pressed. In response, it will send a signal to the fixed base unit. In some cases, the button may be pressed inadvertently. The base unit will still make a call to a monitoring centre, and the person will need to speak with a call centre operator to explain that the button press was inadvertent.

With the present device, these inadvertent calls can be minimised or avoided. Rather than making an outgoing call as soon as the button 114 receives an interaction, the device 100 will only make an outgoing call when the button 114 receives an extended interaction.

This extended interaction enables the device 100 to distinguish between an inadvertent and a deliberate interaction.

In one arrangement of the device 100, the extended interaction is one that lasts for a length of time greater than a predetermined threshold time. This is illustrated in figure 2a. When accidentally brushing against or pressing on the button 114, the device 100 will detect an interaction (at step S200). For accidental or inadvertent interactions, these interactions will typically be brief, for example less than 1 second. The threshold time can be set so that these inadvertent interactions with the button 114 do not result in a call being made by the device 100. The threshold time is configurable, and can be set to different lengths of time as required. The threshold time may be at least half a second, for example at least one second. This may help prevent accidental touches from initiating a call. The threshold time may be less than five seconds. In one example, the threshold time is set at 5 seconds. The threshold time is set to a suitable time period so as to minimise inadvertent interactions whilst still enabling a person to make an outgoing call without too long a delay.

Referring again to figure 2a, the device 100 awaits the detection of an interaction with the button 114. Once detected (at step S200) the device 100 determines the duration of the interaction. This can be done in known ways, for example by comparison of a timing signal such as a clock signal with the start of the interaction.

This determination can be made in other ways.

The device 100 does not make the outgoing call at this stage. Rather, the device 100 continues to monitor the interaction with the button 114. If the interaction stops before the duration exceeds the threshold time, then no outgoing call is made, and the process returns to step S200 to detect another interaction.

If the duration of the interaction exceeds the threshold time, for example 5 seconds, then the device 100 determines (at step S202) that an extended interaction has been detected. The device 100 then proceeds, in step S204, to make the outgoing call.

In one example, the device is arranged to detect the interaction when a contact, such as a touch, is made with the interface at a constant location. There is, in one example, tolerance in determining whether the location is constant, for example if the contact location varies by less than 5mm (or other suitable distance) this may be determined to be a constant location. This may enable the device to distinguish an extended interaction from another type of interaction, such as a swipe interaction. In one example, the device 100 may be arranged to disregard a swipe interaction, such as by having this functionality, where present, disabled.

In one example the device is arranged to make the outgoing call in response to an extended interaction being detected at any portion of the interface 102. In other words, contact with any portion of the interface may be detected by the device as an interaction. This enables a user to call for assistance without needing to worry about where on the interface they are contacting the interface.

In the present arrangement, the device 100 is arranged to provide feedback to the user of the device 100. This may enable the user to know when an interaction, and when an extended interaction, has been detected by the device 100. The feedback comprises, in one example, a visual change in the display portion 104 of the interface. In one example, the feedback comprises a visual change in the predetermined portion.

In one example, the interface 102 flashes when an interaction is detected. The flashing can then stop for the remainder of the duration of the interaction, and start again when an extended interaction is detected by the device 100. This alerts the user to the detection of the extended interaction. Alternatively, the flashing can continue for the duration of the interaction, and stop when an extended interaction is detected. In another example, the device 100 flashes when it detects an interaction.

As the interaction continues, the flashing changes in at least one of intensity (brightness and/or timing) and colour. A particular intensity (for example a continuous light) and/or colour (say, red) can indicate to the user that an extended interaction has been detected.

In response to a user interacting with the button 114, the device 100 can, for example, light up with a white light. This can continue until the duration of the interaction exceeds the threshold time and an extended interaction is detected. The device 100 can then light up with a red light. This indicates to the user that the device 100 is making the call (or trying to make the call), and that the user can stop interacting with the button 114.

In another example, the device 100 vibrates when an interaction is detected. The vibration is caused by the motor 108. The vibrations may increase in intensity as the duration of the interaction increases. The vibrations may change once an extended interaction is detected. On the initial interaction, the device 100 may start vibrating in pulses. As the interaction duration increases, these pulses might become more frequent. Once an extended interaction is detected, the device 100 might vibrate continuously for a predetermined period of time. Again, this can indicate to a user that an extended interaction has been detected and that the device 100 is making the outgoing call (or trying to make the outgoing call).

In another example, the device 100 makes a noise when an interaction is detected.

The noise is generated by the speaker 110. On detection of the interaction, the device 100 emits a beeping noise. As the duration of the interaction increases, the beeping noise increases in at least one of volume and pitch. Once an extended interaction is detected, the device 100 emits a continuous noise. This signals to the user that the device 100 is making the outgoing call (or trying to connect the outgoing call).

It will be understood that, in other arrangements, the device 100 can light up, vibrate and make a noise in the same and/or other ways, and in any combination of these ways.

In another example, the button 114 changes as the interaction proceeds. This may be a change in the visual representation of the button 114 on the display portion 104. The button 114 increases in size until it reaches a maximum when the device 100 detects the extended interaction (figure 2b). Additionally or alternatively, the text of the button 114 changes in size or visibility to indicate that the device has detected the interaction (figure 2c). For example, the text can change in colour or fade from view. Disappearance from view of the text, for example by the text changing colour to match that of the remainder of the button 114, can indicate that an extended interaction has been detected.

In one example, where the button 114 is not normally visible on the interface 102, it becomes visible on the detection by the device 100 of the interaction. The changes in the button 114 then proceed as discussed above for an initially-visible button 114.

In one example, where the button 114 is not normally visible on the interface 102, it becomes visible on the detection by the device 100 of the extended interaction. This may signal to a user that the extended interaction has been detected. That is to say, it may signal to a user that the device is making the outgoing call.

In another example, the button 114 may remain visibly absent from the interface 102 and one or more of other visual, tactile and audible feedback is provided.

Providing feedback in this way to a user of the device allows indication to the user of the status of the device, i.e. whether one or more of detecting an interaction and detecting an extended interaction and attempting to call the number. This can reassure the user that the device has detected the interaction and/or extended interaction. This may help in the correct usage of the device, for example by assisting a user to continue with an interaction such as a contact until the extended interaction is detected, which may increase the ease of use of the device 100.

The making of the outgoing call will now be discussed with reference to figure 3a. In one example, once the device 100 makes the outgoing call (step S300), it checks whether a connection, such as with one of the network and another apparatus (such as a telephone), has been established (at step S302). If no connection can be established, then the device 100 automatically retries to make the outgoing call (step S304). This continues until the connection has been established and/or until at least one of a time limit and a retry limit is reached.

In this way, the user of the device 100 does not need to manually retry to make the call. This could be distressing in an emergency. In some examples, the device 100 does not indicate to the user that it is retrying to make the call. Rather, the display portion 104 of the interface 102 may simply show that a connection is being established, without showing how this connection is proceeding until it is made.

Once the connection is established and the outgoing call started, the device logs the details, such as time, at step S306. The device 100 determines, at step S308, whether the call is answered. When the call is answered, the voice call will start, and the device 100 logs the details, such as time, at step S310. When the call ends, the device 100 again logs the details, such as time, at step S312.

The logging of the call details enables an audit trail to be created to monitor the calls 5 being made. The logging can be done at/by the device 100 as discussed above. Alternatively or additionally, the logging can be done at a remote server. The remote server is, in one example, located at the monitoring centre.

As mentioned above, the device 100 is capable of receiving as well as making calls.

It is desirable that the device 100 cannot receive calls from any incoming number, but only from a limited number of incoming numbers (such as from a monitoring centre, and from nominated family and friends). This can minimise the use of the device 100 for non-emergency uses, and help increase the amount of time that the device 100 can run on a single battery charge. Also, the reduction of incoming numbers allowed to connect to the device 100 means that the device 100 is less likely to be engaged on another call when an incoming call is received. This enhances the usefulness of the device 100 as an emergency calling device.

Further, it is desirable for the device 100 to be configurable to automatically answer at least some calls received by the device 100 without requiring any user interaction.

This can mean that the device automatically enters a state in which it enables voice communication, such as a voice call, for example a two-way voice call. In one example, the device is arranged, on automatically answering a call, to enable the speaker 110 and microphone 112. This enables contact, such as a voice call, to be made with the user of the device 100 even if the person is unable to operate the device 100.

The process of receiving incoming calls will now be discussed with reference to figure 4. Initially, the device 100 receives an incoming call, at step S400. The device then checks whether the incoming call is from a number that is allowed to connect to the device 100 (step S402). This check is done in one example by using a permissions list to check whether the number is authorised. The incoming call is compared to a permissions list which comprises identifiers of all permitted incoming call numbers. In one example, the identifiers are the incoming call numbers themselves. Thus, in this example, the permissions list authorises a call from an incoming call number when that number is contained in the permissions list.

In one example, the permissions list is at the device 100. Alternatively or additionally, the permissions list is at a remote server. In one example the remote server is at the monitoring centre. In another example the remote server is located remote from the monitoring centre.

If the incoming call is not authorised, then the call is not allowed to connect to the device 100 and is rejected (step S404).

If the incoming call is authorised, then the call proceeds to the device 100 and the user is notified (at step S406). The device 100 generates a notification to notify the user of the incoming call. The notification is in one example a ring tone. The notification can also be visual (such as at least a portion of the display portion 104 lighting up) or tactile (such as the motor 108 generating vibrations), or some combination of audible, visual or tactile. In one example, the response, such as the generation of the notification, of the device 100 to the incoming call is user-configurable.

For incoming calls authorised to connect to the device 100, the device 100 determines whether the call should be automatically answered, or whether the user can decide whether or not to answer the call. This determination is made, in one example, by reference to the permissions list. In another example, the auto-answer status of the incoming call number is provided to the device 100 from another list, such as a profile list, on the device 100 or at a remote server. In another example, the incoming call comprises the auto-answer status, and the device is arranged to automatically answer the call in response to detecting from the auto-answer status that the call should be automatically answered.

Where the device 100 determines that the incoming call should not automatically be answered (at step S408), it awaits detection of an answer interaction from a user (step S410). This answer interaction is in one example the interaction of a user with an answer button displayed on the interface 102. The call is then answered (at step S414).

Where the device 100 determines that the incoming call should automatically be answered (step S408), it determines whether a criterion for answering the call has been met. In one example, this criterion is the time period since receiving the incoming call exceeding a predetermined time period. In other words, the incoming call is automatically answered after a predetermined time. Similarly, it could be answered after a predetermined number of rings.

Following the example above, the device 100 determines whether the time period since receiving the incoming call exceeds a predetermined time period (at step S412). When the predetermined time period is exceeded, the device 100 answers the incoming call (step S414).

Similar to the discussion above, when the incoming call is answered, the voice call will start, and the device 100 logs the details, such as time and the incoming number, at step S416. When the call ends, the device 100 again logs the details, such as time, at step S418. Alternatively or additionally, the logging may be done at/by the remote server.

In one example, the device is arranged to re-establish a connection when it is lost. That is to say, in response to the device determining that a call has been dropped (at step S352 of figure 3b), it will attempt to reconnect the call (step S356). In some examples, the device is arranged to try reconnecting the call for at least one of an incoming and an outgoing call (optional step S354 is discussed below). This may be done without any interaction with the device, such as by a user. Thus a user, who may be distressed or physically unable to interact with the device can still continue with the call. In some examples, the device carries on trying to re-establish the call until the call can be made (step S358). Once connected, the call can start and the details can be logged as before (step S360).

This can provide additional assurance to a user of the device. Once a call has been established, the device will enable that call to continue even if the call is interrupted before it ends. The device, in some examples, determines whether the call is terminated, for example deliberately such as by a party to the call. In response to finding that the call was ended on purpose, the device may determine that the call should not be automatically reconnected. In response to finding that the call was not ended on purpose, for example determining that the call was interrupted, the device will attempt to reconnect the interrupted call. In some examples, the device is arranged to automatically reconnect calls to and/or from one or more predetermined number (in other words, optional step S354 of figure 3b determines whether the call should be reconnected, for example only for the one or more predetermined number). The one or more predetermined number is, in one example, at least one of the numbers authorised by the permissions list.

It is desirable if a call, once connected (either made or received by the device 100), cannot be disconnected by a user of the device 100. This enables an emergency call to be maintained, even if a user was to inadvertently press a disconnection button. In some examples, the device is arranged such that the interface provides no facility for the termination of a call. The device 100 is configurable to permit or deny the disconnection of a call by the interface 102.

In one example, the device 100 determines whether, for a given call, the interface 102 provides a facility for disconnecting the call. In other words, the device 100 determines whether or not the interface 102 permits disconnection of the call.

This determination is made, in one example, by reference to the permissions list.

The permissions list comprises, in one example, a disconnection ability status indicator, such as a flag, against at least one of the indicators in the permissions list. In another example, the device 100 is configurable to permit or deny the disconnection of a call by the interface 102 in response to another list, such as a profile list, on the device 100 or at a remote server.

In other words, there may be a number from which a call is automatically answered and which call the user cannot disconnect (for example, from the monitoring centre). There may be another number from which a call is not automatically answered and which call the user can disconnect (for example, from a family member). Other combinations of auto-answer and disconnect ability are possible. This arrangement facilitates the use of the device 100 as an emergency calling device, whilst allowing flexibility of use.

Referring to figure 5, the device 100 determines that a call connection has been made, at step S500. The device 100 receives a disconnection interaction (step S502). In one example, the disconnection interaction is the pressing of a disconnection button on the device 100, for example on the interface 102.

The device 100 then determines whether the interface 102 permits disconnection of the call (step S504; this can be done as discussed above). If the interface 102 does not permit disconnection of the call, the device 100 ignores the disconnection interaction (at step S506). If the interface 102 does permit disconnection of the call, the device 100 disconnects the call (step S508).

In some examples, where it is determined that the interface 102 does not permit the disconnection of the call, no disconnection button may be displayed. This may indicate to a user that the call cannot be disconnected by the device 100.

As discussed in the context of making and receiving calls above, the device 100 (and/or a remote server) can log details of the call disconnection, such as whether the disconnection was user-initiated, and the time of the disconnection.

As well as being usable for making and receiving voice calls, the device 100 can also 25 be used to send reminders to a user of the device. Such reminders can be in the form of at least one of text and an image. This can be useful to remind a user of the device to take their medicine at a particular time of day, for example.

The reminder may be generated by the device 100 itself or it may be generated from a remote server, such as one at the monitoring centre. Following generation of the reminder (step S600 of figure 6), the user of the device 100 is notified of the reminder (step S602). This notification is, in one example, by way of displaying the reminder on the display portion 104 of the device 100. This notification can be accompanied by any one or more of another visual notification, a tactile notification and an audible notification, as discussed above.

The device 100 logs details of the reminder, such as the reminder itself and the time notified to the user (step S602). Where the reminder is generated by the remote server, the device 100 optionally sends an acknowledgement to the server that the reminder has been notified to the user. The device 100 may log this acknowledgement.

The reminder is displayed on the device 100 such that a user can acknowledge the reminder. This is done in one example by the provision of a button on the interface 102 when the reminder is displayed. Pressing of the button by the user acknowledges that the user has seen the notification. The notification disappears when the user has acknowledged it.

The device 100 monitors whether the notification has been acknowledged by the user (at step S604). If the notification has been acknowledged, this is noted by the device 100 and logged, together with details of the acknowledgement, such as the time (step S606). Optionally, the device 100 informs the remote server that the notification has been acknowledged.

If no acknowledgement has been made, the device 100 determines (at step S608) whether a certain time period has elapsed since the notification was made. In one example this time period is 10 minutes. In other examples the time period can differ.

In some examples, the time period is configurable, for example by a monitoring centre or remote server. If this time period has not elapsed, the device continues to monitor for an acknowledgement. Once this time period has elapsed, the device 100 logs that no acknowledgement has been made, and optionally informs the server of this. The device 100 may log this communication with the server.

Again, details may alternatively and/or additionally be logged at the remote server.

Even when the notification is displayed on the device 100, the button 114 remains active, and the device monitors for an interaction with the button 114. In the event that the device detects an interaction with the button 114, the reminder may disappear from view as shown in figure 2b, and the device 100 may proceed to make an outgoing call as described above.

The device is, in one example, used as part of an assistance system in conjunction with other monitors/sensors. Such sensors are, for example, of the type used in Z-Wave monitoring systems, such as movement sensors, pressure sensors, light sensors, temperature sensors, door/window sensors and so on.

The assistance system is arranged, in one example, so that if it is detected that a person has not moved in a particular time period, or has not got out of bed by a particular time, a call is made to the device to see if the person is alright.

The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the present specification as a whole in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims. The applicant indicates that aspects of the present invention may consist of any such individual feature or combination of features. In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the invention.

Claims

CLAIMS1. A mobile communication device for connecting to a communication network, the device being arranged to make an outgoing call over the network only in response to the detection by the device of an extended user interaction with the device.
2. A mobile communication device according to claim 1, the extended user interaction comprising a single interaction for a length of time greater than a predetermined threshold time.
3. A mobile communication device according to any preceding claim, where the device is an emergency calling device.
4. A mobile communication device according to any preceding claim, the device being constrained to call a single number.
5. A mobile communication device according to any preceding claim, the device being arranged to detect an interaction in response to a user interacting with a predetermined portion of an interface of the device.
6. A mobile communication device according to any preceding claim, the device being arranged to provide feedback to a user in response to an interaction being detected.
7. A mobile communication device according to claim 6, the device being arranged to provide feedback during at least a portion of the interaction.
8. A mobile communication device according to one of claims 6 to 7, the device being arranged to change the feedback through at least a portion of the interaction.
9. A mobile communication device according to any preceding claim, the device being arranged to automatically retry making the outgoing call until an outgoing connection can be made.
10.A mobile communication device according to any preceding claim, the device being arranged to automatically try to reconnect a dropped call.
11.A mobile communication device according to any preceding claim, the device being arranged to receive an incoming call over the network, and to automatically answer the incoming call.
12.A mobile communication device according to claim 11, the device being arranged to automatically answer the incoming call after a predetermined time period has elapsed after receiving the incoming call.
13.A mobile communication device according to claim 11 or claim 12, the device being arranged to provide a notification to a user of an incoming call before the call is automatically answered.
14.A mobile communication device according to any preceding claim, the device being arranged to accept an incoming call from a predetermined number in response to a permissions list authorising the predetermined number.
15.A mobile communication device according to any preceding claim, the device being arranged so that at least one of the outgoing call and an incoming call from a first number cannot be disconnected by the interface of the device.
16.A mobile communication device according to any preceding claim, the device being arranged so that the predetermined portion of the interface is always able to receive a user interaction.
17.A mobile communication device according to any preceding claim, the device being arranged to log details of one or more of the time, duration and number of any incoming and outgoing calls.
18.A mobile communication device according to any preceding claim, the device being a watch.
19.An emergency calling system comprising the mobile communication device according to any preceding claim and a remote device.
20.A method of making an outgoing call over a communication network from a mobile communication device for connecting to the network, the method comprising the steps of: detecting an interaction with the device; determining whether the interaction is an extended interaction; and only in response to determining that the interaction is an extended interaction, making an outgoing call over the network.
21.An apparatus substantially as herein described and/or with reference to the accompanying drawings.
22.A method substantially as herein described and/or with reference to the accompanying drawings.