US 7,962,622 B2Grant
System and method for providing provisioning and upgrade services for a wireless device
Issue Date:2011-06-14
•15 Claims
•8 Drawing Sheets
Abstract
In one embodiment, a system is disclosed. The system includes a wireless data processing device, a messaging service to maintain data objects on behalf of a user, and a data center, coupled to the wireless device and the messaging service. The data center establishes a plurality of routing connections between the wireless device and the messaging service. Each of the plurality of connections corresponds to a data service level authorized by the data center.
Metadata
Assignee
- Motorola Mobility, Inc.
Inventors
- John Friend
- Michael Belshe
- David Hoffman
Application Information
Application Number:US 10/400,970
Filing Date:2003-03-27
Priority Date:2001-08-07
Art Unit:2442
Classifications
IPC:
G06F15/16
Patent Drawings (8 sheets)
Description
PRIORITY
[0001] This application is a continuation-in-part of U.S. application entitled SYSTEM AND METHOD FOR FULL WIRELESS SYNCHRONIZATION OF A DATA PROCESSING APPARATUS WITH A DATA SERVICE, application Ser. No. 10/109,928, filed Mar. 29, 2002 now U.S. Pat. No. 7,243,163, which is a continuation-in-part of U.S. application entitled APPARATUS AND METHOD FOR CONSERVING BANDWIDTH BY BATCH PROCESSING DATA TRANSACTIONS, application Ser. No. 09/924,283, filed Aug. 7, 2001 now U.S. Pat. No. 7,155,483.
COPYRIGHT NOTICE
[0002] Contained herein is material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent disclosure by any person as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights to the copyright whatsoever.
FIELD OF THE INVENTION
[0003] This invention relates generally to the field of network data services. More particularly, the invention relates to an apparatus and method for synchronizing a wireless data processing device with a wireless messaging service.
BACKGROUND
[0004] A variety of wireless data processing devices have been introduced over the past several years. These include wireless personal digital assistants (“PDAs”) such as the Palm® VIIx handheld, cellular phones equipped with data processing capabilities (e.g., those which include wireless application protocol (“WAP”) support), and, more recently, wireless messaging devices such as the Blackberry™ wireless pager developed by Research In Motion (“RIM”).™
[0005] Personal digital assistants such as the Palm devices typically provide only limited wireless messaging capabilities (e.g., instant messaging and basic Internet access). For example, these devices typically require a user to manually establish a connection to the Internet via an Internet Service Provider (“ISP”) or to a corporate server to check e-mail messages.
[0006] Although corporate messaging systems such as the RIM Blackberry provide more comprehensive messaging capabilities, there are significant limitations to these systems. Specifically, these systems employ e-mail “redirection” or “forwarding” techniques in which messages are redirected to the wireless device only if certain conditions are met. These conditions, referred to as “redirection events,” may include, for example, an indication that the user is not working at his corporate desktop (e.g., removal of the wireless device from the desktop cradle, a screen saver firing on the desktop, . . . etc) or a manual redirection command initiated by the user (e.g., via the wireless device or the corporate desktop). One such message redirection system is described in U.S. Pat. No. 6,219,694 (“System and Method for Pushing Information From a Host System to a Mobile Data Communication Device Having a Shared Electronic Address”).
[0007] As a result, these systems are (as a practical matter) incapable of providing complete synchronization between the wireless device and the corporate e-mail database. For example, because messages are only redirected to the wireless device under certain conditions (e.g., following a redirection event), at any given point in time, the wireless device may contain an incomplete set of e-mail data. Moreover, even when messages are actively being forwarded to the wireless device, the e-mail data stored at the wireless device and the e-mail database are not truly synchronized. For example, certain types of transactions performed on the wireless device, such as an indication that a message has been viewed by the user, message deletions, movement of messages from one folder to another, . . . etc., are not updated at the e-mail service wirelessly.
[0008] Moreover, only basic e-mail functions such as sending and receiving messages may be controlled at the wireless device. More advanced e-mail management functions must be set at the user's desktop (e.g., configuring e-mail filters, outgoing e-mail signatures, security settings such as passwords, . . . etc).
[0009] In addition, prior messaging systems require a corporate desktop to which the device must be attached when the user is in the office. The problem with this is not merely that a corporate desktop is required, but also that the corporate desktop must be configured with software and a proprietary “cradle” that allows it to communicate directly to the wireless device.
[0010] Accordingly, what is needed is a system and method for providing complete synchronization and management between a wireless device and a messaging service (e.g., a corporate e-mail account). What is also needed is a wireless apparatus for receiving and sending e-mail messages, which does not require a corporate desktop or any software to be installed and executed on the corporate desktop.
SUMMARY
[0011] According to one embodiment, a method is described. The method includes receiving identification (ID) information from a messaging service at a data center to initiate a wireless data service between the messaging service and a wireless device. The method also includes the data center establishing one or more routing connections between the wireless device and the messaging service. Each of the one or more routing connections corresponds to a data service component authorized by the data center.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:
[0013] FIG. 1 illustrates an exemplary network architecture used to implement elements of the present invention;
[0014] FIG. 2 illustrates one embodiment of a flow diagram for initiating service between a server and a wireless device;
[0015] FIG. 3 illustrates one embodiment of network connections between a wireless device and a server;
[0016] FIG. 4 is a flow diagram illustrating one embodiment of upgrading service at a wireless device;
[0017] FIG. 5 illustrates another embodiment of data network connections between a wireless device and a server;
[0018] FIG. 6 illustrates yet another embodiment of data network connections between a wireless device and a server; and
[0019] FIG. 7 illustrates one embodiment of a computer system.
DETAILED DESCRIPTION
[0020] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form to avoid obscuring the underlying principles of the present invention.
[0021] Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
An Exemplary Network Architecture
[0022] FIG. 1 illustrates one embodiment of a network architecture. A “customer site” 120 illustrated in FIG. 1 may be any local-area or wide-area network over which a plurality of servers 103 and clients 110 communicate. For example, customer site 120 may include all servers and clients maintained by a single corporation.
[0023] Servers 103 may be configured to provide a variety of different messaging and groupware services 102 to network users (e.g., e-mail, instant messaging, calendaring, . . . etc). In one embodiment, these services are provided by Microsoft Exchange.™ However, the underlying principles of the invention are not limited to any particular messaging/groupware platform.
[0024] In one embodiment, an interface 100 forwards data objects maintained by service 102 (e.g., e-mail messages, instant messages, calendar data, . . . etc) to a plurality of wireless data processing devices (represented in FIG. 1 by wireless device 130) via an external data network 170 and/or a wireless service provider network 171. For example, if the service 102 includes an e-mail database, the interface 100 transmits any new e-mails, which arrive in a user's mailbox on the service 102 to the user's wireless data processing device 130 (over the network(s) 170 and/or 171).
[0025] Alternatively, or in addition, the service 102 may provide the e-mail to the user's local computer (e.g., client 110) upon request (i.e., so that the user will receive the e-mail on his/her wireless device 130 when out of the office and on his/her personal computer 110 when in the office). Conversely, e-mail messages sent from the user's wireless data processing device 130 are transmitted to the service 102 via the interface 100.
[0026] In one embodiment, the interface 100 is a software module adapted to work with the particular service 102. It should be noted, however, that interface 100 may be implemented in hardware or any combination of hardware and software while still complying with the underlying principles of the invention.
[0027] In one embodiment, the external data network 170 is comprised of a plurality of databases, servers/clients (not shown) and other networking hardware (e.g., routers, hubs, . . . etc) for transmitting data between the interface 100 and the wireless devices 130. In one embodiment, the interface 100 encapsulates data in one or more packets containing an address identifying the wireless devices 130 (e.g., such as a 24-bit Mobitex Access Number (“MAN #”)).
[0028] The external data network 170 transmits the packets to a wireless service provider network 171, which in turn, transmits the packets (or the data contained therein) over a wireless communication link to the wireless device 130. In one embodiment, the wireless service provider network is a 2-way paging network. However, various other network types may be employed (e.g., CDMA 2000, GPRS, PCS, . . . etc) while still complying with the underlying principles of the invention.
[0029] It should be noted that the network service provider network 171 and the external data network 170 (and associated interface 100) may be owned/operated by the same organization or, alternatively, the owner/operator of the external data network 170 may lease wireless services from the wireless service provider network. The underlying principles of the invention are not limited to any particular service arrangement.
Service Initiation
[0030] According to one embodiment, wireless service to a device 130 is initiated by downloading software to the device 130. In such an embodiment, the device 130 is coupled directly to client 110 and initialized by installing the applicable software. The direct connection between wireless device 130 and client 110 may be a wired or wireless (e.g., Bluetooth) connection. According to a further embodiment, no further configuration is required. Particularly, the device 130 user is not required to take any further action to begin service.
[0031] FIG. 2 illustrates one embodiment of a flow diagram for initiating service between interface 100 and a wireless device 130. At processing block 210, interface 100 connects with data network 170 before the software has been downloaded to device 130. At processing block 220, interface 100 downloads a serial number for the wireless device 130 to data network 170. Thus, interface 100 indicates to data network 170 that the particular device 130 is authorized to access server 103.
[0032] Subsequently, the wireless device 130 is turned on for the first time. Thus, at processing block 230, device 130 requests data network 170 to establish a connection with server 103 by providing the network address and the serial number. At processing block 240, data network 170 compares the identification information received from the wireless device and the identification information received from interface 100 in order to validate whether the device 130 is authorized to access server 103 based upon data received from interface 100.
[0033] In addition, data network 170 compares the identification information with a valid service plan that has been previously established for the device at purchase time. Once the service for the device 103 is authorized, data network 170 establishes one or more connections between wireless device 130 and interface 100.
[0034] According to one embodiment, a permanent connection is established at data network 170 for each type of service, e.g., email, calendar address book, etc. The connections represent routing information (e.g., a connection ID) that is in used to deliver service specific messages to and from device 130. FIG. 3 illustrates one embodiment of data network 170 routing connections between a wireless device 130 and a server 103. In the illustrated embodiment, connections 0, 1, 2 and 3 are established between wireless device 130 and a server 103.
[0035] In one embodiment, each connection within data network 170 represents a wireless service authorized by a service plan provided to data network 170. According to one embodiment, connection 0 is a channel defined to be a provisioning service that is used to establish other services The provisioning service validates the authentication of device 130 each time device 130 attempts to provision on the network. In addition, the provisioning service verifies the service plan associated with the wireless device 130.
[0036] In a further embodiment, connection 1 represents an e-mail service, connection 2 represents a calendar service and connection 3 represents an address book service. As described above, each connection stored in network 170 is permanent. Consequently, subsequent communication between device 130 and server 103 are made faster and more efficient. According to one embodiment each connection is private, thus, guaranteeing that messages are only sent or received by devices and servers that have previously established connections.
Service Adjustment
[0037] According to one embodiment, a wireless device 130 user's service may be upgraded/downgraded without configuration of wireless device 130. Accordingly, it is not necessary for a user to take action to establish the new service plan. FIG. 4 is a flow diagram illustrating one embodiment of upgrading (or downgrading) service at a wireless device 130.
[0038] Referring to FIG. 4 , service adjustment information (e.g., upgrade or downgrade) is downloaded at data network 170, processing block 410. According to one embodiment, the service information is downloaded to data network 170 from server 103. However, in other embodiments, the service information may be downloaded from other sources, such as a third party server, or may be entered directly into a database associated with data network 170.
[0039] At processing block 420, data network 170 transmits a message to the wireless device 130 indicating that a new service plan has been established for the device 130. At processing block 430, the device 130 accesses data network 170 to ascertain the service adjustments. At processing block 440, information corresponding to the service change is transmitted from data network 170 to the wireless device 130. As a result, services are added to (or deleted from) wireless device 130. At processing block 450, routing connections at data network 170 are updated based upon the service change.
[0040] FIG. 5 illustrates one embodiment of data network 170 upgraded routing connections between a wireless device 130 and a server 103. Referring to FIG. 5 , connections 4, 5 and 6 are added to connections 0-3. In one embodiment, connection 4 represents a second e-mail account, connection 5 represents a third email account and connection 6 represents a fax service.
[0041] In a further embodiment, the additional e-mail accounts (e.g., connection 4 and connection 5) enable a user to access accounts having different e-mail addresses. FIG. 6 illustrates one embodiment of data network 170 downgraded routing connections between a wireless device 130 and a server 103. Referring to FIG. 6 , connections 2 and 3 have been deleted, indicating that the service plan only authorizes one e-mail account in addition to the provisioning service.
Exemplary Computer System
[0042] FIG. 7 illustrates a computer system 700 on which wireless device 130 and or server 103 may be implemented. Computer system 700 includes a system bus 720 for communicating information, and a processor 710 coupled to bus 720 for processing information. According to one embodiment, processor 710 is implemented using one of the multitude of Motorola DragonBall MC68328-family of microprocessors. Nevertheless one of ordinary skill in the art will appreciate that other processors may be used.
[0043] Computer system 700 further comprises a random access memory (RAM) or other dynamic storage device 725 (referred to herein as main memory), coupled to bus 720 for storing information and instructions to be executed by processor 710. Main memory 725 also may be used for storing temporary variables or other intermediate information during execution of instructions by processor 710. Computer system 700 also may include a read only memory (ROM) and/or other static storage device 726 coupled to bus 720 for storing static information and instructions used by processor 710.
[0044] A data storage device 725 such as a magnetic disk or optical disc and its corresponding drive may also be coupled to computer system 700 for storing information and instructions. Computer system 700 can also be coupled to a second I/O bus 750 via an I/O interface 730. A plurality of I/O devices may be coupled to I/O bus 750, including a display device 724, an input device (e.g., an alphanumeric input device 723 and/or a cursor control device 722).
[0045] The communication device 721 is for accessing other computers (servers or clients) via network 170. The communication device 721 may comprise a modem, a network interface card, or other well-known interface device, such as those used for coupling to Ethernet, token ring, or other types of networks.
[0046] Embodiments of the invention may include various steps as set forth above. The steps may be embodied in machine-executable instructions. The instructions can be used to cause a general-purpose or special-purpose processor to perform certain steps. Alternatively, these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.
[0047] Elements of the present invention may also be provided as a machine-readable medium for storing the machine-executable instructions. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, propagation media or other type of media/machine-readable medium suitable for storing electronic instructions. For example, the present invention may be downloaded as a computer program which may be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., a modem or network connection).
[0048] Throughout the foregoing description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention may be practiced without some of these specific details. For example, while illustrated as an interface 100 to a service 102 executed on a server 103 (see FIG. 1 ), it will be appreciated that the underlying principles of the invention may be implemented on a single client in which the client transmits data over a network.
[0049] Moreover, although described in the context of a wireless data processing device, the underlying principles of the invention may be implemented to compress data in virtually any networking environment, both wired and wireless. Accordingly, the scope and spirit of the invention should be judged in terms of the claims which follow.
Claims
What is claimed is:
1. A method comprising:
receiving identification (ID) information from a messaging service at a data center to activate a wireless device for initial wireless data service between the messaging service and a wireless device;
the data center receiving ID information from the wireless device as a component of a first time request to connect with the messaging service;
activating wireless data service between the messaging service and the wireless device by establishing a first permanent connection to deliver a first type of message service, and a second permanent connection to deliver a second type of message service between the messaging service and the wireless device if the ID information received from the messaging service matches the ID information received from the wireless device.
2. The method of claim 1 wherein activating the wireless data service comprises the data center establishing first and second routing connections between the wireless device and the messaging service.
3. The method of claim 2 wherein each of the first and second routing connections correspond to a data service component authorized by the data center.
4. The method of claim 3 wherein the data center compares the ID information received from the wireless device to the ID information received from the messaging service to determine if the wireless device is authorized to connect with the messaging service.
5. The method of claim 1 wherein the ID information comprises serial number of the wireless device.
6. The method of claim 1 wherein each of the one or more routing connections are permanent.
7. The method of claim 6 wherein each of the one or more routing connections are private.
8. A system comprising:
a wireless device;
a messaging service to maintain data objects on behalf of a user; and
a data center, coupled to the wireless device and the messaging service, to receive identification (ID) information from the messaging service to activate the wireless device for initial wireless data service between the messaging service and the wireless device, receive ID information from the wireless device as a. component of a first time request to connect with the messaging service, activate wireless data service between the messaging service and the wireless device by establishing a first permanent connection to deliver a first type of message service, and a second permanent connection to deliver a second type of message service between the messaging service and the wireless device if the ID information received from the messaging service matches the ID information received from the wireless device.
9. The system of claim 8 wherein the data center establishes a plurality of routing connections between the wireless device and the messaging service, each of plurality of connections corresponding to a data service level authorized by the data center.
10. The system of claim 9 wherein each of the plurality of routing connections are permanent.
11. The system of claim 10 wherein each of the one or more routing connections are private.
12. The system of claim 8 wherein the first routing connection represents an electronic mail (e-mail) service.
13. The system of claim 12 wherein the second routing connection represents a provisioning service, a third routing connection represents a calendar service and a fourth routing connection represents an address book service.
14. The system of claim 12 wherein a second routing connection represents a second e-mail service, and a third routing connection represents a third e-mail service.
15. The system of claim 14 wherein the first, second and third e-mail services each have a different address.
Patent Citations (178)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4682150(A) | 1987-07-01 | Mathes | Applicant |
| US5049881(A) | 1991-09-01 | Gibson et al. | Applicant |
| US5115392(A) | 1992-05-01 | Takamoto et al. | Applicant |
| US5126739(A) | 1992-06-01 | Whiting et al. | Applicant |
| US5159592(A) | 1992-10-01 | Perkins | Applicant |
| US5321840(A) | 1994-06-01 | Ahlin et al. | Applicant |
| US5469161(A) | 1995-11-01 | Bezek | Applicant |
| US5521597(A) | 1996-05-01 | Dimitri | Applicant |
| US5553281(A) | 1996-09-01 | Brown et al. | Applicant |
| US5559800(A) | 1996-09-01 | Mousseau et al. | Applicant |
| US5563595(A) | 1996-10-01 | Strohacker | Applicant |
| US5666530(A) | 1997-09-01 | Clark et al. | Applicant |
| US5715387(A) | 1998-02-01 | Barnstijn et al. | Applicant |
| US5727159(A) | 1998-03-01 | Kikinis | Applicant |
| US5727202(A) | 1998-03-01 | Kucala | Applicant |
| US5760716(A) | 1998-06-01 | Mathews et al. | Applicant |
| US5771010(A) | 1998-06-01 | Masenas | Applicant |
| US5790974(A) | 1998-08-01 | Tognazzini | Applicant |
| US5793970(A) | 1998-08-01 | Fakes et al. | Applicant |
| US5802312(A) | 1998-09-01 | Lazaridis et al. | Applicant |
| US5838923(A) | 1998-11-01 | Lee et al. | Applicant |
| US5841376(A) | 1998-11-01 | Hayashi | Applicant |
| US5870610(A) | 1999-02-01 | Beyda | Applicant |
| US5875329(A) | 1999-02-01 | Shan | Applicant |
| US5903230(A) | 1999-05-01 | Masenas | Applicant |
| US5930471(A) | 1999-07-01 | Milewski et al. | Applicant |
| US5961590(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5974238(A) | 1999-10-01 | Chase, Jr. | Applicant |
| US5987464(A) | 1999-11-01 | Schneider | Applicant |
| US6003089(A) | 1999-12-01 | Shaffer et al. | Applicant |
| US6023708(A) | 2000-02-01 | Mendez et al. | Applicant |
| US6034621(A) | 2000-03-01 | Kaufman | Applicant |
| US6052735(A) | 2000-04-01 | Ulrich et al. | Applicant |
| US6065017(A) | 2000-05-01 | Barker | Applicant |
| US6085185(A) | 2000-07-01 | Matsuzawa et al. | Applicant |
| US6104392(A) | 2000-08-01 | Shaw et al. | Applicant |
| US6111707(A) | 2000-08-01 | Busddecke et al. | Applicant |
| US6151606(A) | 2000-11-01 | Mendez | Applicant |
| US6182117(B1) | 2001-01-01 | Christie et al. | Applicant |
| US6188695(B1) | 2001-02-01 | Przybysz | Applicant |
| US6216157(B1) | 2001-04-01 | Vishwanath et al. | Applicant |
| US6218970(B1) | 2001-04-01 | Jaquette | Applicant |
| US6219694(B1) | 2001-04-01 | Lazaridis et al. | Applicant |
| US6226618(B1) | 2001-05-01 | Downs et al. | Applicant |
| US6259891(B1) | 2001-07-01 | Allen | Applicant |
| US6275848(B1) | 2001-08-01 | Arnold | Applicant |
| US6279001(B1) | 2001-08-01 | DeBettencourt et al. | Applicant |
| US6282294(B1) | 2001-08-01 | Deo et al. | Examiner |
| US6304881(B1) | 2001-10-01 | Halim et al. | Applicant |
| US6310889(B1) | 2001-10-01 | Parsons et al. | Applicant |
| US6330618(B1) | 2001-12-01 | Hawkins et al. | Applicant |
| US6343299(B1) | 2002-01-01 | Huang et al. | Applicant |
| US6347340(B1) | 2002-02-01 | Coelho et al. | Applicant |
| US6360272(B1) | 2002-03-01 | Lincke et al. | Applicant |
| US6384850(B1) | 2002-05-01 | McNally et al. | Applicant |
| US6393434(B1) | 2002-05-01 | Huang et al. | Applicant |
| US6396482(B1) | 2002-05-01 | Griffin et al. | Applicant |
| US6401136(B1) | 2002-06-01 | Britton et al. | Applicant |
| US6430601(B1) | 2002-08-01 | Eldridge et al. | Applicant |
| US6449622(B1) | 2002-09-01 | LaRue et al. | Applicant |
| US6457062(B1) | 2002-09-01 | Pivowar et al. | Applicant |
| US6460055(B1) | 2002-10-01 | Midgley et al. | Applicant |
| US6463463(B1) | 2002-10-01 | Godfrey et al. | Applicant |
| US6463464(B1) | 2002-10-01 | Lazaridis et al. | Applicant |
| US6477543(B1) | 2002-11-01 | Huang et al. | Applicant |
| US6505055(B1) | 2003-01-01 | Kahn et al. | Applicant |
| US6535892(B1) | 2003-03-01 | LaRue et al. | Applicant |
| US6553037(B1) | 2003-04-01 | Pivowar et al. | Examiner |
| US6571245(B2) | 2003-05-01 | Huang et al. | Applicant |
| US6604236(B1) | 2003-08-01 | Draper et al. | Applicant |
| US6615246(B2) | 2003-09-01 | Pivowar et al. | Examiner |
| US6615253(B1) | 2003-09-01 | Bowman-Amuah | Applicant |
| US6625621(B2) | 2003-09-01 | Tan et al. | Applicant |
| US6628934(B2) | 2003-09-01 | Rosenberg et al. | Applicant |
| US6636873(B1) | 2003-10-01 | Carini et al. | Applicant |
| US6640244(B1) | 2003-10-01 | Bowman-Amuah | Applicant |
| US6654746(B1) | 2003-11-01 | Wong et al. | Applicant |
| US6658167(B1) | 2003-12-01 | Lee et al. | Applicant |
| US6671757(B1) | 2003-12-01 | Multer et al. | Applicant |
| US6675203(B1) | 2004-01-01 | Herrod et al. | Applicant |
| US6694335(B1) | 2004-02-01 | Hopmann et al. | Applicant |
| US6697458(B1) | 2004-02-01 | Kunjibettu | Applicant |
| US6701378(B1) | 2004-03-01 | Gilhuly et al. | Applicant |
| US6721787(B1) | 2004-04-01 | Hiscock | Applicant |
| US6721871(B2) | 2004-04-01 | Piispanen et al. | Applicant |
| US6732105(B1) | 2004-05-01 | Watson et al. | Examiner |
| US6757698(B2) | 2004-06-01 | McBride et al. | Applicant |
| US6779019(B1) | 2004-08-01 | Mousseau et al. | Applicant |
| US6792085(B1) | 2004-09-01 | Rigaldies et al. | Applicant |
| US6810405(B1) | 2004-10-01 | LaRue et al. | Applicant |
| US6850757(B2) | 2005-02-01 | Watanabe et al. | Examiner |
| US6874029(B2) | 2005-03-01 | Hutcheson et al. | Applicant |
| US6874037(B1) | 2005-03-01 | Abram et al. | Applicant |
| US6901415(B2) | 2005-05-01 | Thomas et al. | Applicant |
| US6907243(B1) | 2005-06-01 | Patel | Applicant |
| US6931454(B2) | 2005-08-01 | Deshpande et al. | Applicant |
| US6934766(B1) | 2005-08-01 | Russell | Applicant |
| US6941348(B2) | 2005-09-01 | Petry et al. | Applicant |
| US6941349(B2) | 2005-09-01 | Godfrey et al. | Applicant |
| US6947738(B2) | 2005-09-01 | Skog et al. | Examiner |
| US6954789(B2) | 2005-10-01 | Dietz et al. | Applicant |
| US6957077(B2) | 2005-10-01 | Dehlin | Examiner |
| US6973299(B2) | 2005-12-01 | Apfel | Applicant |
| US6983308(B1) | 2006-01-01 | Oberhaus et al. | Applicant |
| US7003776(B2) | 2006-02-01 | Sutherland | Applicant |
| US7010303(B2) | 2006-03-01 | Lewis et al. | Examiner |
| US7016700(B2) | 2006-03-01 | Takahashi et al. | Examiner |
| US7085809(B2) | 2006-08-01 | Mori et al. | Applicant |
| US7092699(B1) | 2006-08-01 | Hefter | Applicant |
| US7103656(B2) | 2006-09-01 | Lewis et al. | Examiner |
| US7136934(B2) | 2006-11-01 | Carter et al. | Applicant |
| US7138934(B2) | 2006-11-01 | Melanson | Applicant |
| US7139555(B2) | 2006-11-01 | Apfel | Applicant |
| US7149813(B2) | 2006-12-01 | Flanagin et al. | Applicant |
| US7184999(B1) | 2007-02-01 | Watson et al. | Examiner |
| US7203477(B2) | 2007-04-01 | Coppinger et al. | Examiner |
| US7203485(B2) | 2007-04-01 | Coppinger et al. | Examiner |
| US7243163(B1) | 2007-07-01 | Friend et al. | Applicant |
| US7287097(B1) | 2007-10-01 | Friend et al. | Applicant |
| US7313385(B2) | 2007-12-01 | Yabe et al. | Applicant |
| US7509376(B2) | 2009-03-01 | Mousseau et al. | Applicant |
| US7596565(B2) | 2009-09-01 | Friend et al. | Applicant |
| US7743119(B2) | 2010-06-01 | Friend et al. | Applicant |
| US7817981(B2) | 2010-10-01 | Coppinger et al. | Examiner |
| US7822410(B2) | 2010-10-01 | Coppinger et al. | Examiner |
| US7835951(B1) | 2010-11-01 | Burger et al. | Examiner |
| US2001/0004744(A1) | 2001-06-01 | Lazaridis et al. | Applicant |
| US2001/0005864(A1) | 2001-06-01 | Mousseau et al. | Applicant |
| US2001/0010059(A1) | 2001-07-01 | Burman et al. | Applicant |
| US2001/0034654(A1) | 2001-10-01 | Vigil et al. | Applicant |
| US2001/0051996(A1) | 2001-12-01 | Cooper et al. | Examiner |
| US2001/0051998(A1) | 2001-12-01 | Henderson | Applicant |
| US2001/0054115(A1) | 2001-12-01 | Ferguson et al. | Applicant |
| US2002/0013853(A1) | 2002-01-01 | Baber et al. | Applicant |
| US2002/0016818(A1) | 2002-02-01 | Kirani et al. | Applicant |
| US2002/0019225(A1) | 2002-02-01 | Miyashita | Applicant |
| US2002/0032722(A1) | 2002-03-01 | Baynes, Jr. et al. | Applicant |
| US2002/0046286(A1) | 2002-04-01 | Caldwell et al. | Applicant |
| US2002/0116465(A1) | 2002-08-01 | Kim et al. | Examiner |
| US2002/0119793(A1) | 2002-08-01 | Hronek et al. | Applicant |
| US2002/0120696(A1) | 2002-08-01 | Mousseau et al. | Applicant |
| US2002/0146240(A1) | 2002-10-01 | Ogawa et al. | Applicant |
| US2002/0160773(A1) | 2002-10-01 | Gresham et al. | Applicant |
| US2003/0046434(A1) | 2003-03-01 | Flanagin et al. | Applicant |
| US2003/0050046(A1) | 2003-03-01 | Conneely et al. | Applicant |
| US2003/0069842(A1) | 2003-04-01 | Kight et al. | Applicant |
| US2003/0069848(A1) | 2003-04-01 | Larson et al. | Examiner |
| US2003/0081621(A1) | 2003-05-01 | Godfrey et al. | Applicant |
| US2003/0097381(A1) | 2003-05-01 | Detweiler et al. | Applicant |
| US2004/0049599(A1) | 2004-03-01 | Friend et al. | Applicant |
| US2004/0054739(A1) | 2004-03-01 | Friend et al. | Applicant |
| US2004/0088546(A1) | 2004-05-01 | Shah et al. | Examiner |
| US2004/0105423(A1) | 2004-06-01 | Koehler et al. | Applicant |
| US2004/0109436(A1) | 2004-06-01 | Vargas et al. | Applicant |
| US2004/0181591(A1) | 2004-09-01 | Yu et al. | Applicant |
| US2004/0213283(A1) | 2004-10-01 | Ohkubo et al. | Applicant |
| US2005/0148356(A1) | 2005-07-01 | Ferguson et al. | Applicant |
| US2006/0112427(A1) | 2006-05-01 | Shahbazi | Examiner |
| US2007/0130315(A1) | 2007-06-01 | Friend et al. | Examiner |
| US2007/0239898(A1) | 2007-10-01 | Friend et al. | Applicant |
| US2007/0266107(A1) | 2007-11-01 | Friend et al. | Applicant |
| US2008/0301231(A1) | 2008-12-01 | Mehta et al. | Applicant |
| EP909037(A1) | 1999-04-01 | Applicant | |
| EP917077(A2) | 1999-05-01 | Applicant | |
| EP1014629 | 2000-06-01 | Applicant | |
| EP666651(B1) | 2000-07-01 | Applicant | |
| JP7-182263(A) | 1995-07-01 | Applicant | |
| JP10-269125(A) | 1998-10-01 | Applicant | |
| JP11-136365(A) | 1999-05-01 | Applicant | |
| JP2001-053785(A) | 2001-02-01 | Applicant | |
| JP2001-076040(A) | 2001-03-01 | Applicant | |
| WO67158(A2) | 2000-11-01 | Applicant | |
| WO178342(A2) | 2001-10-01 | Applicant | |
| WO219626(A2) | 2002-03-01 | Applicant | |
| WO2086954(A1) | 2002-10-01 | Applicant | |
| WO3007482(A1) | 2003-01-01 | Applicant | |
| WO3015362(A1) | 2003-02-01 | Applicant | |
| WO3083667(A1) | 2003-10-01 | Applicant |
Non-Patent Literature (6)
- Stefan G. Hild and Peter Robinson, “Mobilizing Applications”, IEEE Personal Communications, Oct. 1997, XP-000721303, pp. 26-34.Applicant
- European Patent Office, “Supplementary European Search Report” for Application No. 03719504.7 (PCT/US2003/09576); Aug. 22, 2006; 4 pages.Applicant
- United States Patent and Trademark Office, “Non-Final Office Action” for U.S. Appl. No. 09/924,283, Mar. 21, 2005, 11 pages.Applicant
- United States Patent and Trademark Office, “Final Office Action” for U.S. Appl. No. 09/924,283, Sep. 7, 2005, 13 pages.Applicant
- United States Patent and Trademark Office, “Non-Final Office Action” for U.S. Appl. No. 09/924,283, Apr. 10, 2006, 18 pages.Applicant
- United States Patent and Trademark Office, “System and Method for Full Wireless Synchronization of a Data Processing Apparatus with a Messaging Service”, U.S. Appl. No. 10/348,281 filed Jan. 21, 2003, 107 pages.Applicant