|Publication number||US20070130315 A1|
|Application number||US 11/700,523|
|Publication date||Jun 7, 2007|
|Filing date||Jan 30, 2007|
|Priority date||Aug 7, 2001|
|Also published as||US7962622, US20040006630|
|Publication number||11700523, 700523, US 2007/0130315 A1, US 2007/130315 A1, US 20070130315 A1, US 20070130315A1, US 2007130315 A1, US 2007130315A1, US-A1-20070130315, US-A1-2007130315, US2007/0130315A1, US2007/130315A1, US20070130315 A1, US20070130315A1, US2007130315 A1, US2007130315A1|
|Inventors||John Friend, Michael Belshe, David Hoffman|
|Original Assignee||John Friend, Michael Belshe, David Hoffman|
|Export Citation||BiBTeX, EndNote, RefMan|
|Referenced by (49), Classifications (33), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation-in-part of co-pending 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, which is a continuation-in-part of co-pending 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.
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.
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.
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”).™
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.
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”).
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.
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).
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.
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.
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.
A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:
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.
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.
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.
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
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.
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.
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 #”)).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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).
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
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.
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7962622 *||Mar 27, 2003||Jun 14, 2011||Motorola Mobility, Inc.||System and method for providing provisioning and upgrade services for a wireless device|
|US8385916||Apr 26, 2012||Feb 26, 2013||Headwater Partners I Llc||Automated device provisioning and activation|
|US8396458||Mar 12, 2013||Headwater Partners I Llc||Automated device provisioning and activation|
|US8406733||May 1, 2012||Mar 26, 2013||Headwater Partners I Llc||Automated device provisioning and activation|
|US8406748||Mar 26, 2013||Headwater Partners I Llc||Adaptive ambient services|
|US8437271||Apr 9, 2012||May 7, 2013||Headwater Partners I Llc||Verifiable and accurate service usage monitoring for intermediate networking devices|
|US8441989||Jul 20, 2012||May 14, 2013||Headwater Partners I Llc||Open transaction central billing system|
|US8467312||Jun 18, 2013||Headwater Partners I Llc||Verifiable and accurate service usage monitoring for intermediate networking devices|
|US8478667||Apr 25, 2012||Jul 2, 2013||Headwater Partners I Llc||Automated device provisioning and activation|
|US8516552||Apr 4, 2012||Aug 20, 2013||Headwater Partners I Llc||Verifiable service policy implementation for intermediate networking devices|
|US8531986||Apr 10, 2012||Sep 10, 2013||Headwater Partners I Llc||Network tools for analysis, design, testing, and production of services|
|US8547872||Apr 12, 2012||Oct 1, 2013||Headwater Partners I Llc||Verifiable and accurate service usage monitoring for intermediate networking devices|
|US8570908||Apr 25, 2013||Oct 29, 2013||Headwater Partners I Llc||Automated device provisioning and activation|
|US8588110||Sep 13, 2012||Nov 19, 2013||Headwater Partners I Llc||Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account|
|US8589541||May 25, 2011||Nov 19, 2013||Headwater Partners I Llc||Device-assisted services for protecting network capacity|
|US8626115||Sep 9, 2011||Jan 7, 2014||Headwater Partners I Llc||Wireless network service interfaces|
|US8630192||Mar 2, 2009||Jan 14, 2014||Headwater Partners I Llc||Verifiable and accurate service usage monitoring for intermediate networking devices|
|US8630611||Nov 15, 2012||Jan 14, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8631102||Nov 15, 2012||Jan 14, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8635678||Mar 28, 2013||Jan 21, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8639811||Jan 15, 2013||Jan 28, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8639935||Dec 12, 2012||Jan 28, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8640198||Jan 15, 2013||Jan 28, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8666364||Sep 13, 2012||Mar 4, 2014||Headwater Partners I Llc||Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account|
|US8667571||Dec 4, 2012||Mar 4, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8675507||Mar 2, 2009||Mar 18, 2014||Headwater Partners I Llc||Service profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices|
|US8688099||Sep 13, 2012||Apr 1, 2014||Headwater Partners I Llc||Open development system for access service providers|
|US8695073||Apr 19, 2013||Apr 8, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8713630||Apr 12, 2012||Apr 29, 2014||Headwater Partners I Llc||Verifiable service policy implementation for intermediate networking devices|
|US8724554||Mar 19, 2013||May 13, 2014||Headwater Partners I Llc||Open transaction central billing system|
|US8737957||Apr 22, 2013||May 27, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8797908||May 16, 2013||Aug 5, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8799451||Mar 2, 2009||Aug 5, 2014||Headwater Partners I Llc||Verifiable service policy implementation for intermediate networking devices|
|US8839387||Mar 2, 2009||Sep 16, 2014||Headwater Partners I Llc||Roaming services network and overlay networks|
|US8839388||Mar 2, 2009||Sep 16, 2014||Headwater Partners I Llc||Automated device provisioning and activation|
|US8868455||Aug 17, 2012||Oct 21, 2014||Headwater Partners I Llc||Adaptive ambient services|
|US8886162||Jan 9, 2014||Nov 11, 2014||Headwater Partners I Llc||Restricting end-user device communications over a wireless access network associated with a cost|
|US8897743||Dec 20, 2011||Nov 25, 2014||Headwater Partners I Llc||Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account|
|US8897744||Oct 2, 2012||Nov 25, 2014||Headwater Partners I Llc||Device assisted ambient services|
|US8898079||Sep 13, 2012||Nov 25, 2014||Headwater Partners I Llc||Network based ambient services|
|US8903452||Oct 2, 2012||Dec 2, 2014||Headwater Partners I Llc||Device assisted ambient services|
|US8924549||Aug 20, 2012||Dec 30, 2014||Headwater Partners I Llc||Network based ambient services|
|US8948025||Apr 18, 2014||Feb 3, 2015||Headwater Partners I Llc||Remotely configurable device agent for packet routing|
|US9014026||Feb 7, 2012||Apr 21, 2015||Headwater Partners I Llc||Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy|
|US9026079||Jan 3, 2014||May 5, 2015||Headwater Partners I Llc||Wireless network service interfaces|
|US9037127||Apr 28, 2014||May 19, 2015||Headwater Partners I Llc||Device agent for remote user configuration of wireless network access|
|US9094311||Jul 23, 2014||Jul 28, 2015||Headwater Partners I, Llc||Techniques for attribution of mobile device data traffic to initiating end-user application|
|US20140058955 *||Aug 27, 2012||Feb 27, 2014||Bank Of America Corporation||Readable indicia for product registration|
|WO2010088278A1 *||Jan 27, 2010||Aug 5, 2010||Headwater Partners I Llc||Device assisted services install|
|International Classification||H04L29/08, G06F17/30, H04L12/58, H04L29/06, H04L12/56, G06F15/173|
|Cooperative Classification||H04L67/2814, H04L67/1095, H04L67/04, H04L69/04, H04L67/14, H04L67/325, H04L69/329, H04W88/184, H04L12/5895, H04W76/021, H04W4/12, H04L51/38, H04W8/26, H04L45/24, H04W76/022, H04W76/02, H04W8/18|
|European Classification||H04L29/06C5, H04L45/24, H04L29/08N3, H04L29/08N31T, H04W76/02C, H04L12/58W, H04L29/08N13, H04W76/02, H04L29/08N27D|
|Apr 1, 2009||AS||Assignment|
Owner name: MOTOROLA, INC.,ILLINOIS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GOOD TECHNOLOGY, INC.;REEL/FRAME:022481/0859
Effective date: 20090225
|Oct 23, 2009||AS||Assignment|
Owner name: MOTOROLA, INC., ILLINOIS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GOOD TECHNOLOGY INC.;REEL/FRAME:023415/0580
Effective date: 20090225
|Dec 13, 2010||AS||Assignment|
Owner name: MOTOROLA MOBILITY, INC, ILLINOIS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA, INC;REEL/FRAME:025673/0558
Effective date: 20100731
|Aug 21, 2012||AS||Assignment|
Owner name: MOTOROLA MOBILITY LLC, ILLINOIS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA MOBILITY, INC.;REEL/FRAME:028829/0856
Effective date: 20120622