111111
`
`1111111111111111111111111111111111111111111111111111111111111111111111111111
`US 20050257209Al
`
`(19) United States
`(12) Patent Application Publication
`Adams et al.
`
`(10) Pub. No.: US 2005/0257209 Al
`Nov. 17, 2005
`( 43) Pub. Date:
`
`(54) SYSTEM AND METHOD OF OWNER
`APPLICATION CONTROL OF ELECTRONIC
`DEVICES
`
`(76)
`
`Inventors: Neil P. Adams, Waterloo (CA);
`Michael G. Kirkup, Waterloo (CA);
`Herbert A. Little, Waterloo (CA);
`Russell N. Owen, Waterloo (CA)
`
`Publication Classification
`
`(51)
`Int. CI? ....................................................... G06F 9/44
`(52) U.S. Cl. ............................................ 717/168; 717/174
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`John V. Biernacki, Esq.
`JONES DAY
`North Point
`901 Lakeside Avenue
`Cleveland, OH 44114 (US)
`
`(21)
`
`Appl. No.:
`
`11/118,844
`
`(22) Filed:
`
`Apr. 29, 2005
`
`Related U.S. Application Data
`
`(60) Provisional application No. 60/567,163, filed on Apr.
`30, 2004.
`
`Systems and methods of owner application control of an
`electronic device are provided. Owner application control
`information is stored on the electronic device and/or one or
`more remote servers. Owner application control information
`is consulted to determine if one or more required applica(cid:173)
`tions are available for execution on the electronic device. If
`not, one or more required applications not available are
`downloaded and installed. This could be in a manner trans(cid:173)
`parent to the user of the electronic device. If one or more
`required applications are not available on the electronic
`device, the device can be functionally disabled in whole, or
`in part, until one or more required applications are available.
`
`220
`
`INFORMATION
`OWNER
`INSERTION POINT
`(BRANDING POINT)
`
`230
`
`OWNER CONTROL
`INFORMA TJON
`INSERTION POINT
`(CONTROL POINT)
`
`224
`
`222
`
`234
`
`232
`
`21&
`
`210
`
`212
`
`OWNER
`INFORMA TJON
`STORE
`
`214
`
`OWNER CONTROL
`INFORMATION
`STORE
`
`ELECTRONIC DEVICE
`
`BLACKBERRY EX. 1004, pg. 1
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 1 of 9
`
`US 2005/0257209 A1
`
`CORPORATE LAN
`
`WIRELESS
`NETWORK
`GATEWAY
`
`16
`
`20
`
`24
`
`12
`
`COMPUTER
`SYSTEM
`
`14
`
`MOBILE
`OEV ICE
`
`22
`
`BLACKBERRY EX. 1004, pg. 2
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 2 of 9
`
`US 2005/0257209 Al
`
`220 ?
`
`INFORMATION
`OWNER
`INSERTION POINT
`(BRANDING POINT)
`
`L230
`
`OWNER CONTROL
`INFORMATION
`INSERTION POINT
`(CONTROL POINT)
`
`OWNER
`INFORMATION
`SOURCE
`
`_;224
`
`OWNER CONTROL
`INFORMATION
`SOURCE
`
`\.._ 234
`
`v222
`
`INTERFACE/
`CONNECTOR
`
`INTERFACE/ v232
`CONNECTOR
`
`v2lo
`
`INTERFACE/
`CONNECTOR
`
`0
`
`lf21
`
`212/
`
`OWNER
`INFORMATION
`STORE
`
`l (214
`
`OWNER CONTROL
`INFORMATION
`STORE
`
`ELECTRONIC DEVICE
`
`Fig. 2
`
`BLACKBERRY EX. 1004, pg. 3
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 3 of 9
`
`US 2005/0257209 Al
`
`64\_
`
`60 (
`
`INSERTION TOOL
`
`) 52
`
`OWNER
`INFORMATION
`STORE
`
`INTERFACE/
`CONNECTOR
`
`TO
`WIRELESS
`NETWORK
`
`\30
`
`WIRELESS
`TRANSCEIVER
`
`50 (
`
`INTERFACE/
`CONNECTOR
`
`) 44
`
`INSERTION
`MODULE
`T
`
`\_ 48
`
`46
`
`42?
`
`Ul
`
`) 40
`
`PROCESSOR I
`
`APPLICATION
`LOADER
`I
`
`!
`
`TO OTHER
`DEVICE
`SYSTEMS
`
`34?
`
`SOFTWARE
`APPLICATIONS
`
`35/
`
`38}
`
`OWNER
`INFORMATION
`STORE
`MEMORY
`
`AUTHORIZATION
`RECORD
`STORE
`
`(32
`
`MOBILE DEVICE
`
`Flg. 3
`
`BLACKBERRY EX. 1004, pg. 4
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 4 of 9
`
`US 2005/0257209 Al
`
`72
`
`74
`
`ESTABLISH OWNER
`INFORMATION
`
`SIGN AND SEND
`OWNER
`INFORMATION
`TO DEVICE
`
`NO
`
`78
`
`YES
`
`CHECK
`DIGITAL
`SIGNATURE
`
`82
`
`ERROR
`PROCESSING
`
`NO
`
`YES
`
`84
`
`INSERT OWNER
`INFORMATION
`
`BLACKBERRY EX. 1004, pg. 5
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 5 of 9
`
`US 2005/0257209 Al
`
`92
`
`ESTABLISH OWNER
`CONTROL
`INFORMATION
`
`94
`
`SIGN AND SEND
`OWNER CONTROL
`INFORMATIOM
`TO DEVICE
`
`CHECK
`DIGITAL
`SIGNATURE
`
`96
`
`100
`
`ERROR
`PROCESSING
`
`NO
`
`102
`
`INSERT
`ES
`>--y ~ OWNER CONTROL
`INFORMATION
`
`BLACKBERRY EX. 1004, pg. 6
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 6 of 9
`
`US 2005/0257209 Al
`
`110
`
`RECEIVE
`OPERATION
`REQUEST
`
`NO
`
`YES
`
`YES
`
`YES
`
`ERROR
`PROCESSING
`
`NO
`
`NO
`
`120
`
`ERROR
`PROCESSING
`
`122
`
`PERFORM
`OPERATION
`
`BLACKBERRY EX. 1004, pg. 7
`
`

`

`5248
`
`\
`
`~
`
`MODULE
`
`•
`•
`•
`52~
`OTHER SOfTWARE
`MODULES
`
`519+ r-~~~~-~-~~;-~~--~~t~~[;-~~-;;-~~ -;: ... -------------------------------------------------------------------------------------------- --
`/I DATA COMMUNICA liON I \
`'- 522
`
`'...,..__ ___ ____,
`NON-VOLATILE
`MEMORY
`
`~SERIAL PORT
`
`530
`
`//
`' ' ' /
`
`/
`
`••
`
`•• MICROPROCESSOR
`
`lc
`
`•I KEYBOARD
`
`532
`
`538
`{ 511
`------ -----------------------------~
`I :
`
`I
`I
`I
`I
`I
`I
`I
`I
`
`CONTROL
`
`514
`
`~ TRANSMITTER lc
`
`SIGNALS
`
`CONTROL
`
`,
`
`534
`
`536
`
`~ MICROPHONE
`
`OTHER DEVICE
`SUBSYSTEMS
`
`SHORT-RANGE
`COMMUNICATIONS
`
`542
`
`540
`
`I
`I
`-------------------------------------------------------------------------------------------------------------------------------------------~
`
`Ft9. 7
`
`500[
`
`(')
`
`~ .....
`
`""C
`~ .....
`~ = .....
`~ 't:l -....
`.... 0 =
`~
`0' -....
`.... 0 =
`
`(')
`
`~ .....
`
`z
`0
`~
`'"""'
`~-..J
`N c c
`
`Ul
`
`'JJ. =(cid:173)~
`~ .....
`-..J
`0 ......,
`'0
`
`Cj
`'JJ.
`
`N c c
`~ c
`
`N
`Ul
`-..J
`N c
`'0
`>
`'"""'
`
`BLACKBERRY EX. 1004, pg. 8
`
`

`

`Patent Application Publication Nov. 17, 2005 Sheet 8 of 9
`
`US 2005/0257209 Al
`
`REQUIRED
`AVAILABLE
`?
`
`DISABLE DEVICE
`OPE RAT ION
`
`DOWNLOAD
`MISSING
`APPLICATION
`
`810
`
`820
`
`840
`
`DEVICE
`OPERATES .,._ ___ ____,J
`NORMALLY
`
`Fig. 8
`
`BLACKBERRY EX. 1004, pg. 9
`
`

`

`I
`
`! Version
`i Policy Set
`i Disposition! Delivery Mechanism
`:Application
`T------------------------------------------------,-----------------------~----------------,--------------------------,-------------------------------
`i Wire I ine Only
`i N/A
`i <Use Latest>
`: [:±] ~ SystePI Software
`: Required
`LitJ_I?J_ ~!-~'!~~_r _______________________________ J __ ~~1~! ~~ _ !~!-~ ~ ~~?..-L. -~~g,_u_i_~~~- ____ j_ ~~! ~-~!~~-_Q~ _11 ________ J. _ ~!-~ ________________________ _
`t------------------------------------------------,-----------------------~----------------,--------------------------,-------------------------------
`l ________ El_~-~~{~~~--~~~~~~~L~~~!<__~g~ __ j __ ~~1~!~_!11 __ !~!-~~~~?.._l __ ~~g,_u_i_~~~-----L'!~!~-~!~~--Q~_l1 ________ j __ ~!-~-------------------------
`i
`i <SystePI Version> i Required
`i Wireline Only
`[±J~WTLS Security Package
`iN/A
`i <SystePI Version> i Required
`i Wire! ine Only
`·------------------------------------------------~-----------------------~----------------~--------------------------~-------------------------------
`i N/A
`:[±]~Phone
`~-~-~-H~-;~P~d------------------------------l--<s~;i~~-v~~-;i~~-;-r--opti-o~~~-----l--~i~~~i~~--6~1-y ________ ! __ N/_i ________________________ _
`T------------------------------------------------,----1------------------r----------------,--------------------------,-------------------------------
`i
`i Wire I i ne On I y
`i <Sys te111 Version>
`i N/A
`[:±] ~ 950/957
`: Optional
`T------------------------------------------------,-----------------------~----------------,--------------------------,-------------------------------
`:
`[±] ~ 6200 Series
`: <Sys te111 Version>
`: Wi rei i ne On I y
`: N/A
`: Optional
`+------------------------------------------------~-----------------------~----------------1--------------------------1-------------------------------
`:
`[±] ~ 6700 Series
`: <Sys te111 Version>
`: Optional
`: Wire I i ne On I y
`: N/A
`t------------~--------------------------------i-----------------------~----------------;--------------------------;-------------------------------
`:
`[:±] ~ 7200 Series
`: <Syste111 Version>
`: Optional
`: Wirel ine Only
`: N/A
`~------------------------------------------------~-----------------------~----------------~--------------------------~-------------------------------
`:
`t±J ~ 7700 Series
`Q~
`1
`1
`1
`1
`1
`: <Syste111 Version>
`: Optional
`: Wirel ine Only
`: N/A
`r-~-~-r~-;ks---------------------------------~--<s1f;ie~-ve~-;i~~-;-r--opti-~~~~-----~--~i~E!Ii~e--a~l-i ________ 1 __ N/ji ________________________ _
`i------- ·rrn~ -&ioii-s;~-;;;------------------- -l--~5;; ~ ;~ --y ;r_s_i_;~; ----f-op; i ;~~~------T -wi;; i i~;- a~ I;-----------T-Ni;;-------------------------(cid:173)
`
`;--------t±J-~-6ioo-s;~-;;~--------------------l--~s;~~;~-v~;;~;~;----:--op;i;~~~------l--wi;;ii~;-o~i;-----------l--N;;;--------------------------
`T------------------------------------------------,-----------------------~----------------,--------------------------,-------------------------------
`:
`[:±] ~ 7200 Series
`: <Syste111 Version>
`: Optional
`: Wirel ine Only
`: N/A
`+------------------------------------------------~-----------------------~----------------~--------------------------~-------------------------------
`:
`[±] ~ 7700 Series
`: <Syste111 Version>
`: Optional
`: Wirel ine Only
`: N/A
`t------------------------------------------------~-----------------------j----------------~--------------------------~--------~--------------------1
`: EJ ~Calender and Tasks
`: <Syste111 Version> : Optional
`: Wirel ine Only
`: N/A
`:
`~--------t±J-~-95o/957 ________________________ i __ ~s;~~~~-v~;;~;~;----r-lopti~~~~f~f---i--wi;;i;~;-o~ly ___________ i __ N/A____________ ------------1
`i-[±J-~-~~-~e~~-ai_H_os-Aj)p-------------------~--~:()-----------------r-lieq~-i~ed-----~--~i~~~ess---------------1--ini-ernili-Aj)p-Po-iici-e;---1
`r-[±J-~-RI14cel_i ______________________________ l __ <A-~r>---------------r--opti-~~~~-----~-~i~~~e55 _______________ ! __ £~i-er~iii-Ailp-Po-iici-;5---1
`
`i-E±J-~-RI-Hie~--------------------------------1--<A-~y;---------------:--opii-~~~~-----i-~i~E!ie55---------------i--£~i-er~iii-Aj)p-Po-iici~;---1
`T------------------------------------------------,-----------------------~----------------,--------------------------,-------------------------------,
`
`I
`I
`
`1
`1
`
`I
`I
`
`I
`I
`
`I
`I
`
`I
`I
`
`+------------------------------------------------~-----------------------~----------------1--------------------------~-------------------------------l
`
`I
`I
`
`1
`1
`
`I
`I
`
`I
`I
`
`I
`I
`
`I
`I
`
`~------------------------------------------------~-----------------------~----------------~--------------------------~-------------------------------J
`
`Ft9. 9
`
`(')
`
`~ .....
`
`""C
`~ .....
`~ = .....
`~ 't:l -....
`.... 0 =
`~
`0' -....
`.... 0 =
`
`(')
`
`~ .....
`
`z
`0
`~
`"""'
`~-..J
`N c c
`
`Ul
`
`900
`
`'JJ. =-~
`~ .....
`'0
`0 ......,
`'0
`
`Cj
`'JJ.
`
`N c c
`~ c
`
`N
`Ul
`-..J
`N c
`'0
`>
`"""'
`
`BLACKBERRY EX. 1004, pg. 10
`
`

`

`US 2005/0257209 A1
`
`Nov. 17, 2005
`
`1
`
`SYSTEM AND METHOD OF OWNER
`APPLICATION CONTROL OF ELECTRONIC
`DEVICES
`
`[0008] FIG. 3 is a block diagram of an electronic device
`in which a system and method of owner control are imple(cid:173)
`mented.
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application claims priority to and the benefit
`of U.S. Provisional Application Ser. No. 60/567,163, filed on
`Apr. 30, 2004, of which the entire disclosure (including any
`and all figures) is incorporated herein by reference.
`
`[0002] This application claims priority to and the benefit
`of U.S. application Ser. No. 10/732,132 (entitled "System
`and method of owner control of electronic devices" filed
`Dec. 10, 2003), which claims priority to U.S. provisional
`patent application Ser. No. 60/432,610 (entitled "System and
`method of owner control of electronic devices" filed Dec.
`12, 2002). By this reference, the full disclosure, including
`the drawings, of U.S. application Ser. Nos. 60/432,610 and
`10/732,132, are incorporated herein by reference.
`
`BACKGROUND
`
`[0003] This system relates generally to electronic devices,
`and in particular to controlling application installation of
`such devices by a device owner.
`
`In a corporate environment, employees are often
`[0004]
`provided with access to office supplies and equipment to be
`used in performing job functions. Standard equipment typi(cid:173)
`cally includes at least a personal computer (PC), and may
`also include wireless mobile communication devices and
`other types of electronic devices. Although such equipment
`is intended primarily for business or work-related purposes,
`users sometimes make personal use of office equipment.
`Employers may be comfortable with some degree of per(cid:173)
`sonal use of such equipment, provided that the personal use
`does not interfere with normal job functions, does not incur
`additional costs, and conforms with company policies.
`
`In these types of situations, a user of an electronic
`[0005]
`device is not the owner of the device, and the user and owner
`may have different perceptions of acceptable device uses.
`Acceptable uses may be specified in company policies, for
`example, which employees are expected to follow, but
`beyond company policy statements, a corporate device
`owner often has little if any control over how electronic
`devices are ultimately used. According to one known
`scheme for controlling operation of electronic devices, an
`owner loads a policy file onto a device to restrict the type of
`operations or software applications that may be executed by
`the device. However, this type of scheme is sometimes
`circumvented by a user by either deleting the owner policy
`file or replacing the owner policy file with a user policy file
`which may include fewer restrictions than the owner policy
`file. Therefore, there remains a need for a system and
`method of owner application control of electronic devices.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0006] FIG. 1 is a block diagram showing a communica(cid:173)
`tion system in which electronic devices are used.
`
`[0007] FIG. 2 is a block diagram illustrating a system of
`inserting owner information and owner control information
`onto an electronic device.
`
`[0009] FIG. 4 is a flow diagram illustrating a method of
`inserting owner information onto an electronic device.
`
`[0010] FIG. 5 is a flow diagram illustrating a method of
`inserting owner control information onto an electronic
`device.
`
`[0011] FIG. 6 is a flow diagram showing a method of
`owner control of an electronic device.
`
`[0012] FIG. 7 is a block diagram of a wireless mobile
`communication device as an example of an electronic
`device.
`
`[0013] FIG. 8 is a flow diagram illustrating a method of
`device initialization of required applications.
`
`[0014] FIG. 9 depicts an exemplary user interface on a
`remote server for an owner to designate application control
`information for dissemination to particular devices, or
`groups of devices.
`
`DETAILED DESCRIPTION
`
`[0015] FIG. 1 is a block diagram showing a communica(cid:173)
`tion system in which electronic devices are used. The
`communication system 10 includes a Wide Area Network
`(WAN) 12, coupled to a computer system 14, a wireless
`network gateway 16 and a Local Area Network (LAN) 18.
`The wireless network gateway 16 is also connected to a
`wireless communication network 20 in which a wireless
`mobile communication device 22 ("mobile device"), is
`configured to operate.
`
`[0016] The computer system 14 is a desktop or laptop PC,
`which is configured to communicate to the WAN 12, the
`Internet for example. PCs, such as the computer system 14,
`normally access the Internet through an Internet Service
`Provider (ISP), Application Service Provider (ASP) or the
`like.
`
`[0017] The LAN 18 is an example of a typical working
`environment, in which multiple computers 28 are connected
`in a network. It is normally located behind a security firewall
`24. Within the LAN 18, a message server 26, operating on
`a computer behind the firewall 24, acts as the primary
`interface for the corporation to exchange messages both
`within the LAN 18, and with other external messaging
`clients via the WAN 12. Known message servers include, for
`example, Microsoft™ Exchange Server and Lotus
`Domino TM. The LAN 18 includes multiple computer sys(cid:173)
`tems 28, each of which implements a messaging client, such
`as Microsoft Outlook™, Lotus Notes™, Yahoo!™ Messen(cid:173)
`ger, AOL Instant Messenger, or other client-server or peer(cid:173)
`to-peer, or similar messaging clients with various architec(cid:173)
`tures. Messages received by the message server 26 are
`distributed to mailboxes for user accounts addressed in the
`received messages, and are then accessed by a user through
`a messaging client operating on a computer system 28. The
`fact that the example given illustrates a client-server archi(cid:173)
`tecture in no way implies that such architecture is necessary,
`as other architectures may be used.
`
`[0018] Although only a message server 26 is shown in the
`LAN 18, those skilled in the art will appreciate that a LAN
`
`BLACKBERRY EX. 1004, pg. 11
`
`

`

`US 2005/0257209 Al
`
`Nov. 17, 2005
`
`2
`
`may include other types of servers supporting resources that
`are shared between the networked computer systems 28, and
`that the message server 26 may also provide additional
`functionality, such as dynamic database storage for data such
`as, but not limited to, calendars, to-do lists, task lists, e-mail
`and documentation. The message server 26 and electronic
`messaging are described for illustrative purposes only.
`Owner control systems and methods are applicable to a wide
`range of electronic devices, and are in no way limited to
`electronic devices with messaging capabilities.
`
`[0019] The wireless gateway 16 provides an interface to a
`wireless network 20, through which messages may be
`exchanged with a mobile device 22. Such functions as
`addressing of the mobile device 22, encoding or otherwise
`transforming messages for wireless transmission, and any
`other interface functions are performed by the wireless
`gateway 16. The wireless gateway 16 may be configured to
`operate with more than one wireless network 20, in which
`case the wireless gateway 16 also determines a most likely
`network for locating a given mobile device 22 and possibly
`track mobile devices as users roam between countries or
`networks.
`
`[0020] The mobile device 22 is, for example, a data
`communication device, a voice communication device, a
`dual-mode communication device such as many modern
`cellular telephones having both data and voice communica(cid:173)
`tions functionality, a multiple-mode device capable of voice,
`data and other types of communications, a personal digital
`assistant (PDA) enabled for wireless communications, or a
`laptop or desktop computer system with a wireless modem.
`
`[0021] Any computer system with access to the WAN 12
`may exchange messages with the mobile device 22 through
`the wireless network gateway 16. Alternatively, private
`wireless network gateways such as wireless Virtual Private
`Network (VPN) routers could be implemented to provide a
`private interface to a wireless network. A wireless VPN
`router implemented in the LAN 18 provides a private
`interface from the LAN 18 to one or more mobile devices
`such as 22 through the wireless network 20. A private
`interface to a mobile device 22 may also effectively be
`extended to entities outside the LAN 18 by providing a
`message forwarding or redirection system that operates with
`the message server 26. Such a message redirection system is
`disclosed in U.S. Pat. No. 6,219,694, which is hereby
`incorporated into this application by reference. In this type
`of system, incoming messages received by the message
`server 26 and addressed to a user of a mobile device 22 are
`sent through the wireless network interface, either a wireless
`VPN router, the wireless gateway 16, or another interface,
`for example, to the wireless network 20 and to the user's
`mobile device 22. Another alternate interface to a user's
`mailbox on a message server 26 may be a Wireless Appli(cid:173)
`cation Protocol (WAP) gateway. Through a WAP gateway, a
`list of messages in a user's mailbox on the message server
`26, and possibly each message or a portion of each message,
`may be sent to the mobile device 22.
`
`[0022] A wireless network 20 normally delivers messages
`to and from communication devices such as the mobile
`device 22 via RF transmissions between base stations and
`devices. The wireless network 20 may, for example, be a
`data-centric wireless network, a voice-centric wireless net(cid:173)
`work, or a dual-mode network that can support both voice
`
`and data communications over the same infrastructure.
`Recently developed networks include Code Division Mul(cid:173)
`tiple Access (CDMA) networks and General Packet Radio
`Service (GPRS) networks. So-called third-generation (3G)
`networks like Enhanced Data rates for Global Evolution
`(EDGE) and Universal Mobile Telecommunications Sys(cid:173)
`tems (UMTS) are currently under development. Older data(cid:173)
`centric networks include, but are not limited to, the Mobi(cid:173)
`tex™ Radio Network ("Mobitex"), and the DataTAC™
`Radio Network ("DataTAC"). Voice-centric data networks
`such as Personal Communication System (PCS) networks,
`including Global System for Mobile Communications
`(GSM) and Time Division Multiple Access (TDMA) sys(cid:173)
`tems, have been available in North America and world-wide
`for several years.
`
`In the system 10, a company that owns the LAN 18
`[0023]
`may provide a computer system 28 and/or a mobile device
`22 to an employee. When a computer system 28 issued to an
`employee is a laptop computer, for example, the computer
`system 28 may be used either within or outside the corporate
`LAN 18. When the computer system is operating within the
`LAN 18, non-local operations may be restricted by config(cid:173)
`uring permissions and restrictions for the computer system
`28, a network account of the user, or both, in such a way that
`the permissions and restrictions are not configurable by the
`user. However, if a user is using a computer outside the LAN
`18, by connecting the computer to the WAN 12 as shown at
`14, for example, network-based controls in place at the LAN
`18 can sometimes be bypassed.
`
`In order to maintain control over an electronic
`[0024]
`device such as the computer system 28 or mobile device 22,
`an owner may establish local settings directly on the device.
`Such local settings control device operations, but only as
`long as the settings remain intact on the device. A common
`problem with this type of control mechanism is that local
`settings may be deleted, replaced, or otherwise altered by a
`user.
`
`In some instances, the owner control information
`[0025]
`can include one or more applications lists. The application
`lists provide owner control of application installation and
`deletion on the electronic device. As an example, application
`lists can address different types of applications, such as but
`not limited to:
`[0026] Required applications: These applications
`must be present on the device before the user may
`use the device; alternatively, one or more operations
`of the device can be disabled until such applications
`are available for execution on the device. This will
`allow the owner to install audit and remote admin(cid:173)
`istrative applications. The user can in some imple(cid:173)
`mentations be prevented from deleting these appli(cid:173)
`cations. This list may be small.
`[0027] Allowable (or authorized) applications: These
`applications may or may not be present on a device.
`Thus the user is free to download these applications
`if they desire the functionality that the application
`provides. This list may be small.
`[0028] Excluded applications: These applications
`may not be present on a device. Presumably an
`excluded application is a malicious application, or
`otherwise undesirable application. This list is poten(cid:173)
`tially large.
`
`BLACKBERRY EX. 1004, pg. 12
`
`

`

`US 2005/0257209 Al
`
`Nov. 17, 2005
`
`3
`
`[0029] With respect to allowed and/or required applica(cid:173)
`tions, even if the applications are required or allowed on the
`device, the owner may want to impose restriction on opera(cid:173)
`tions that such applications can perform. For instance, the
`owner may want to control functionality such as:
`
`[0030] 1) Is the application allowed to open network
`connections inside the firewall (e.g., via MDS)?
`
`[0031] 2) Is the application allowed to open network
`connections outside the firewall (e.g., v1a WAP,
`device TCP, SMS)?
`
`[0032] 3) Is the application allowed to open local
`connections (e.g., serial, IR, or USB connections)?
`
`[0033] 4) Is the application allowed to interact with
`other processes? Is the application allowed to access
`a Runtime Store or a Persistent Store?
`
`[0034] 5) Is the application allowed access to a
`telephone API (e.g., to make phone calls)?
`
`[0035] FIG. 2 is a block diagram illustrating a system of
`inserting owner information and owner control information
`onto an electronic device; such an insertion system may be
`used in one or more implementations of the described owner
`application control systems and methods. The foregoing
`explanation is therefore exemplary in nature. The system in
`FIG. 2 includes an electronic device 210, an owner infor(cid:173)
`mation insertion point 220, and an owner control informa(cid:173)
`tion insertion point 230. The owner information insertion
`point 220 is alternatively referred to as a branding point,
`while the owner control insertion point 230 is alternatively
`referred to as a control point. An owner information store
`212, an owner control information store 214, and an inter(cid:173)
`face/connector 216 are provided in the electronic device
`210. The owner information insertion point 220 includes an
`owner information source 224 and an interface/connector
`222. The owner control information insertion point 230
`similarly includes an owner control information source 234
`and an interface/connector 232.
`[0036] The owner information store 212 stores informa(cid:173)
`tion, such as an owner name or other identification infor(cid:173)
`mation, for example, which identifies an owner of the
`electronic device 210. The owner control information store
`214 stores information that is used to control the operation
`of the electronic device 210. Owner control information
`may, for example, be specified in an authorization record
`that lists software applications authorized to be installed and
`executed on the electronic device 210; authorization records
`can further constrain operations performed by installed
`applications. The use of owner control information to con(cid:173)
`trol operations of an electronic device is described in further
`detail below. The owner information source 224 and the
`owner control information source 234 could be local
`memory devices, communication modules through which
`remote memory devices storing owner information and
`owner control information are accessible, or possibly user
`interfaces through which owner information and owner
`control information are entered.
`[0037] The interface/connector 222 is compatible with the
`interface/connector 216 to establish a communication link
`between the owner information insertion point 220 and the
`electronic device 210, to thereby enable owner information
`to be transferred to the electronic device 210 from the owner
`
`information source 224. The interface/connector 232 simi(cid:173)
`larly enables transfer of owner control information from the
`owner control information source 234 onto the electronic
`device 210 via a communication link established between
`the interface/connectors 232 and 216. The interface/connec(cid:173)
`tors 216, 222, and 232 may establish wired communication
`links, where the interface/connectors are serial ports, for
`example, or wireless communication links such as infrared
`links where the interface/connectors are infrared modules.
`Owner information and owner control information trans(cid:173)
`ferred to a device are respectively inserted or stored in the
`owner information store 212 and the owner control infor(cid:173)
`mation store 214.
`[0038] The owner control insertion point 220 is associated
`with an owner of the electronic device 210. Where the
`electronic device 210 is provided to a user by an employer,
`for example, the owner control insertion point 220 may be
`a computer system or device controlled by a corporate
`computer system administrator or IT department. The elec(cid:173)
`tronic device 210 is "branded" with owner information by
`establishing a communication link between the owner infor(cid:173)
`mation insertion point 220 and the electronic device 210
`through the interface/connectors 222 and 216 and then
`inserting owner information into the owner information
`store 212. Unless otherwise desired, once owner information
`has been inserted onto the mobile device 210, then there can
`be a configuration such that only the owner or a party
`authorized by the owner is able to change the owner infor(cid:173)
`mation or insert or change owner control information on the
`electronic device 210.
`[0039] Because insertion of owner control information
`onto the electronic device 210 is restricted once owner
`information has been inserted, the owner control informa(cid:173)
`tion insertion point 230 need not necessarily be controlled
`by the owner of the electronic device 210. When the owner
`maintains control over the owner control information inser(cid:173)
`tion point 230, the insertion points 220 and 230 may be
`implemented in the same computer system or device and
`share the same interface/connector. However, separate inser(cid:173)
`tion points 220 and 230 as shown in FIG. 2 allow an owner
`of the electronic device to delegate owner control informa(cid:173)
`tion insertion to a trusted entity. If owner control information
`insertion is controlled using digital signatures, for example,
`as described in further detail below, an owner first brands the
`electronic device 210 and provides the electronic device 210
`and digitally signed owner control information to a user. In
`this case, the owner control information insertion point 230
`may be the user's computer system, which is then used to
`insert the digitally signed owner control information onto
`the electronic device 210.
`
`[0040]
`In most implementations, the owner information
`insertion point 220 and the owner control information con(cid:173)
`trol point 230 include the same type of interface/connectors
`222 and 232, compatible with the interface/connector 216 in
`the electronic device 210. However, the electronic device
`210 may alternatively include multiple interface/connectors,
`such that different types of interface/connectors may be
`implemented at an owner information insertion point 220
`and an owner control information insertion point 230.
`Although only a single owner control information insertion
`point 220 and owner control information insertion point 230
`are shown in FIG. 2, a complete insertion system may
`include more than one of each type of insertion point. In a
`
`BLACKBERRY EX. 1004, pg. 13
`
`

`

`US 2005/0257209 Al
`
`Nov. 17, 2005
`
`4
`
`large company, for example, corporate computer system
`administrators may be authorized to perform owner infor(cid:173)
`mation insertion operations from administrator computer
`systems, or from any corporate computer system from which
`administrative functions can be accessed, thereby providing
`multiple owner information insertion points 220. Similarly,
`when an owner allows users to insert digitally signed owner
`control information onto electronic devices, as described
`above, each user's computer system may be used as an
`owner control information insertion point 230.
`
`[0041] The systems and methods of owner application
`control can use the
`insertion structures and methods
`described above; however, so long as owner control infor(cid:173)
`mation store is capable of storing a required application list,
`and in some instances an allowed application list and/or an
`excluded application list, the particular control information
`insertion system and method can vary significantly, and use
`any conventional insertion/interfacing technology, without
`impacting the owner application control systems and meth(cid:173)
`ods discussed herein.
`
`[0042] FIG. 3 is a block diagram of an electronic device
`in which a system and method of owner application control
`can be implemented. In FIG. 3, the electronic device is a
`mobile device 30 adapted to operate within a wireless
`network. Also shown in FIG. 3 is an insertion tool 64 used
`to insert owner information onto the mobile device 30.
`
`It should be apparent to those skilled in the art that
`[0043]
`only the components involved in an owner control system
`are shown in FIG. 3. A mobile device typically includes
`further components in addition to those shown in