(12) United States Patent
`Chiu et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7,870,228 B2
`Jan. 11, 2011
`
`US007870228B2
`
`(54) SYSTEMAND METHOD FOR REMOTELY
`CONTROLLING MOBILE COMMUNICATION
`DEVICES
`
`(75) Inventors: RE hy S.S.; s
`. Godfrey, Waterloo
`; Wen Urao,
`Waterloo (CA)
`(73) Assignee: Research In Motion Limited, Waterloo
`(CA)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 939 days.
`(21) Appl. No.: 10/282,289
`
`(*) Notice:
`
`(22) Filed:
`
`Oct. 28, 2002
`
`(65)
`
`Prior Publication Data
`US 2003/0088.633 A1
`May 8, 2003
`
`Related U.S. Application Data
`(60) Provisional application No. 60/330,652, filed on Oct.
`26, 2001.
`
`(2006.01)
`(2006.01)
`
`51) Int. Cl.
`(51)
`o I5/6
`GO6F 15/173
`(52) U.S. Cl
`709/219; 709/226
`58 Fi ld fici - - - - - ificati- - - - - -s - - - - - - - h- - - - -
`s 709/218
`(58) Field o 7 .. site St. O 8.221.225 2O3, 22 4.
`709,250 226. 455,406 409 41 418 419
`S
`licati
`fil f s
`1
`s
`h hi s
`s
`ee application file for complete search history.
`References Cited
`U.S. PATENT DOCUMENTS
`
`(56)
`
`5,577,100 A * 1 1/1996 McGregor et al. .......... 455,406
`5,734,978 A * 3/1998 Hayatake et al. ............ 455,410
`6,021,433 A * 2/2000 Payne et al. ................. TO9,219
`6,044,265 A
`3/2000 Roach, Jr. ................... 455,419
`6,198.915 B1* 3/2001 McGregor et al. .......... 455,406
`6,199,099 B1* 3/2001 Gershman et al. ........... TO9,203
`
`26
`desktop
`Computer 27
`Configuration
`System
`Exchange
`Sewer
`
`Desktop
`Computer 29
`Configuration
`System
`
`f
`
`4 :
`
`;
`
`
`
`
`
`
`
`6048
`
`Enterprise
`Server
`Remote
`Control
`System
`
`4/2001 Lazaridis et al. ............ TO9,206
`6.219,694 B1
`6,300,863 B1 * 10/2001 Cotichini et al. ............. 340, 5.8
`6,333,684 B1* 12/2001 Kang ......................... 340,72
`6,418,533 B2 * 7/2002 Angelo et al. ................. T26, 19
`6.424,996 B1* 7/2002 Killcommons et al. ...... 709/206
`
`(Continued)
`FOREIGN PATENT DOCUMENTS
`221 1892
`8, 1996
`
`CA
`
`OTHER PUBLICATIONS
`
`CIPO: Office Action issued Nov. 3, 2009 for Canadian Patent Appli
`cation No. 2410114 (4 pages).
`Primary Examiner Ramy MOsman
`Assistant Examiner Sargon N Nano
`(74) Attorney, Agent, or Firm—Jones Day: Krishna K.
`Pathiyal; Robert C. Liang
`(57)
`ABSTRACT
`
`A system for remotely controlling mobile communication
`devices includes a redirection system, a remote control sys
`temand a mobile data communication device. The redirection
`system detects a triggering event at a host system and in
`response to the triggering event continuously redirects data
`items from the host system to a wireless network. The mobile
`data communication device receives data items from the
`wireless network and executes a plurality of device opera
`tions. The remote control system receives control information
`from a user interface and transmits the control information
`through the redirection system to the wireless network. The
`control information is received and executed by the mobile
`data communication device to remotely control one or more
`of the device operations. Methods of controlling the operation
`of mobile data communication devices are also disclosed.
`
`8 Claims, 13 Drawing Sheets
`
`600
`1.
`
`Mobile Dewice with
`Control Message
`Processing System
`24a
`Mobile Dewice with
`Control Message
`Processing System
`24
`
`se
`
`32
`
`Wireless
`Gateway
`V-20
`
`22
`
`Mobile
`Device
`24c
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`US 7,870.228 B2
`Page 2
`
`U.S. PATENT DOCUMENTS
`
`6,446,118 B1* 9/2002 Gottlieb ...................... 709/217
`6,449,305 B1* 9/2002 Menich et al. .
`... 375,141
`6,542,729 B1 * 4/2003 Chimaytelli et al. ......... 455/410
`6,594,682 B2 * 7/2003 Peterson et al. ............. 718/102
`6,633,759 B1 * 10/2003 Kobayashi .....
`455,419
`6,662,023 B1* 12/2003 Helle .........
`455,558
`6,691,162 B1* 2/2004 Wick ..........
`709,224
`6,757,713 B1* 6/2004 Ogilvie et al. .
`... 709/206
`6,771,954 B1* 8/2004 Yoneyama et al. .......... 455/420
`6,779,019 B1 -
`82004 Mousseau et al............ 709,206
`6,804,699 B1 * 10/2004 Henrie .......
`709,203
`6,813,487 B1 * 1 1/2004 Trommelen .
`455,404.1
`6,813,498 B1 * 1 1/2004 Durga et al. ............. 455,456.1
`
`12/2004 Tsimelzon .................. TO9,228
`6,834,306 B1
`6,993,666 B1* 1/2006 Hokkanen et al.
`... T26.5
`6,999,993 B1* 2/2006 Shah et al. .................. 709f2O7
`7,065,347 B1 * 6/2006 Vikse et al. ................. 455,419
`7,099,699 B2 * 8/2006 Jeong ......
`455,565
`7,150,017 B1 * 12/2006 Voglet al. .................. T18, 102
`7.200,220 B1
`4/2007 Yamao ....................... 379,350
`2001/0000777 A1* 5/2001 McGregor et al. .
`455,406
`2001/0004591 A1* 6/2001 Jeong ......................... 455,419
`2001/0013127 A1* 8, 2001 Tomita et al. ................. 7.25/58
`2001/0027478 A1 10, 2001 Meier et al.
`2001/0029.178 A1* 10, 2001 Criss et al. .................. 455,419
`2004/0023695 A1
`2/2004 Zechlin ...................... 455,566
`
`
`
`* cited by examiner
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 1 of 13
`
`US 7,870,228 B2
`
`
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 2 of 13
`
`US 7,870,228 B2
`
`l
`
`
`
`28
`
`
`
`2B
`
`
`
`4
`
`ess'
`).
`A
`^
`
`LOCAL AREANETWORK
`(LAN)
`10B
`SERVER
`COMPUTER
`REDIRECTION SERVER
`SOFTWARE
`30
`i -. FAX OR WOICE
`i
`MACHINE
`
`C
`
`2s b. Erd A 32
`
`20
`
`as
`
`- -
`
`- - DEVICE
`s 24
`
`Fig. 2
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 3 of 13
`
`US 7,870,228 B2
`
`
`
`LOCAL AREA NETWORK (LAN)
`
`14
`
`TCP/IP
`SUB-SYSTEM
`
`S2
`
`NS21
`PRIMARY STORE
`
`E-MAIL
`SUB-SYSTEM
`
`ALTERNATE LINK
`
`MAIN LINK
`
`REDIRECTOR
`PROGRAM
`
`SETUP EVENTS
`TRIGGER
`
`SETUP EVENTS
`TRIGGER
`
`SCREEN SAVER
`SUB-SYSTEM
`
`KEYBOARD
`SUB-SYSTEM
`
`OESKTOP COMPUTER
`
`Fig. 3
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 4 of 13
`
`US 7,870,228 B2
`
`REDIRECTION
`SOFTWARE
`STARTED
`
`
`
`
`
`50
`
`INSTALL TRIGGER
`POINTS IN
`SYSTEM
`
`
`
`WAIT FOR
`MESSAGES AND
`SIGNALS
`
`
`
`IS
`TRIGGER
`FIRED FLAG
`ON ?
`
`-54
`MESSAGE AND
`SIGNALS
`
`
`
`
`
`
`
`
`
`
`
`FORWARD
`TO USER
`
`
`
`
`
`ADO OUTER
`ENVELOPE
`
`
`
`
`
`
`
`
`
`
`
`
`
`Fig. 4
`
`60
`
`SET TRIGGER
`FIRE FLAG
`
`TRIGGER
`SIGNAL
`
`SYSTEM
`ALARM
`
`62
`
`64
`
`66
`
`OTHER
`EVENTS TO BE
`REDIRECTE
`
`NO
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 5 of 13
`
`US 7,870,228 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`-84
`MESSAGE AND
`SIGNALS
`
`
`
`
`
`
`
`80
`MOBILE
`SOFTWARE
`STARTED
`
`WAIT FOR
`MESSAGES AND
`SIGNALS
`
`
`
`98
`ES
`
`REMOVE
`OUTER
`ENVELOPE
`
`MESSAGE
`FROM
`DESTO
`
`
`
`SET DESK TOP
`REDIRECTION
`FLAG ON
`
`88
`COMPOSE AND
`SEND TO DESK TOP
`
`86
`
`USER SIGNAL
`TO START
`REDIRECT9)
`
`90
`
`
`
`EE
`
`lOO
`
`MESSAGE
`TO SEN
`
`SEND TO
`DESTINATION
`ADDRESS
`
`
`
`
`
`
`
`IS USER
`USING DESKTOP
`
`SOF 5.
`
`IS THIS A
`MESSAGE
`REPLY
`
`
`
`
`
`PUT OUTER ENVELOPE
`ON MESSAGE AND
`AODRESS TO DESK TOP
`
`IS DESK TOP
`REDIRECTION
`FLAG ON ?
`
`O2
`
`08
`
`Fig. 5
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 6 of 13
`
`US 7,870,228 B2
`
`CN
`CN
`
`À Zº
`
`8 |
`
`- (-Firewal
`Interface / Gateway Protocol
`(GP) Client
`
`809
`
`:
`
`CD
`O)
`c
`kn
`9
`
`w
`
`B | 09
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 8 of 13
`
`US 7,870,228 B2
`
`--Firewall
`
`Interface?
`GP Client
`
`Interface? Interfacef
`
`-HFirewal
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 9 of 13
`
`US 7,870,228 B2
`
`
`
`Exchange
`Software
`
`MeSSaging
`Server
`(MAPI)
`
`Agent "Site" Computer
`Agent Software
`
`Intra-Computer
`Messaging (MAPI)
`
`Messaging
`Client
`(MAPI)
`
`interface/
`Client
`
`FIG. 9
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 10 of 13
`
`US 7,870,228 B2
`
`SSSAA
`- ZZZZZY
`
`N
`N
`
`co
`
`-CH-Firewall
`
`0 || || ||
`
`Interface / Gateway Protocol (GP)
`Client
`
`80 || ||
`
`0 I "OIH
`
`DL O?
`
`(_)
`
`
`(_)
`
`.9)
`TE
`
`e
`
`| || 0 || ||
`
`
`
`
`
`
`
`
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 11 of 13
`
`US 7,870,228 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`Enterprise
`User Admin
`Service
`
`
`
`Enterprise
`User Admin
`Client
`1202
`
`
`
`sing
`
`Enterprise
`Server/
`Remote Control
`System
`11 O2
`
`FIG. 1
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 12 of 13
`
`US 7,870,228 B2
`
`oos,
`
`1- Firewall
`
`Interface?
`GP Client
`
`Interface? Interface/
`
`--Firewal
`
`Interface
`/Client
`
`O
`InterfaceS
`|Client
`2
`
`|Client
`
`MAP
`
`MAP
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`U.S. Patent
`
`Jan. 11, 2011
`
`Sheet 13 of 13
`
`US 7,870,228 B2
`
`1402
`
`Generate
`Control
`Message
`1404
`
`Transmit
`Control
`Message
`1406
`
`
`
`
`
`Receive
`Control
`Message
`
`Execute
`Command
`
`FIG. 13
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`US 7,870,228 B2
`
`1.
`SYSTEMAND METHOD FOR REMOTELY
`CONTROLLING MOBILE COMMUNICATION
`DEVICES
`
`CROSS-REFERENCE TO RELATED
`APPLICATION
`
`This application claims priority from U.S. Provisional
`Application Ser. No. 60/330,652, filed on Oct. 26, 2001. The
`complete disclosure of this provisional application, including
`drawings, is hereby incorporated into this application by ref
`CCC.
`
`10
`
`FIELD OF THE INVENTION
`
`The present invention is directed toward the field of mobile
`communications. In particular, the system and method of the
`present invention provide for remote control of mobile com
`munication devices. The hand-held mobile communication
`devices may be associated with an event-driven redirection
`computer program ("redirector program') operating at a host
`system, which, upon sensing a particular user-defined event
`has occurred, redirects user-selected data items from the host
`system to the user's mobile communication device. The
`mobile data communication device may be coupled to the
`host system via a wireless network and one or more landline
`networks.
`
`15
`
`25
`
`BACKGROUND
`
`30
`
`35
`
`40
`
`45
`
`Known systems and methods for replicating information
`from a host system to a user's mobile data communication
`device are typically “synchronization systems in which the
`user's data items are warehoused (or stored) at the host sys
`tem for an indefinite period of time and then transmitted in
`bulk only in response to a user request. In these types of
`systems and methods, when replication of the warehoused
`data items to the mobile device is desired, the user typically
`places the mobile device in an interface cradle that is electri
`cally connected to the host system via Some form of local,
`dedicated communication, such as a serial cable oran infrared
`or other type of wireless link. Software executing on the
`mobile data communication device then transmits commands
`via the local communications link to the host system to cause
`the host to begin transmitting the user's data items for storage
`in a memory bank of the mobile device. In these synchroni
`zation schemes, the mobile unit “pulls' the warehoused infor
`mation from the host system in a batch each time the user
`desires to replicate information between the two devices.
`Therefore, the two systems (host system and device) only
`50
`maintain the same data items after a user-initiated command
`sequence that causes the mobile device to download the data
`items from the host system.
`A general problem with these synchronization systems is
`that the only time that the user data items are replicated
`between the host system and the mobile data communication
`device is when the user commands the mobile device to
`download or pull the user data from the host system. At some
`later time a new message could be sent to the user, but the user
`would not receive that message until the next time the user
`fetches the user data items. Thus, a user may fail to respond to
`an emergency update or message because the user only peri
`odically synchronizes the system, such as once per day. Other
`problems with these systems include: (1) the amount of data
`to be reconciled between the host and the mobile device can
`become large if the user does not “synchronize” on a daily or
`hourly basis, leading to bandwidth difficulties, particularly
`
`55
`
`60
`
`65
`
`2
`when the mobile device is communicating via a wireless
`packet-switched network; and (2) reconciling large amounts
`of data, as can accrue in these batch-mode synchronization
`systems, can require a great deal of communication between
`the host and the mobile device, thus leading to a more com
`plex, costly and energy-inefficient system.
`In order to address such disadvantages of pull-based data
`item synchronization systems, the assignee of the instant
`application has developed a more automated, continuous,
`efficient and reliable system and method of ensuring that user
`data items are replicated at a user's mobile communication
`device. User-selected data items or certain portions of the
`selected data items stored at a host system are continuously
`redirected or “pushed to a user's mobile data communica
`tion device upon the occurrence of a user-defined triggering
`event.
`In Such a system, a user's mobile communication device is
`configured for redirection service provided by the host sys
`tem, as well as for mobile communication services provided
`by a communication network operator. Although a user may
`perceive such device services as a single service, redirection
`services and communications services are commonly pro
`vided by differententities. Even when the host system, device
`and redirection service are provided for employee use in a
`corporate environment for example, a corporate information
`technology (IT) or like department can only control host
`system and redirection operations, and must normally inter
`act with a communication network operator or communica
`tions service provider if any type of control of device func
`tions is required. When a corporate user forgets a device
`password that must be entered correctly in order to use the
`device for example, a new password can normally only be set
`by the network operator, not by the corporate IT department.
`Involvement of network operators or external service provid
`ers may significantly complicate and thereby effectively pre
`clude remote control of device operations by a corporate
`client or redirection or other device service provider.
`
`SUMMARY
`
`A system for remotely controlling mobile communication
`devices includes a redirection system, a remote control sys
`temand a mobile data communication device. The redirection
`system detects a triggering event at a host system and in
`response to the triggering event continuously redirects data
`items from the host system to a wireless network. The mobile
`data communication device receives data items from the
`wireless network and executes a plurality of device opera
`tions. The remote control system receives control information
`from a user interface and transmits the control information
`through the redirection system to the wireless network. The
`control information is received and executed by the mobile
`data communication device to remotely control one or more
`of the device operations.
`According to another embodiment of the invention, a
`method for controlling the operation of a mobile data com
`munication device in a communication system, wherein the
`communication system includes a redirection system that
`detects a triggering event at the host system and in response to
`the triggering event continuously redirects data items from
`the host system over a wireless network to the mobile data
`communication device, is also provided. The method com
`prises the steps of configuring the mobile communication
`device to perform a plurality of operations, receiving an
`administrative command that identifies at least one operation
`of the mobile communication device, generating a control
`message corresponding to the administrative command,
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`US 7,870,228 B2
`
`3
`transmitting the control message through the redirection sys
`tem to the wireless network, receiving the control message
`with the mobile data communication device, and in response
`to the control message, automatically executing the adminis
`trative command on the mobile data communication device to
`cause the mobile data communication device to perform the
`identified operation.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a system diagram showing the redirection of user
`data items from a user's desktop PC (host system) to the
`user's mobile data communication device;
`FIG. 2 is a system diagram showing the redirection of user
`data items from a network server (host system) to the user's
`mobile data communication device;
`FIG. 3 is a block diagram showing the interaction of redi
`rector software with other components of the host system in
`FIG. 1:
`FIG. 4 is a flow chart showing the steps carried out by
`exemplary redirector Software operating at the host system;
`FIG. 5 is a flow chart showing an example of steps that may
`be carried out by the mobile data communication device to
`interface with redirector software as represented in FIG. 4.
`operating at the host system;
`FIG. 6 is a block diagram of an example network server
`based redirection system;
`FIG. 7 is a block diagram of an exemplary user adminis
`tration system;
`FIG. 8 is a block diagram of another exemplary network
`server-based distributed redirection system;
`FIG. 9 is a block diagram of an exemplary agent site;
`FIG. 10 is a block diagram showing another example net
`work server-based redirection system;
`FIG. 11 shows another exemplary user administration sys
`tem;
`FIG. 12 is a block diagram of yet another network server
`based distributed redirection system; and
`FIG. 13 is a flow chart showing a method of controlling
`operation of a mobile data communication device.
`
`10
`
`15
`
`25
`
`30
`
`35
`
`40
`
`DETAILED DESCRIPTION
`
`4
`A redirection system or redirector Software program oper
`ating at the host system enables the user to redirect or mirror
`certain user-selected data items (or parts of data items) from
`the host system to the user's mobile data communication
`device upon detecting that one or more user-defined trigger
`ing events has occurred. Also operating at the host system are
`various Sub-systems that may be configured to create trigger
`ing events, such as a screen saver Sub-system or a keyboard
`Sub-system, as well as Sub-systems for repackaging the user's
`data items for transparent delivery to the mobile data device,
`such as a Transmission Control Protocol/Internet Protocol
`(“TCP/IP) sub-system or one or more E-Mail sub-systems.
`Other sub-systems for creating triggering events and repack
`aging the user's data items could also be present at the host
`system. The host system also includes a primary memory
`store where the user's data items are normally stored.
`Using the redirector Software program, the user can select
`certain data items for redirection, Such as E-mail messages,
`calendar events, meeting notifications, address entries, jour
`nal entries, personal reminders etc. Having selected the data
`items for redirection, the user can then configure one or more
`event triggers to be sensed by the redirector program to ini
`tiate redirection of the user data items. These user-defined
`trigger points (or event triggers) include external events,
`internal events and networked events. Examples of external
`events include: receiving a message from the user's mobile
`data communication device to begin redirection; receiving a
`similar message from Some external computer; sensing that
`the user is no longer in the vicinity of the host system; or any
`other event that is external to the host system. Internal events
`could be a calendar alarm, screen saver activation, keyboard
`timeout, programmable timer, or any other user-defined event
`that is internal to the host system. Networked events are
`user-defined messages that are transmitted to the host system
`from another computer coupled to the host system via a
`network to initiate redirection. These are just some of the
`examples of the types of user-defined events that can trigger
`the redirector program to push data items from the host to the
`mobile device. Although it is anticipated that the configura
`tion that specifies which data items will be redirected and in
`what form will be set at the host system, Such configuration
`may be set or modified through data sent from the mobile
`communications device.
`In addition to the functionality noted above, a redirection
`system may provide a set of possibly Software-implemented
`control functions for determining the type of mobile data
`communication device and its address, for programming a
`preferred list of message types that are to be redirected, and
`for determining whether the mobile device can receive and
`process certain types of message attachments, such as word
`processor or Voice attachments. The determination of
`whether a particular mobile device can receive and process
`attachments is initially configured by the user of that mobile
`device at the host system. This configuration can be altered on
`a global or per message basis by transmitting a command
`message from the mobile device to the host system. If the
`redirector is configured so that the mobile data device cannot
`receive and process word processor or Voice attachments,
`then the redirector routes these attachments to an external
`machine that is compatible with the particular attachment,
`Such as an attached printer or networked fax machine or
`telephone. Other types of attachments could be redirected to
`other types of external machines in a similar fashion, depend
`ing upon the capabilities of the mobile device. For example, if
`a user is traveling and receives a message with an attachment
`that the user's mobile device can process or display, the user
`may send a command message from a mobile communica
`
`A host system is a computer where a redirection system or
`redirector Software is operating. The host system may be
`either a user's desktop PC, although, alternatively, the host
`system could be a network server connected to the user's PC
`via a local-area network (“LAN), or could be any other
`system that is in communication with the user's desktop PC.
`Instead of warehousing (or storing) the user's data items at
`the host system and then “synchronizing a mobile data com
`munication device to data items stored at the host system
`when the mobile device requests that such items of informa
`tion be communicated to it, systems in which the present
`invention may be deployed preferably employ a “push’ para
`digm that continuously packages and retransmits the user
`selected items of information to the mobile communication
`device in response to a triggering event detected at the host
`system. Wireless mobile data communications devices, espe
`cially those that can return a confirmation signal to the host
`that the pushed data has been received are especially well
`suited for this type of push paradigm. Due to the bandwidth
`limitations of wireless networks, redirection of only a portion
`of a user-selected data item may be desirable, with the user
`given the option of then retrieving the entire data item (or
`some other portion of the data item) from the host system.
`
`45
`
`50
`
`55
`
`60
`
`65
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`US 7,870,228 B2
`
`10
`
`15
`
`5
`tions device to the host system indicating that that attachment
`is to be sent to a fax machine at a hotel where the user will be
`spending the evening. This enables the user to receive impor
`tant E-mail attachments as long as the host system is provided
`with sufficient information about the destination where the
`attachment is to be forwarded.
`Once an event has triggered redirection of the user data
`items, the host system may then repackage these items in a
`manner that is transparent to the mobile communication
`device, so that information on the mobile device appears
`similar to information on the user's host system. One repack
`aging method includes wrapping the user data items in an
`E-mail envelope that corresponds to the address of the mobile
`data communication device, although, alternatively, other
`repackaging methods could be used, such as special-purpose
`TCP/IP wrapping techniques, or other methods of wrapping
`the user selected data items. The repackaging preferably
`results in E-mail messages generated by the user from the
`mobile device to be transmitted from the host system, thus
`enabling the user to appear to have a single E-mail address,
`Such that the recipients of messages sent from the mobile
`communications device do not know where the user was
`physically located when the message was first sent. The
`repackaging also permits both messages to the mobile device
`and sent from the mobile device to be encrypted and
`decrypted as well as compressed and decompressed.
`In an alternative system and method, a redirection system is
`provided on a network server, and the server is programmed
`to detect numerous redirection event triggers over the net
`work from multiple user desktop computers coupled to the
`server via a LAN. The server can receive internal event trig
`gers from each of the user desktops via the network, and can
`also receive external event triggers, such as messages from
`the users’ mobile data communication devices. In response to
`receiving one of these triggers, the server redirects the user's
`data items to the proper mobile data communication device.
`The user data items and addressing information for a particu
`lar mobile device can be stored at the server or at the user's
`PC. Using this alternative configuration, one redirector pro
`gram can serve a plurality of users. This alternative configu
`ration could also include an Internet- or intranet-based redi
`rector program that could be accessible through a secure
`webpage or other user interface. The redirector program
`could be located on an Internet Service Provider's system and
`accessible only through the Internet.
`In another alternative arrangement, a redirector program
`operates at both the host system and at the user's mobile data
`communication device. The user's mobile device then oper
`ates similarly to the host system described below, and is
`configured in a similar fashion to push certain user-selected
`data items from the mobile device to the user's host system
`(or Some other computer) upon detecting an event trigger at
`the mobile device. This configuration provides two-way
`pushing of information from the host to the mobile device and
`from the mobile device to the host.
`Referring now to the drawings, FIG. 1 is an example sys
`tem diagram showing the redirection of user data items (such
`as message A or C) from a users office PC (host system) 10A
`to the user's mobile data communication device 24, where the
`redirector software 12A is operating at the user's PC. Mes
`60
`sage A in FIG. 1 represents an internal message sent from
`desktop 26 to the user's host system 10A via LAN 14. Mes
`sage C in FIG.1 represents an external message from a sender
`that is not directly connected to LAN 14, such as the user's
`mobile data communication device 24, Some other user's
`mobile device (not shown), or any user connected to the
`Internet 18. Message C also represents a command message
`
`45
`
`6
`from the user's mobile data communication device 24 to the
`host system 10A. As described in more detail in FIG. 3, the
`host system 10 preferably includes, along with the typical
`hardware and Software associated with a workstation or desk
`top computer, the redirector program 12A, a TCP/IP sub
`system 42, a primary message store 40, an E-mail Subsystem
`44, a screen saver Subsystem 48, and a keyboard Subsystem
`46.
`In FIG.1, the host system 10A is the user's desktop system,
`typically located in the users office. The host system 10A is
`connected to a LAN 14, which also connects to other com
`puters 26, 28 that may be in the users office or elsewhere. The
`LAN 14, in turn, is connected to a wide area network
`(“WAN') 18, preferably the Internet, which is defined by the
`use of TCP/IP to exchange information, but which, alterna
`tively could be any other type of WAN. The connection of the
`LAN 14 to the WAN18 is via high bandwidth link 16, typi
`cally a T1 or T3 connection. The WAN18 in turn is connected
`to a variety of gateways, via connections 32. A gateway forms
`a connection or bridge between the WAN 18 and some other
`type of network, such as an RF wireless network, cellular
`network, satellite network, or other synchronous or asynchro
`nous landline connection.
`In the example of FIG. 1, a wireless gateway 20 is con
`nected to the Internet for communicating via wireless link 22
`to a plurality of wireless mobile data communication devices
`24. Also shown in FIG. 1 is machine 30, which could be a
`FAX machine, a printer, a system for displaying images (such
`as video), a machine capable of processing and playing audio
`files, such as a voice mail system, or some other type of
`peripheral system or device. Certain message attachments
`may be redirected to such an external machine 30 if the
`redirector program configuration data reflects that the mobile
`device 24 cannot receive and process the attachments, or if the
`user has specified that certain attachments are not to be for
`warded to mobile device 24, even if such device can process
`those attachments. By way of example, consider an E-mail
`sent to a user that includes three attachments—a word pro
`cessing document, a video clip and an audio clip. The redi
`rection program could be configured to send the text of the
`E-mail to the remote device, to send the word processing
`document to a networked printer located near the user, to send
`the video clip to a store accessible through a secure connec
`tion through the Internet and to send the audio clip to the
`user's voice mail system. This example is not intended to be
`limiting, but rather to illustrate the variety of possibilities
`embodied in the redirection concept.
`The mobile data communication device 24 may be a hand
`held two-way wireless paging computer, a wirelessly enabled
`palm-top computer, a mobile telephone with data messaging
`capabilities, or a wirelessly enabled laptop computer, but
`could, alternatively be other types of mobile data communi
`cation devices capable of sending and receiving messages via
`a network connection 22. Although the system may operate in
`a two-way communications mode, certain aspects of the redi
`rection could be beneficially used in a “one and one-half or
`acknowledgment paging environment, or even with a one
`way paging system. The mobile data communication device
`24 may be configured, for example via Software program
`instructions, to work in conjunction with the redirector pro
`gram 12A to enable the seamless, transparent redirection of
`user-selected data items. FIG. 4 describes the basic method
`steps of an example redirector program, and FIG.5 describes
`the steps of a corresponding program which may be operating
`at the mobile device 24.
`In an alternative system not explicitly shown in the draw
`ings, the mobile device 24 also includes a redirector program.
`
`25
`
`30
`
`35
`
`40
`
`50
`
`55
`
`65
`
`Hafeman, Exhibit 2029
`Google LLC et al. v. Hafeman
`IPR2022-01191
`
`

`

`US 7,870,228 B2
`
`7
`User selected data items can be replicated from the host to the
`mobile device and Vice versa. The configuration and opera
`tion of the mobile device 24 having a redirector program is
`similar to that described herein with respect to FIGS. 1-5.
`A user can preferably configure the redirector program
`12A to push certain user-selected data items to the user's
`mobile data communication device 24 when the redirector
`12A detects that a particular user-defined event trigger (or
`tri