Automatic security action invocation for mobile communications device

A mobile communications device, server, and method for providing security on a mobile communications device are described. In accordance with one example embodiment, the mobile communications device comprises: a processor; a communications subsystem connected to the processor operable to exchange signals with a wireless network and with the processor; a storage element connected to the processor and having a plurality of application modules and data stored thereon, the data comprising at least user application data associated with the application modules and service data including data for establishing communications with the wireless network; and a security module operable to detect policy messages received by the mobile communications device, wherein the security module is further operable to perform a security action if a first policy message to enforce a first data protection policy is received and a subsequent policy message to enforce a second data protection policy is not received within a predetermined duration from the time at which the first policy message is received; and wherein the security action comprises erasing or encrypting at least some of the data on the storage element.

TECHNICAL FIELD

The present application relates to security for mobile communications devices.

BACKGROUND

As a result of their mobility, mobile communications devices are sometimes lost or stolen. Frequently, the loss of the information stored on a missing device is of greater concern than the loss of the device itself. For example, the device may have sensitive and/or confidential information stored on it that could cause harm if acquired by others. Such sensitive information could include, among other things, stored messages of a confidential nature, and stored communications information that would allow a third party to masquerade electronically as the person to whom the mobile device rightfully belongs.

In some mobile communications networks, once a user discovers that his or her mobile device is missing, he or she can contact the network operator or the system administrator for his or her organization and request that a “kill packet” be sent to the missing mobile device instructing the device to wipe sensitive information from its memory. However, such a system requires that the user realize that the mobile device is missing, and that the mobile device be in communication with the network. If the user relies on the device for communication, they may be unable to report it missing or stolen in a timely manner.

Thus, security for mobile communications devices remains a concern.

It will be noted that throughout the drawings similar features are identified by the same reference numerals.

DETAILED DESCRIPTION

In accordance with one example embodiment of the present application, there is provided a mobile communications device, comprising: a processor; a communications subsystem connected to the processor operable to exchange signals with a wireless network and with the processor; a storage element connected to the processor and having a plurality of application modules and data stored thereon, the data comprising at least user application data associated with the application modules and service data including data for establishing communications with the wireless network; and a security module operable to detect policy messages received by the mobile communications device; wherein the security module is further operable to perform a security action if a first policy message to enforce a first data protection policy is received and a subsequent policy message to enforce a second data protection policy is not received within a predetermined duration from a time at which the first policy message is received; and wherein the security action comprises erasing or encrypting at least some of the data on the storage element.

In accordance with another example embodiment of the present application, there is provided a mobile communications device, comprising: a processor; a communications subsystem connected to the processor operable to exchange signals with a wireless network and with the processor; a storage element connected to the processor and having a plurality of application modules and data stored thereon, the data comprising at least user application data associated with the application modules and service data including data for establishing communications with the wireless network; and a security module operable to determine if a battery level falls below a predetermined threshold and perform a security action comprising erasing or encrypting at least some of the data on the storage element if the battery power falls below the predetermined threshold.

In accordance with a further example embodiment of the present application, there is provided a mobile communications device, comprising: a processor; a communications subsystem connected to the processor operable to exchange signals with a wireless network and with the processor; a storage element connected to the processor and having a plurality of application modules and data stored thereon, the data comprising at least user application data associated with the application modules and service data including data for establishing communications with the wireless network; and a security module operable to detect a locked state of the mobile communications device and initiate a lockout data protection timer for a predetermined duration upon detection of the locked state; and wherein the security module is operable to, after the lockout data protection timer has been initiated, detect if a password shared by the user and the mobile communications device is entered through a user input device within the predetermined duration of the lockout data protection timer; wherein the security module is operable to terminate the lockout data protection timer if entry of the password is detected within the predetermined duration; and wherein the security module is operable to perform a security action comprising erasing or encrypting at least some of the data on the storage element if entry of the password is not detected within the predetermined duration.

In accordance with a further example embodiment of the present application, there is provided a mobile communications device, comprising: a processor; a communications subsystem connected to the processor operable to exchange signals with a wireless network and with the processor; a storage element connected to the processor and having a plurality of application modules and data stored thereon, the data comprising at least user application data associated with the application modules and service data including data for establishing communications with the wireless network; and a security module operable to detect if a delayed data protection initiate command is received by the mobile communications device; wherein the security module is operable to initiate a delayed data protection timer for a first predetermined duration provided in the delayed data protection initiate command if the delayed data protection initiate command is received; wherein the security module is operable to, after the delayed data protection timer has been initiated, detect: (i) entry of a password shared by the user and the mobile communications device through a user input device within the first predetermined duration of the delayed data protection timer; (ii) receipt by the mobile communications device of a terminate command; or (iii) receipt by the mobile communications device of a delay command; wherein the security module is operable to terminate the delayed data protection timer if entry of the password or receipt of the terminate command is detected within the first predetermined duration; wherein the security module is operable to reset the delayed data protection timer for a second predetermined duration provided in the delay command if receipt of a delay command is detected within the first predetermined duration; and wherein the security module is operable to perform a security action comprising erasing or encrypting at least some of the data on the storage element if entry of the password, receipt of the terminate command, or receipt of a delay command is not detected within the first predetermined duration.

In accordance with a further example embodiment of the present application, there is provided a method for providing security on a mobile communications device, the mobile communications device being configured to communicate with a wireless communications network and including a storage element having data stored thereon, the method comprising the acts of: monitoring to detect policy messages received by the mobile communications device; and if a first policy message to enforce a first data protection policy is received and a subsequent policy message to enforce a second data protection policy is not received within a predetermined duration from a time at which the first policy message is received, performing a security action comprising erasing or encrypting at least some of the data on the storage element.

In accordance with a further example embodiment of the present application, there is provided a method for providing security on a mobile communications device, the mobile communications device being configured to communicate with a wireless communications network and including a storage element having data stored thereon, the method comprising the acts of: monitoring to determine if a battery level falls below a predetermined threshold, and if the battery power falls below the predetermined threshold, performing a security action comprising erasing or encrypting at least some of the data on the storage element.

In accordance with a further example embodiment of the present application, there is provided a method for providing security on a mobile communications device, the mobile communications device being configured to communicate with a wireless communications network and including a storage element having data stored thereon, the method comprising the acts of: monitoring to detect for the locked state of the mobile communications device and initiating a lockout data protection timer for a predetermined duration upon detection of the locked state; and monitoring, after the lockout data protection timer has been initiated, to detect if a password shared by the user and the mobile communications device is entered through the user input device within the predetermined duration of the lockout data protection timer; if entry of the password is detected within the predetermined duration, terminating the lockout data protection timer; and if entry of the password is not detected within the predetermined duration, performing a security action comprising erasing or encrypting at least some of the data on the storage element.

In accordance with a further example embodiment of the present application, there is provided a method for providing security on a mobile communications device, the mobile communications device being configured to communicate with a wireless communications network and including a storage element having data stored thereon, the method comprising the acts of: monitoring to detect if a delayed data protection initiate command is received by the mobile communications device, and if a delayed data protection initiate command is received, initiating a delayed data protection timer for a first predetermined duration provided in the delayed data protection initiate command; and monitoring, after the delayed data protection timer has been initiated, to detect for: (i) entry of a password shared by the user and the mobile communications device through the user input device within the first predetermined duration of the delayed data protection timer; (ii) receipt by the mobile communications device of a terminate command; or (iii) receipt by the mobile communications device of a delay command; if entry of the password or receipt of the terminate command is detected within the first predetermined duration, terminating the delayed data protection timer; if receipt of a delay command is detected within the first predetermined duration, resetting the delayed data protection timer for a second predetermined duration provided in the delay command; and if entry of the password, receipt of the terminate command, or receipt of a delay command is not detected within the first predetermined duration, performing a security action comprising erasing or encrypting at least some of the data on the storage element.

In accordance with a further example embodiment of the present application, there is provided a server for providing security on at least one mobile communications device, the server being configured to communicate with a plurality of mobile communications devices over a wireless network, the server comprising: a processor; a communications subsystem connected to the processor for exchanging signals with the wireless network and with the processor; and a security module for sending policy messages to one or more of the mobile communications devices in the plurality of mobile communications devices associated with the server at predetermined intervals in accordance with a predetermined frequency, the policy messages including instructions for execution by the one or more of the devices to enforce or terminate a data protection policy.

In accordance with a further example embodiment of the present application, there is provided a communications system for providing security on a mobile communications device, comprising:one or more mobile communications devices, each comprising: a processor; a communications subsystem connected to the processor operable to exchange signals with a wireless network and with the processor; a storage element connected to the processor and having a plurality of application modules and data stored thereon, the data comprising at least user application data associated with the application modules and service data including data for establishing communications with the wireless network; and a security module operable to detect policy messages received by the mobile communications device; wherein the security module is further operable to perform a security action if a first policy message to enforce a first data protection policy is received and a subsequent policy message to enforce a second data protection policy is not received within a predetermined duration from a time at which the first policy message is received; and wherein the security action comprises erasing or encrypting at least some of the data on the storage element; anda server comprising: a processor; a communications subsystem connected to the processor for exchanging signals with the wireless network and with the processor; and a security module for sending policy messages to the one or more mobile communications devices at predetermined intervals in accordance with a predetermined frequency, the policy messages including instructions for execution by the one or more of the mobile communications devices to enforce or terminate a data protection policy.

In accordance with a further example embodiment of the present application, there is provided a computer program product comprising a machine-readable medium tangibly embodying instructions executable on a mobile communications device for providing security on the mobile communications device, the machine-readable instructions comprising: code for monitoring to detect policy messages received by the mobile communications device; and code for performing a security action comprising erasing or encrypting at least some of the data on the storage element if a first policy message to enforce a first data protection is received and a subsequent policy message to enforce a second data protection policy is not received within a predetermined duration from a time at which the first policy message is received.

Referring now to the drawings,FIG. 1is a block diagram of a mobile communication device10to which example embodiments described herein can be applied. The mobile communication device10is a two-way communication device having at least data and possibly also voice communication capabilities and the capability to communicate with other computer systems on the Internet. Depending on the functionality provided by the device, in various embodiments the device may be a data communication device, a multiple-mode communication device configured for both data and voice communication, a mobile telephone, a PDA (personal digital assistant) enabled for wireless communication, or a computer system with a wireless modem, among other things.

The mobile device10includes a wireless communication subsystem11for exchanging radio frequency signals with a wireless network50. The communication subsystem11includes a receiver, a transmitter, and associated components, such as one or more antenna elements, local oscillators (LOs), and digital signal processor (DSP). As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem11depends on the wireless network50in which mobile device10is intended to operate.

The mobile device10may send and receive communication signals over the wireless network50after the required network registration or activation procedures have been completed. Signals received by the antenna through the wireless network50are input to the receiver, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and the like, and analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in the DSP. In a similar manner, signals to be transmitted are processed, including modulation and encoding, for example, by DSP. These DSP-processed signals are input to the transmitter for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over the wireless network50via the antenna. The DSP not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in the receiver and the transmitter may be adaptively controlled through automatic gain control algorithms implemented in the DSP.

The mobile device10includes a controller in the form of at least one microprocessor38that controls the overall operation of the mobile device10. The microprocessor38interacts with communications subsystem11and also interacts with further device subsystems such as the display22, flash memory24, random access memory (RAM)26, auxiliary input/output (I/O) subsystems28, serial port30, keyboard or keypad32, speaker34, microphone36, a short-range communications subsystem40, a clickable thumbwheel (trackwheel) or trackball (not shown), and any other device subsystems generally designated as42.

Some of the subsystems shown inFIG. 1perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions. Notably, some subsystems, such as keyboard32and display22for example, may be used for both communication-related functions, such as entering a text message for transmission over a communication network, and device-resident functions such as a calculator or task list.

Operating system software54and various software applications58used by the microprocessor38are, in one example embodiment, stored in a persistent store such as flash memory24or similar storage element. Those skilled in the art will appreciate that the operating system54, specific device applications58, or parts thereof, may be temporarily loaded into a volatile store such as RAM26. It is contemplated that received communication signals may also be stored to RAM26.

The microprocessor38, in addition to its operating system functions, enables execution of software applications58on the device. A predetermined set of applications58which control basic device operations, including at least data and voice communication applications for example, will normally be installed on the mobile device10during manufacture. Further applications may also be loaded onto the mobile device10through the network50, an auxiliary I/O subsystem28, serial port30, short-range communications subsystem40or any other suitable subsystem42, and installed by a user in the RAM26or a non-volatile store for execution by the microprocessor38. Such flexibility in application installation increases the functionality of the device and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the mobile device10.

In a data communication mode, a received signal such as a text message or web page download will be processed by the communication subsystem11and input to the microprocessor38, which will further process the received signal for output to the display22, or alternatively to an auxiliary I/O device28. A user of mobile device10may also compose data items such as email messages for example, using the keyboard32in conjunction with the display22and possibly an auxiliary I/O device28. Such composed items may then be transmitted over a communication network through the communication subsystem11.

The serial port30(which may for example be a Universal Serial Bus (USB) port) inFIG. 1would normally be implemented in a personal digital assistant (PDA)-type communication device for which synchronization with a user's desktop computer (not shown) may be desirable, but is an optional device component. Such a port30would enable a user to set preferences through an external device or software application and would extend the capabilities of the device by providing for information or software downloads to the mobile device10other than through a wireless communication network.

A short-range communications subsystem40is a further component which may provide for communication between the mobile device10and different systems or devices, which need not necessarily be similar devices. For example, the subsystem40may include an infrared device and associated circuits and components or a Bluetooth™ communication module to provide for communication with similarly enabled systems and devices. The mobile device10may be a handheld device. The mobile device10includes a battery12as a power source, which will typically be a rechargeable battery that may be charged, for example, through charging circuitry coupled to the USB port30

Wireless communication network50is, in an example embodiment, a wireless wide area packet data network, which provides radio coverage to mobile devices10. Wireless communication network50may also be a voice and data network such as GSM (Global System for Mobile Communication) and GPRS (General Packet Radio System), CDMA (Code Division Multiple Access), or various other third generation networks such as EDGE (Enhanced Data rates for GSM Evolution) or UMTS (Universal Mobile Telecommunications Systems). In some example embodiments, network50is a wireless local area network (WLAN), such as for example a network compliant with one or more of the IEEE 802.11 family of standards. In some example embodiments, the mobile device10is configured to communicate in both data and voice modes over both wireless WAN and WLAN networks and to roam between such networks.

In an example embodiment, wireless gateway62is adapted to route data packets received from a mobile communication device10over wireless mobile network50to destination electronic mail messaging or Internet access server68through a mobile device server66, and to route data packets received from the server68through the mobile device server66over the wireless mobile network50to a destination mobile communications device. Wireless gateway62forms a connection or bridge between the servers and wireless networks associated with wireless e-mail communication and/or Internet access. In an example embodiment, wireless gateway62is coupled between wireless network50and a hardwired data network (for example an enterprise network70that is located behind a firewall) that includes mobile device server66and electronic mail server68. The wireless gateway62, in example embodiments, stores system configuration information, system state data, and tables that store mobile device10information. The mobile device server66, in example embodiments, is a server located in an enterprise network70behind a firewall and connected to the wireless gateway62through the Internet or another connection. Mobile device server66is configured as an enterprise's interface between the enterprise network70and the wireless network50. Typically, a plurality of mobile devices10will be associated with a mobile device server66that is part of the enterprise network70managed by an organization that the users of such mobile devices10are part of. Mail server68is coupled to mobile device server66and, in one embodiment, is a conventional electronic mail server. In another embodiment, the mobile device server66is a component of the mail server68. In some embodiments, the mobile device server66may be operated by a wireless carrier that operates wireless network50.

The mobile device10stores data60in an erasable persistent memory, which in one example embodiment is flash memory24. In various embodiments, the data60includes service data61comprising information required by the mobile device10to establish and maintain communications with the wireless communications network50(wireless network service data) and the wireless gateway62(gateway service data). The data60may also include other data64, user application data63such as email messages, address book and contact information, calendar and schedule information, notepad documents, image files, and other commonly stored user information stored on the mobile device10by its user. The data60may also include data required for the communications layers managed by the mobile device server66and servers68. The data60often includes critical data that the user of mobile device10(or others) does not want to be accessed by an unauthorized party.

In some examples, flash memory24may include both a memory component that is permanently part of the mobile device10, as well a removable memory including for example memory on a Subscriber Identity Module (SIM) card. Some of the data60may be stored on the SIM card, and some stored on permanent flash memory.

In an example embodiment, mobile device server66is configured to periodically transmit IT (Information Technology) data protection policy messages72(sometimes referred to as merely policy messages72) through the wireless gateway62and wireless network50to its associated mobile devices10. Typically, mobiles devices10will have a number of settings, including security settings that are governed by a data protection policy. The periodic transmission of data protection policy messages from the mobile device server66to addressed mobile device10that are associated with the mobile device server66assists in ensuring, among other things, that each of the mobile devices10is kept up to date with the latest data protection policy. The content and frequency of policy messages72can be set by an authorized IT administrator of enterprise network70.

In order to provide security for a lost or stolen mobile device10, the mobile device10includes a security module56, which in one example embodiment is implemented by a software component that is part of the operating system54. In other embodiments, the security module56is, or is part of, a specialized software application58separate from the operating system54. The security module56includes instructions for configuring the microprocessor38to cause the mobile device10to carry out at least parts of the security processes that are described below. The process200shown inFIG. 2is intended to address a security situation in which a user's mobile device10has been lost or stolen and is no longer able to receive messages from the mobile device server66and hence cannot receive a “Kill Packet” or “Device Wipe” command. Generally, in the security process200, a data protection security action (for example, a device wipe) is taken on the mobile device10if a specified amount of time passes without the mobile device10receiving a policy message72from its associated mobile device server66. Thus, if the mobile device10is out of radio coverage for too long a time period, it will be wiped. Also, even if the device is in radio coverage of a wireless network, but that particular network is not a network through which the mobile device10can receive data protection policy packets from the mobile device server66, then the mobile device10will be wiped—for example, if the mobile device10moves out of coverage its “home” wireless network50into an area of alternative network coverage where the operator of the “home” wireless network50does have appropriate coverage agreements in place, then the mobile device10will be wiped after a predetermined duration. Additionally, as will be explained in greater detail below, in some embodiments, the mobile device10will be wiped if it is turned off for too long and thus does not receive an updated policy message72due to being in the “off” state. Alternatively, in other embodiments rather than wiping the device (i.e., erasing data from the mobile device10) data60on the mobile device10may be encrypted.

Prior to explaining the operation of a particular mobile device10in greater detail in the context ofFIG. 2, the configuration of the mobile device server66will first be discussed. In an example embodiment, an IT manager or administrator makes a decision to enable auto-wipe security for at least some of the mobile devices10that are associated with the mobile device server66, and uses an IT data protection policy editor that is coupled to the mobile device server66to set a data protection policy for the affected mobile devices10to automatically wipe the mobile device10when the data protection policy is out of date. As part of selecting the auto-wipe policy, the IT administrator can set both the frequency at which policy messages72are sent, and the duration of time that an auto-wipe should occur after if an updated policy message72is not received at a mobile device10(i.e., the duration of a timer(s), as described in more detail below). In some embodiments, these values may be set at the same time or at different times (for example, via separate user interface dialogues or menus). This allows the frequency at which policy messages72are sent and the duration of timers to be configured independently. In some embodiments, the duration of the timer may be configured to be same as the frequency at which policy messages72are sent, or may be configured to be different. Setting the frequency of policy messages72to be the same as the duration of the timer (for example, setting the policy messages72to be sent every 5 minutes and setting the timer duration to 5 minutes) provides a configuration in which the mobile device10cannot miss a single policy message72without performing a data protection security action (e.g., a device wipe). This configuration may not be advantageous for users that may be out of coverage periodically, depending on the specific timer duration/frequency of policy messages72. For such users, specifying a timer duration which is greater than the frequency of policy messages72may allow one or more policy messages72to be missed without performing a data protection security action (depending on the specific values assigned to the frequency of the policy messages72and the timer duration), if this capability is desired. By way of illustrative example only, the auto-wipe countdown timer starting time duration could be 24 hours, with the standard duration between policy messages72being set at 8 hours, with the result that missing3consecutive policy messages72will result in a device wipe.

In some embodiments, the IT administrator has the option of setting the data protection policy globally for all mobile devices10associated with the mobile device server66, or for groups or classes of mobile devices10associated with the mobile device server66, or for one or more individual mobile devices10associated with the mobile device server66.

Referring now toFIG. 8, an example embodiment of the mobile device server66will be briefly described. The mobile device server66may be a computer implementing a server application(s) configured for performing the security processes and functions described herein. The mobile device server66in this example embodiment comprises a processor802(i.e., microprocessor) for controlling its operation, a communications subsystem804connected to the processor802for communicating with the wireless network50via the wireless gateway62and with the processor802, a display805such as a monitor, one or more user input devices806such as a keyboard and mouse connected to the processor802for sending user input signals to the processor802in response to user inputs, and a memory or storage element808such as a hard disk drive (HDD), RAM, ROM and/or other suitable memory connected to the processor802, and other suitable input and output devices (not shown) as desired or required. Operating system software810, software applications812, and data814used by the processor802are stored in the memory808. The applications812and data814configure the operation of the mobile device server66. Other features of the mobile device server66for implementing the security processes and functions described herein will be appreciated by persons ordinarily skilled in the art.

The mobile device server66also includes a security module818which, in this example embodiment, is implemented by one or more software components or modules stored in memory808. The security module818configures the processor802to carry out at least parts of the security processes of the mobile device server66that are described herein. In one example embodiment, the security module818is configured for sending policy messages72to one or more of the mobile devices10in the plurality of mobile communications devices10associated with the mobile device server66at predetermined intervals in accordance with a predetermined frequency, the policy messages including instructions for execution by the one or more of the mobile devices10to enforce (i.e., initiate, modify, maintain) or terminate a data protection policy, as explained in more detail herein.

Once the data protection policy associated with one or more mobile devices10is set to specify an auto-wipe policy, a corresponding policy message72specifying the auto-wipe policy is pushed through wireless gateway62and wireless network50to the affected mobile devices10. In some embodiments, the policy message72containing an auto-wipe policy is sent immediately upon the policy being changed. In other embodiments, the revised data protection policy is sent at the next regularly scheduled interval via a policy message72. In an example embodiment, so long as the auto-wipe policy is in effect, each of the policy messages72that are sent to the affected mobile device10will include confirmation that the auto-wipe policy is in effect. In the event that the administrator chooses to rescind the auto-wipe policy, the next policy message72that is sent out from the mobile device server66will omit the auto-wipe policy confirmation.

Turning again toFIG. 2, as indicated in step202, the mobile device10is configured to detect if and when a policy message72that specifies an auto-wipe policy is received by the mobile device10. Next in step204, if a policy message72specifying an auto-wipe policy is received, the mobile device10sets an internal auto-wipe timer to a predetermined time duration, and starts counting down from the predetermined time duration. In an example embodiment, the predetermined time duration to be used for the auto-wipe countdown timer is set in the received policy message72(and thus set by the IT administrator through mobile device server66, as indicated above). In other example embodiments, the countdown auto-wipe timer duration can be set directly at the mobile device10by a user thereof (although caution may need to be exercised as user's often won't have an in depth knowledge of how often policy messages72are actually sent). In an example embodiment, the countdown auto-wipe timer tracks absolute time relative to when the policy message72is received such that any attempt by a user of the device to alter the time by re-setting the clock time and date on the device (either in a conscious attempt to thwart the pending device wipe, or in an innocent attempt to adjust to a different time zone) does not affect the total duration of time allocated to the auto-wipe countdown timer.

As indicated in steps206and208, once the auto-wipe timer has been set and begins to countdown, the mobile device10monitors for the earliest of the following two events to occur: (a) for a new policy message72to be received (step206); or (b) for the auto-wipe timer to time out (step208). In the event that the auto-wipe countdown timer times out before a new data protection policy message72is received by the mobile device10, then a device wipe is automatically performed (step212) (described in greater detail below). In the event that a new data protection policy message72is received before time out of the auto-wipe timer, then the timer countdown ends (step207), and a check is done to see if the newly received policy message72also specifies an auto-wipe policy (step202). If so, the auto-wipe timer is reset to the time specified in the newly received policy message72, and the countdown process begins again.

Turing again to step212ofFIG. 2, a device wipe includes permanently erasing of all user data60stored on the permanent storage (for example flash memory24) and transient storage (for example RAM26) of the mobile device10. In at least some embodiments, erasing the data includes ensuring that at least the relevant memory locations are overwritten with meaningless bits (for example all zeros or all ones). Thus, in a device wipe, in various embodiments, information required by the mobile device10to function as a communications device is deleted (thereby disabling the mobile device10as a communications device—as a possible exception, the ability of the mobile device10to be used for emergency calls such as 911 calls may be maintained), and any information such as stored email and other messages, address book lists, task items, etc. that may be confidential to the user is deleted. In some example embodiments, a device wipe can include erasing only selected classes of data60(for example erasing of all service data61, but not user application data63, or alternatively, erasing all user application data63but not service data61).

With reference toFIG. 3, in at least one example embodiment, the security module56is also configured to wipe the mobile device10when it is turned off and missing data protection policy messages72. Typically, when the mobile device is in an off state its draw on battery12is greatly reduced and substantially all of the device's functions are suspended (for example, its display22and wireless communications subsystem11are shut down). Some limited device functions continue even when the mobile device10is powered off, for example, in an off device, an internal clock continues to run and the device monitors for activation of an “ON” button (so long as the battery has sufficient power). When the mobile device10is powered off, it does not have the ability to receive messages (including policy messages72) through the wireless communications subsystem11. In one example embodiment, the mobile device10is configured so that turning the device off will not thwart an impending device wipe. As indicated in process245ofFIG. 3, the security module56detects if shutdown of the mobile device is initiated (for example, through user selection of a “Turn Power Off” option) while the auto-wipe countdown timer from process200is running (step250). If the device power off is initiated while the auto-wipe timer is running, then an auto-on time is set corresponding to the time remaining on the auto-wipe countdown timer (step252). If the device is still turned off when the auto-on time is reached, the device automatically powers on and performs the device wipe (step254). In example embodiments, sub-process245can be enabled and disabled through policy messages72.

Thus it will be appreciated that the security process ofFIG. 2is based on an underlying assumption that if a mobile device10cannot receive a policy message72, it cannot receive a kill packet, and accordingly data on the device is potentially at risk. This risk is mitigated by wiping the data automatically after a specified amount of time passes without the mobile device receiving a policy message72. In at least some example embodiments, as indicated inFIG. 3, the mobile device10will execute the device wipe even if it is turned off prior to the expiry of the specified time duration.

The security process ofFIG. 2(either on its own or as combined with the process ofFIG. 3) can be varied in example embodiments to reduce the possibility that a device wipe that should otherwise have occurred will not occur due to the mobile device10turning off due to a discharged battery12. In this regard, with reference toFIG. 4, a sub-process265can be performed as part of process200wherein while the auto-wipe countdown timer of process200is running, the security module200monitors to determine if the battery power12falls below a particular threshold (step270), and if the battery power does fall below the predetermined threshold, then a device wipe is performed immediately (step272). In at least one example embodiment, the critical low battery threshold is the level at which the mobile device will automatically turn off its RF radio (namely when the mobile device10will turn off the transmitter and receiver circuitry of the wireless communications system11)—the turning off of the radio is a relevant event as the mobile device10can no longer receive a kill packet when its radio is off. In an alternate embodiment, the critical low battery threshold is a predetermined (or dynamically determined) level at which the mobile device10has just enough battery power remaining to execute the wipe process. Thus, the sub-process265in combination with process200provides a security environment in which a mobile device that is configured to automatically perform a device wipe if a new policy message is not received within a predetermined time duration will perform a pre-emptive device wipe prior to waiting for the entirety of the predetermined time duration if in the meantime battery power goes too low. Such a configuration recognizes that attempting to wait the entire duration of the countdown auto-wipe timer will be ineffective if the battery will not contain enough power to facilitate the wipe at the future time. In example embodiments, sub-process265can be enabled and disabled through policy messages72.

In some embodiments, the sub-process265may be implemented independently of the process200. In such embodiments, a separate IT data protection policy rule may be implemented indicating that the device should wipe itself when the battery level falls below a predetermined threshold regardless of whether an auto-wipe countdown timer is running.

Another example of a security process that can be applied to mobile device10according to a further embodiment will now be described with reference toFIG. 5. The security process500ofFIG. 5permits a user's device to be wiped when it has been lost or stolen but has not been reported as such. In such a situation, the IT administrator will not know that a kill packet should be sent, and furthermore, the device may still be receiving policy messages72and accordingly a device wipe through the process200will not necessarily be triggered. In an example embodiment, the security module56of mobile device10is configured to place the mobile device10into standby locked state upon the occurrence of certain events. While the mobile device10is in a locked mode, the device user is prevented from using substantially all of the functionality of the device, including accessing any data stored on the mobile device10. In order to get the mobile device out of its locked state, the user must enter a password or other shared secret (for example through a keyboard of the device). The events that trigger placing the mobile device10into a locked state may include, for example, user selection of a device lock option; user inactivity for a predetermined duration; lack of wireless network coverage or activity for a predetermined duration or holstering or closing of the mobile device10.

It will be appreciated that the trigger condition for initiating a locked state of the mobile device10may be one of: user input instructing the mobile communications device10to initiate the locked state; the occurrence of a periodic interval or the expiry of a predetermined duration (for example, a long-term timeout may be implemented by the IT administrator which causes the mobile communications device10to lock periodically after a predetermined duration from a trigger condition (such as the unlocking of the device from a previous locked state) regardless of the user activity or network coverage at the time); user inactivity for a predetermined duration (for example, as measured by a lack of user input via the user input devices28,32); loss of communication with the wireless network50; and holstering of the mobile communications device10if the device is a holsterable device or closing of the mobile communications device10if the device is a flip-style device.

The trigger condition may also include a variance from a predetermined threshold in a communications characteristic (such as a messaging traffic pattern between the mobile communications device10and the wireless network50) between the mobile communications device10and the wireless network50, a lack of communication by the mobile communications device10with the wireless network50for a predetermined duration of time, and a variance in the use of the input devices28,32from a predetermined threshold.

In the security process500ofFIG. 5, the data protection policy applied mobile device10has been configured to specify that a device wipe automatically be performed if the mobile device10remains in a locked state for more than a predetermined time duration. In one embodiment, the data protection policy specifying such an auto-wipe security mode can be set at the enterprise network70by an IT administrator and provided to the mobile device10through a policy message72sent by the mobile device server66through the wireless network50. In a similar manner, the auto-wipe security process500can be disabled by an IT administrator at the enterprise network70.

In the case where the security process500is enabled by the data protection policy applied to the mobile device10, then an auto-wipe countdown timer is set to a specified time (which could be for example be specified in a message previously received from mobile device server66) as soon as the mobile device10is placed into a locked state (step504). Similar to the countdown timer used in security process200, the timer used in process500is also based on absolute time so that changes to the clock time or calendar date on the mobile device10do not affect the countdown timer. Once the countdown timer is running, the mobile device10monitors to determine if the user authentication occurs (step506) prior to the expiry of the auto-wipe countdown timer (step508). If the user authenticates within the requisite time period (user authentication including entry of a password or shared secret to unlock the mobile device10), then the countdown timer is stopped (step512). However, if the countdown timer expires before user authentication occurs, then a device wipe occurs (step510) to mitigate against unauthorized access to data on the device.

It will be appreciated that the situation could arise where a policy message72enabling the auto-wipe process ofFIG. 5is received from the mobile device server66while the mobile device10is already in a locked state. In such a situation, the security module56is configured in an example embodiment to immediately set the countdown timer to a value specified in the received policy message72and begin process500. Similarly, a policy message72may be received at the mobile device10disabling the auto-wipe process500ofFIG. 5while the device is locked and the countdown timer is running. In such a situation, the process500is terminated without requiring the user entry of the shared secret.

The sub-process245discussed above (auto-on and device wipe at expiry of timeout period) and the sub-process265(device-wipe when battery low and auto-wipe timer is running) can be run in combination with security process500to further enhance security. Additionally, the security processes200and500can both be applied simultaneously to a mobile device10, with different countdown timers being used for each.

As previously noted, in the example security processes200and500described above, the optional sub-process265can be used to ensure that the mobile device10is wiped if the device battery is sufficiently discharged at the same time that an auto-wipe countdown timer is running. In at least some example embodiments, the security module56can be configured to perform a device wipe any time that the battery charge level falls below a threshold, for example, the threshold at which the device radio (wireless communications subsystem11) gets automatically turned off, regardless of whether any auto-wipe countdown timer is running or not. Thus referring toFIG. 4, step270would be modified so that the only relevant determination to be made is if the battery power is below the threshold, and if so, then a device wipe is automatically performed (step272). In example embodiments, the modified “wipe device when battery low” process265can be enabled and disabled through policy messages72received at a mobile device10.

Another example embodiment will now be described. As noted above, one approach to mobile device security is for the IT administrator to cause the mobile device server66to send a kill packet or device wipe command to a specific mobile device10that the IT administrator has reason to believe may be lost or stolen, perhaps due to a notification from the normal device user that he or she is missing his or her mobile device10. In such situations, the kill packet causes a device wipe immediately upon being received by the mobile device10. However, there may be circumstances where a device user has misplaced his or her device, but thinks that there is a chance that they may recover it, and so the device user does not want the device immediately wiped upon advising the IT administrator of the missing device. In this regard, security process600ofFIG. 6provides a “delayed-wipe process” in which a delayed data protection initiate command sent (e.g., device wipe command) from the mobile device server66includes a specified delay time period (e.g., timer duration), and upon receiving the delayed data protection initiate command, the mobile device10starts delayed data protection timer (e.g., auto-wipe countdown timer) configuring the mobile device10to perform a security action such as a device wipe if one of the following events does not occur prior the expiry of the timer: (i) the device user does not unlock the device prior to expiry of the timer; (ii) the mobile device10does not receive a further message from the mobile device server66that either terminates/revokes the delayed data protection timer; or (iii) the mobile device10does not receive a further message from the mobile device server66that extends the duration of timer.

The illustrated embodiment ofFIG. 6in which the security action to be performed is a device wipe will now be described in more detail. The process600commences when an IT administrator causes a delayed device wipe command to be sent from the mobile device server66and the command is received at the device (step602). A delayed device wipe command is similar to a policy message72but rather than providing details of an IT data protection policy, the delayed device wipe command instructs the mobile device10to start a timer upon receipt of the command and provides information relevant to the timer such as its duration. Typically, the transport and authentication mechanisms for both policy messages72and commands are the same, however different transport and authentication mechanism could be used if desired. After receiving the delayed device wipe command, the security module56of mobile device10then sets an auto-wipe countdown timer to a time specified in the received device wipe command (step604). Similar to processes200and500, the auto-wipe countdown timer of process600measures absolute time so that resetting of the device clock or date has no effect on it. While the auto-wipe countdown timer is running, the security module56monitors for occurrence of any one of the following three events: (i) user authentication, which occurs when the user enters a password or shared secret to the mobile device10(step606); (ii) receipt by the mobile device of a terminate auto-wipe command from the mobile device server66(step608) (useful for example if the device user positively determines that they have left the device in a secure location, but they cannot access it to enter the password); and (iii) receipt by the mobile device of a delay auto-wipe command from the mobile device server66(step612) (useful for example if the device user is reasonably certain, but not positive, that the device is in a secure location and wants more time to reach the device). Events (ii) and (iii) give the device user flexibility to contact the IT administrator and arrange for cancellation or variation of the delayed wipe command. In the event that user authentication (step606) or receipt of a terminate auto-wipe message (step608) occurs before expiry of the auto-wipe timer, than the security process600is terminated (step610). In the event of receipt by the mobile device of a delay auto-wipe command from the mobile device server66(step612) prior to expiry of the auto-wipe countdown timer than the auto-wipe timer is reset to the new value that is specified in the received command (the auto-wipe timer can be shortened by a similar process, if desired, rather than extended). In the event that auto-wipe timer expires prior to the occurrence of one of the above events, then a device wipe is performed (steps616and618) to erase data60and disable the mobile device10.

The sub-process245discussed above (auto-on and device wipe at expiry of timeout period) and the sub-process265(device wipe when battery low and auto-wipe timer is running) can be run in combination with security process600to further enhance security. Additionally, either or both of the security processes200and500can be applied in conjunction with process600to a mobile device10, with different countdown timers being used for each.

FIG. 7illustrates another security sub-process700that can be applied to the mobile device either on its own, or in combination with any or all of the processes200,500and600and other sub-processes described above. In sub-process700, the security module56forces the mobile device10to go into a locked state in the event that the mobile device10is out of radio coverage for a predetermined time period, regardless of any current user input activity. As indicated in step702, the security module56is configured to monitor for a lack of radio coverage through communications subsystem11, and when the lack of coverage time period exceeds a set out-of-coverage time threshold, then the mobile device10is forced into a locked state (step704) regardless of any user interaction with the device at the time. After the device enters the locked state, an authorized user will have the ability to at least temporarily unlock the device upon entry of the correct password or shared secret; however, without the entry of the password or shared secret the device will remain locked.

When sub-process700is enabled, even if the user successfully unlocks the device, it will again lock itself if it remains out of radio coverage for the predetermined out-of-coverage threshold. Security process700provides some assurances that when the mobile device10is out of radio coverage (and thus unable to receive a kill packet or device wipe command) that the device will be in a locked state if it is in unauthorized hands. When combined with security process500, the sub-process700can cause the device lock triggering event for starting the auto-wipe timer of process500. In some embodiments, the security module56may be configured to perform a long term timeout that will lock the device every N minutes regardless of what the user is doing or what the radio coverage for the mobile device10is. Sub-process700can be used to effectively shorten the long term timeout period by applying a shorter timeout threshold when the device is out of radio coverage. In example embodiments, the “lock device when out-of coverage” process700can be enabled and disabled through policy messages72received at a mobile device10.

In accordance with another example embodiment, there is provided a mobile communications device10, comprising: a processor for controlling the operation of the mobile communications device10; a user input device28,32connected to the processor38for sending user input signals to the processor38in response to user inputs; a communications subsystem11connected to the processor38for exchanging signals with a wireless network50and with the processor38; a security module56associated with the processor38for monitoring to detect for a lack of communication through the communications subsystem11, if the duration of the lack of communication through the communications subsystem11time period exceeds a predetermined duration, performing a security action comprising erasing or encrypting at least some of the data60on the storage element24,26. The security module56may also initiate a locked state of the mobile communications device10if the duration of the lack of communication through the communications subsystem11time period exceeds a predetermined duration, and perform monitoring, after the locked state has been initiated, to detect if a password shared by the user and the mobile communications device10is entered through the user input device28,32, and if entry of the password is detected, terminate the locked state. The security module56may be configured to only perform a security action if the duration of the lack of communication through the communications subsystem11time period exceeds a predetermined duration and the mobile communications device10remains in a locked state. The monitoring to detect for a lack of communication and/or monitoring to detect if a password shared by the user and the mobile communications device10is entered through the user input device may be enabled and disabled by respective policy messages72received on the mobile communications device10. A related method and server for sending policy messages72to the mobile communications device10is also provided.

It will be appreciated to persons skilled in the art that various alterations, modifications and variations to the particular embodiments described herein are possible. For example, although the data protection security action has been described primarily as the erasure or “wiping” of data60, it will be appreciated that encryption may be used as an alternative to wiping data. In addition, the data60which is subject to the data protection security action may be user application data63(such as that associated with the application modules58), service data61required to establish and maintain communications with the wireless network50, service data61required to establish and maintain communications with the wireless gateway62, or combinations thereof. The erasure or encryption of data60may be performed on some or all of each of the above-described data types, or portions thereof. In addition, in some embodiment some of the data60may be erased and some of the data60may be encrypted. The decision between the data60which is erased and the data60which is encrypted may be based on the type of data. In addition, the security module56may be configurable by the user to erase or encrypt the data60on the storage element24,26. In addition, in some embodiments, where data60is erased the data protection security action may further comprise overwriting (with meaningless data/bits, such as ones or zeroes) the portion of the storage element24,26where the erased data was data60was formerly stored.

While the present application is primarily described as a method, a person of ordinary skill in the art will understand that the present application is also directed to a communications device (such as the mobile communications device described above), for carrying out the disclosed method and including components for performing each described method step, be it by way of hardware components, a computer programmed by appropriate software to enable the practice of the disclosed method, by any combination of the two, or in any other manner. Moreover, an article of manufacture for use with the apparatus, such as a pre-recorded storage device or other similar computer readable medium including program instructions recorded thereon, or a computer data signal carrying computer readable program instructions may direct an apparatus to facilitate the practice of the disclosed method. It is understood that such apparatus (i.e., a communications device such as the mobile communications device described above), articles of manufacture, and computer data signals also come within the scope of the present application. In addition, a communications system comprising a mobile data server and a plurality of mobile communication devices connected via a wireless communication network, in which the mobile data server is configured to implement at least some of the security processes herein described, and in which one or more of the mobile communication devices are configured to implement at least some of the security processes herein described, also comes within the scope of the present application.

The embodiments of the present application described above are intended to be examples only. Those of skill in the art may effect alterations, modifications and variations to the particular embodiments without departing from the intended scope of the present application. In particular, features from one or more of the above-described embodiments may be selected to create alternate embodiments comprised of a subcombination of features which may not be explicitly described above. In addition, features from one or more of the above-described embodiments may be selected and combined to create alternate embodiments comprised of a combination of features which may not be explicitly described above. Features suitable for such combinations and subcombinations would be readily apparent to persons skilled in the art upon review of the present application as a whole. The subject matter described herein and in the recited claims intends to cover and embrace all suitable changes in technology.