System and method for monitoring and maintaining a wireless device

Description of equivalent WO 2006132924 A2

SYSTEM AND METHOD FOR MONITORING AND MAINTAINING A

WIRELESS DEVICE

BACKGROUND

0004Field of the Invention

0005[0001] This invention relates generally to the field of network data

0006services. More particularly, the invention relates to an apparatus and

0007method for monitoring and maintaining a wireless device.

0008Description of the Related Art

0009[0002] A variety of wireless data processing devices have been

0010introduced over the past several years. These include wireless personal

0011digital assistants ("PDAs") such as the Palm® VIIx handheld, cellular

0012phones equipped with data processing capabilities (e.g., those which include

0013wireless application protocol ("WAP") support), and, more recently,

0014wireless messaging devices such as the Blackberry™ wireless pager

0015developed by Research In Motion ("RIM").™

0016[0003] Mobile platforms included on the wireless data processing

0017devices run mission-critical applications. As such, it is important to gather

0018information about applications running on the device, protect the data on

0019the device, and protect the applications on the device. Furthermore, there may be requirements that certain prerequisite applications be present or

0020absent on the mobile platform to enforce an organization's policies, to secure

0021the mobile platform, or to permit auditing procedures.

0022[0004] Presently, some applications operate to scan a device and remove

0023certain files according to criteria contained in the application. For example,

0024a virus scanner operates in such a way. However, virus scanners only scan

0025for known objects on the device, and not for the absence of certain objects.

0026Furthermore, virus scanners only check for the existence of viruses, and not

0027for generic things such as battery strength or device peripheral functionality.

0028[0005] Also, because the virus scanner application resides on the device

0029on which it operates, it cannot check itself to ensure that it is running

0030properly. Furthermore, virus scanners only accept rules from the vendor of

0031the application, and do not have the functionality to allow organizations

0032other than the vendor to generate and enforce rules to fit the organization's

0033corporate policy.

0034[0006] Currently, existing products or technology in the market do not

0035gather device information and enforce the existence or non-existence of

0036applications on the device. Accordingly, what is needed is a system and

0037method for monitoring and maintaining a wireless device. What is also needed is a network infrastructure to support remote monitoring and

0038maintenance of a wireless device.

SUMMARY

0040[0007] A system is disclosed in which a data processing device is

0041monitored and maintained over a network. One embodiment of the system

0042comprises a wireless device including: a service to maintain data objects,

0043provide messaging capability, and provide data access capability on behalf

0044of a user of the wireless device; and a rules engine communicatively coupled

0045to the service to execute a set of rules transmitted to the wireless device from

0046a server, the set of rules to instruct the rules engine to gather information

0047related to the wireless device and to take action on the wireless device based

0048on the gathered information.

0049[0008] In another embodiment, a system is disclosed comprising a server

0050communicatively coupled to a network, and an administrator coupled to the

0051server configured to provide a set of rules to a wireless device, the set of

0052rules to instruct the wireless device to gather information related to the

0053wireless device and take action based on the gathered information.

BRIEF DESCRIPTION OF THE DRAWINGS

0055[0009] A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:

0056[0010] FIG. 1 illustrates an exemplary network architecture used to implement embodiments of the present invention;

0057[0011 ] FIG. 2 illustrates one embodiment of a network architecture used to implement an application checker;

0058[0012] FIG. 3 is a flow diagram depicting one embodiment of a method of the present invention;

0059[0013] FIG. 4 is a flow diagram depicting another embodiment of a method of the present invention; and

0060[0014] FIG. 5 is a flow diagram depicting a further embodiment of a method of the present invention.

DETAILED DESCRIPTION

0062[0015] In the following description, for the purposes of explanation,

0063numerous specific details are set forth in order to provide a thorough

0064understanding of the present invention. It will be apparent, however, to one

0065skilled in the art that the present invention may be practiced without some

0066of these specific details. In other instances, well-known structures and

0067devices are shown in block diagram form to avoid obscuring the underlying

0068principles of the present invention.

AN EXEMPLARY NETWORK ARCHITECTURE

0070[0016] Figure 1 illustrates one embodiment of a network architecture

0071for implementing the techniques described herein. The "customer site" 120

0072illustrated in Figure 1 may be any local-area or wide-area network over

0073which a plurality of servers 103 and clients 110 communicate. For example,

0074the customer site may include all servers and clients maintained by a single

0075corporation. The servers 103 may be configured to provide a variety of

0076different messaging and groupware services 102 to network users (e.g., e-

0077mail, instant messaging, calendaring, . . . etc). In one embodiment, these

0078services are provided by Microsoft Exchange.™ However, the underlying

0079principles of the invention are not limited to any particular

0080messaging/groupware platform. [0017] In one embodiment of the invention, an interface 101 forwards

0081data objects maintained by the service 102 (e.g., e-mail messages, instant

0082messages, calendar data, . . . etc) to a plurality of wireless data processing

0083devices (represented in Figure 1 by wireless device 130) via an external data

0084network 170 and/or a wireless service provider network 171. For example, if

0085the service 102 includes an e-mail database, the interface 101 transmits any

0086new e-mails which arrive in a user's mailbox on the service 102 to the user's

0087wireless data processing device 130 (over the network(s) 170 and/or 171).

0088[0018] Alternatively, or in addition, the service 102 may provide the e-

0089mail to the user's local computer (e.g., client 110) upon request (i.e., so that

0090the user will receive the e-mail on his/her wireless device 130 when out of

0091the office and on his/her personal computer 110 when in the office).

0092Conversely, e-mail messages sent from the user's wireless data processing

0093device 130 are transmitted to the service 102 via the interface 101.

0094[0019] In one embodiment, the interface 101 is a software module

0095adapted to work with the particular service 120. It should be noted,

0096however, that the interface 101 may be implemented in hardware or any

0097combination of hardware and software while still complying with the

0098underlying principles of the invention. [0020] In one embodiment, the external data network 170 is comprised

0099of a plurality of servers/clients (not shown) and other networking hardware

0100(e.g., routers, hubs, . . . etc) for transmitting data between the interface 101

0101and the wireless devices 130. In one embodiment, the interface 101

0102encapsulates data in one or more packets containing an address identifying

0103the wireless devices 130 (e.g., such as a 24-bit Mobitex Access Number

0104("MAN #")). The external data network 170 transmits the packets to a

0105wireless service provider network 171 which, in turn, transmits the packets

0106(or the data contained therein) over a wireless communication link to the

0107wireless device 130. In one embodiment, the wireless service provider

0108network is a 2-way paging network. However, various other network types

0109may be employed (e.g., CDMA 2000, PCS, . . . etc) while still complying with

0110the underlying principles of the invention.

0111[0021 ] It should be noted that the network service provider network

0112171 and the external data network 170 (and associated interface 101) may be

0113owned/ operated by the same organization or, alternatively, the

0114owner/operator of the external data network 170 may lease wireless services

0115from the wireless service provider network. The underlying principles of

0116the invention are not limited to any particular service arrangement. [0022] In one embodiment of the invention, the service 102 (e.g., the e-

0117mail database) is fully synchronized with the wireless data processing

0118device 130. Thus, any actions performed on the wireless device 130 are

0119automatically updated on the service 102 and any transactions occurring at

0120the service 102 are automatically reflected on the device 130.

0121Synchronization updates of this type may include but are not limited to

0122device configuration modifications, calendar updates, e-mail message

0123updates, instant messages, to-do list updates and/or any other type of

0124personal information management transactions or corporate data

0125management transactions (hereinafter "message transactions").

0126[0023] As one example, when a user views an e-mail message using the

0127device 130, an indication that the user viewed the message is transmitted to

0128the service 102 (via the interface 101). Accordingly, if the user subsequently

0129connects to e-mail via a client 110, the e-mail will appear as having already

0130been viewed. Other actions such as message deletions, filing activities (e.g.,

0131moving a message to a particular folder), message responses, meeting

0132confirmations/additions . . . etc, will automatically be reflected in the service

0133102, thereby providing complete synchronization between the service 102,

0134the device 130 and/or the client 110 (if one is being used). [0024] Current systems do not offer organizational control over

0135monitoring their wireless devices for various criteria, and maintaining the

0136wireless devices based on the monitoring. As such, these systems cannot

0137gather device information and enforce organizational policies on the

0138wireless devices. One reason for this is that prior systems do not monitor

0139the entire wireless device unit remotely, and any monitoring is not done

0140based on organizational policies. As such, in order for an organization to

0141monitor and maintain its wireless devices, embodiments of the invention

0142employ one or more of the following techniques.

AN EXEMPLARY WIRELESS DEVICE MONITOR

0144[0025] Figure 2 is a block diagram illustrating one embodiment of a

0145system 200 to monitor and maintain a wireless device. System 200 includes

0146a wireless device 210, a network 220, and a server 230. In one embodiment,

0147system 200 may be implemented as system 100 of Figure 1. Network 220

0148may be the same as data network 170 and wireless service provider network

0149171, individually and/or in combination. Also, a firewall may be utilized

0150between the network 220 and server 230. System 200 may be used to

0151implement monitoring and maintenance of the wireless device 210.

0152[0026] Wireless device 210 further includes a mobile platform

0153application 212 and a rules engine 214. In one embodiment, the application 212 provides wireless messaging and data access for the wireless device 210

0154in connection with a main server, such as server 230. Server 230 may be

0155maintained by an organization that owns and operates the wireless device

0156210. In one embodiment, application 212 operates as a service to maintain

0157data objects on behalf of a user of the wireless device 210. Application 212

0158may also provide real-time synchronization of the wireless device 210 with

0159server 230. In one embodiment, application 212 is a software module

0160adapted to work with server 230.

0161[0027] In one embodiment, application 212 receives a rule definition file

0162sent to the wireless device 210 through a wireless or wired medium. This

0163rule definition file may be created by an organization owning the wireless

0164device, and sent to the wireless device 210 by way of server 230, which may

0165be operated by the organization. The rule definition file embodies a set of

0166rules to be applied to the wireless device. In one embodiment, application

0167212 transfers the rule definition file to rules engine 214 for analysis and

0168execution.

0169[0028] The rules engine 214 of the wireless device 210 stores and

0170executes the rule definition file. In one embodiment, the rules engine 214

0171operates to verify authenticity of any rule definition files it receives. This

0172verification may be accomplished by determining the origination of the rule definition file and cross-referencing the origination with a list of allowable

0173entities.

0174[0029] Based on the rule definition file, the rules engine 214 monitors

0175the wireless device 210 by gathering information relating to the wireless

0176device 210, and checking information associated with one or more

0177applications on the wireless device 210. Wireless device information that the

0178rules engine 214 may gather includes, but is not limited to, applications

0179installed on the device, applications not installed on the device, and

0180functionally operative features within applications installed on the device.

0181Furthermore, the information gathered may include device characteristics

0182such as OS version, ROM version, application licensing restrictions and their

0183expiry, code signature and certification validation of applications,

0184application usage patterns, device hardware characteristics, device operating

0185characteristics, peripherals on the device, and SMS functionality.

0186[0030] In one embodiment, the rules engine 214 may also take action

0187based on the results from monitoring of the wireless device 210 by way of

0188the rule definition file. Such actions may include, but are not limited to,

0189warning the device user, locking the device, phoning a set of numbers,

0190initiating software downloads and upgrades, alerting the corporate network

0191monitors, shutting down applications, shutting down the device, and erasing critical data on the device. Furthermore, the rules engine may take

0192action and enforce device system characteristics based on corporate policies

0193promulgated by an organization owning the wireless device 210.

0194[0031] In one embodiment, rules engine 214 is a software module

0195adapted to work with application 212. It should be noted, however, that the

0196rules engine 214 may be implemented in hardware or any combination of

0197hardware and software while still complying with the underlying principles

0198of the invention.

0199[0032] In one embodiment, server 230 may be configured to provide a

0200variety of different messaging and groupware services to network users

0201(e.g., e-mail, instant messaging, calendaring, . . . etc) such as wireless device

0202210. In one embodiment, these services are provided by Microsoft

0203Exchange.™ In one embodiment, server 230 is the same as server 103 of

0204Figure 1. In another embodiment, server 230 may be a synchronization

0205server such as GoodLink™ server of Good Technology, Inc. of Santa Clara,

0206CA.

0207[0033] Server 230 further includes an administrator 240 and an

0208organization policy editor 245 as part of the administrator 240. The

0209administrator 240 is responsible for assembling and transmitting the rule definition file to the wireless device 210. In one embodiment, the rule

0210definition file is any set of rules to be applied to the wireless device 210. The

0211rule definition file may be an Extensible Markup Language (XML) file,

0212native script, executable module, or a pointer (URL) to another resource of

0213the rule definition file. In one embodiment, any changes or updates made to

0214the rule file may be incrementally synchronized with the wireless device.

0215[0034] In one embodiment, the corporate policy editor 245 is

0216responsible for transforming corporate policies for the wireless device 210

0217into the set of rules for the rule definition file. Some examples of corporate

0218policies include, but are not limited to, allowing or not allowing certain

0219applications to exist on the wireless device, maintaining particular settings

0220within applications, ensuring certain versions of applications are up-to-date,

0221and preventing certain peripherals from being associated with the wireless

0222device. One skilled in the art will appreciate that a variety of corporate

0223policies may be implemented to monitor and maintain the wireless device

0224210.

0225[0035] In one embodiment, administrator 240 is a software module

0226adapted to work with server 230. It should be noted, however, that the

0227administrator 240 may be implemented in hardware or any combination of hardware and software while still complying with the underlying principles

0228of the invention.

0229[0036] Figure 3 is a flow diagram of one embodiment of a method 300

0230to monitor and maintain a wireless device. Method 300 may be

0231implemented in a system such as that described with respect to Figure 2. At

0232processing block 310, a rule definition file is received at the wireless device

0233210. In one embodiment, the mobile platform application 212 receives the

0234file and routes it to the rules engine 214. At processing block 320, the rules

0235engine 214 verifies the authenticity of the rule definition file.

0236[0037] Then, at processing block 330, the rules engine executes the rule

0237definition file. Upon execution of the file, the rules engine 214 may gather

0238information related to the wireless device. The information gathered may

0239include, but is not limited to, applications installed on the device,

0240applications not installed on the device, functionally operative features

0241within applications installed on the device, and battery status. Furthermore,

0242the information gathered may include device characteristics such as OS

0243version, ROM version, application licensing restrictions and their expiry,

0244code signature and certification validation of applications, application usage

0245patterns, device hardware characteristics, device operating characteristics,

0246peripherals on the device, and SMS functionality. [0038] Finally, at processing block 340 the rules engine 214 performs an

0247action based on the execution of the rule definition file. Such an action may

0248include, but is not limited to, warning the device user, locking the device,

0249phoning a set of numbers, initiating software downloads and upgrades,

0250alerting the corporate network monitors, shutting down applications,

0251shutting down the device, and erasing critical data on the device.

0252[0039] Figure 4 is a flow diagram of one embodiment of a method 400

0253to receive a rule definition file at the rules engine 214. At processing block

0254410, the rules engine 214 determines whether a periodic monitoring session

0255of the wireless device 210 is required. The monitoring session may be the

0256same process as described with respect to Figure 3. In one embodiment,

0257such a periodic monitoring session may occur at various time intervals

0258including, upon start-up of the wireless device, once a day, once a week, and

0259upon installation of any components or applications on the wireless device.

0260One skilled in the art will appreciate that a variety of monitoring time

0261intervals may be implemented by the rules engine 214.

0262[0040] If a periodic monitoring session is required, then at processing

0263block 420 the rules engine 214 informs the mobile platform application 212

0264of the wireless device 210 to check for an update with server 230. At

0265processing block 430, the application 212 connects to the server 230 to determine if an updated rule definition file exists. In some embodiments,

0266the application 212 or server 230 may compare the rule definition file

0267already on the wireless device 210 with the most recent rule definition file on

0268the server 230.

0269[0041] If a more recent rule definition file exists on the server 230, then

0270at processing block 440 the updated file is downloaded to the wireless

0271device 210. At processing block 450, the monitoring session is initiated. In

0272one embodiment, the monitoring session is the same process as described

0273with respect to Figure 3.

0274[0042] Figure 5 is a flow diagram of another embodiment of a method

0275500 to receive a rule definition file at a rules engine. In some embodiments,

0276in lieu of the wireless device 210 determining whether an updated rule

0277definition file exists, the server 230 may automatically synchronize any

0278updated rule definition file with the wireless device's 210 file. The following

0279description illustrates this process.

0280[0043] At processing block 510, the server 230 updates the rule

0281definition file stored on the server 230. Then, at processing block 520, the

0282server incrementally synchronizes changes to the file with the wireless

0283device 210. Such synchronization may occur over a wired or wireless medium. Finally, at processing block 530, the rules engine 214 initiates a

0284monitoring session according to the new rule definition file received from

0285the server 230. In some embodiments, the rules engine 214 may initiate the

0286monitoring session when it receives an updated file, and/or it may initiate

0287monitoring session on a periodic basis, according to some of the example

0288time intervals mentioned previously.

0289[0044] Embodiments of the invention may include various steps as set

0290forth above. The steps may be embodied in machine-executable

0291instructions. The instructions can be used to cause a general-purpose or

0292special-purpose processor to perform certain steps. Alternatively, these

0293steps may be performed by specific hardware components that contain

0294hardwired logic for performing the steps, or by any combination of

0295programmed computer components and custom hardware components.

0296[0045] Elements of the present invention may also be provided as a

0297machine-readable medium for storing the machine-executable instructions.

0298The machine-readable medium may include, but is not limited to, floppy

0299diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs,

0300RAMs, EPROMs, EEPROMs, magnetic or optical cards, Flash memory,

0301propagation media or other type of media/machine-readable medium

0302suitable for storing electronic instructions. For example, the present invention may be downloaded as a computer program which may be

0303transferred from a remote computer (e.g., a server) to a requesting computer

0304(e.g., a client) by way of data signals embodied in a carrier wave or other

0305propagation medium via a communication link (e.g., a modem or network

0306connection).

0307[0046] Throughout the foregoing description, for the purposes of

0308explanation, numerous specific details were set forth in order to provide a

0309thorough understanding of the invention. It will be apparent, however, to

0310one skilled in the art that the invention may be practiced without some of

0311these specific details. For example, while illustrated as an interface 101 to a

0312service 102 executed on a server 103 (see Figure 1), it will be appreciated that

0313the underlying principles of the invention may be implemented on a single

0314client in which the client transmits data over a network. Moreover, although

0315described in the context of a wireless data processing device, the underlying

0316principles of the invention may be implemented to compress data in

0317virtually any networking environment, both wired and wireless.

0318Accordingly, the scope and spirit of the invention should be judged in terms

0319of the claims which follow. /