Patent Grant
7801941
The apparatus and method discussed herein relates to handheld computers and, more particularly, to exchanging data between a handheld computer and another device.
Handheld computers, often referred to as personal digital assistants (PDAs), are intended to be mobile devices. In general, small sizes are desired for handheld computers to enhance mobility. Additionally, it is often desirable to maintain relatively low selling prices for handheld computers so they will appeal to a wider range of customers. This smaller size and low price tend to limit the processing power and storage capacity of handheld computers. Thus, handheld computers are typically less powerful than their desktop or server counterparts.
Many handheld computers are capable of establishing a wireless communication link between the handheld computer and another computing device, such as another handheld computer, a desktop computer, or a server. In certain situations, handheld computers may rely on other computing devices to perform functions on behalf of the handheld computer. For example, a handheld computer may rely on a server to receive and store email messages that can be accessed and read by a handheld computer. The handheld computer periodically establishes a connection with the server and views email messages stored on the server. After viewing the email messages, the connection between the server and the handheld computer is terminated. Since the connection between the server and the handheld computer is not continuous, it is desirable to provide mechanisms that support an efficient exchange of data between the server and the handheld computer.
Embodiments of the apparatus and method discussed herein provide for a handheld computer capable of exchanging data with other computing devices, such as servers, desktop computers, laptop computers, or other handheld computers. The handheld computer is aware of various actions that the server or other computing device is capable of performing on behalf of the handheld computer. The handheld computer then requests certain actions from the appropriate server based on the handheld computer's knowledge of that server's capabilities. The handheld computer may also group multiple actions in a single request sent to the server during a single communication session, rather than sending multiple separate requests to the server. The server may respond to the multiple actions at the same time (e.g., during the same communication session) or may respond to different actions at different times. An example structure is described that provides logic for handling the communication of data between a handheld computer and another computing device as well as communicating the data to and from one or more application programs.
In one embodiment, a transport component receives a request to perform an action from a handheld computer. A router is coupled to the transport component and identifies an action contained in the received request. An executor is coupled to the router and executes the identified action. The executor also generates a response based on execution of the identified action. The transponder component also communicates the response to the handheld computer.
In another embodiment, a method identifies multiple actions supported by a server. A user request is received to perform an operation. The method determines an action associated with the requested operation. The server is requested to perform the action. A response is received from the server such that the response is generated as a result of performing the action.
The systems and methods described herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings. Similar reference numbers are used throughout the drawings to reference similar elements and features.
The systems and methods described herein provide for the exchange of data between two devices. For purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various systems and methods. It will be apparent, however, that the systems and methods described herein may be implemented without these specific details. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Specific examples are discussed herein with reference to a server and a handheld computer. However, the methods and systems described herein can be used by any computing device to communicate with another computing device. Additionally, various examples are described with reference to a wireless communication link that allows two computing devices to communicate with one another. Alternate embodiments may utilize a wired communication link or a combination of one or more wireless communication links and one or more wired communication links.
As used herein, a handheld computer includes any portable computing device and any mobile computing device. Example handheld computers include PDAs, cellular phones, communicators, vehicle-based computer systems and laptop computers.
Handheld computer 102 also includes three application programs 106, 108 and 110. Although handheld computer 102 contains three application programs 106-110, a particular handheld computer may contain any number of application programs. Any or all of these application programs 106-110 may interact with client 104 to generate one or more requests for server 100 and receive data back in response to the requests. The application programs 106-110 may include, for example, an email application program, a database access program, a contact manager and a text editing application.
The architecture of server 100 provides specific logic for processing data and delivering data to the appropriate application. This architecture provides a peer-to-peer messaging framework for devices to exchange data via a wireless communication link. This architecture permits the development of cross-platform client-server wireless applications. The addition of an invocation layer, discussed below, assists with the handling of data and ensures that data is provided to the appropriate application.
The architecture of server 100 is configured to process various “actions” and other functions. An “action” is an application-level task that, when performed, generates a response that is provided to the user (or application) requesting that the action be performed. In one embodiment, actions are implemented as classes in an object oriented language, such as C++. Each application program supports one or more actions. For example, an email application may support actions such as “fetch messages” and “delete messages”. A client device (such as a handheld computer) uses the services of a server supporting this architecture to execute the actions and provide the results to the client device.
Actions can be grouped together based on the application that the actions are associated with or the type of application that the actions are associated with (e.g., an email application or all database-related applications). A particular action may be associated with two or more applications and/or two or more types of applications. Additionally, a particular action may be associated with a particular user. Each action includes one or more components, such as an action name, an action identifier, an application identifier and a payload, which contains various data that is associated with the action.
Referring again to
Transport component 112 is coupled to a router 114, which maintains system resource information and assists the transport component with the identification of actions contained in received requests. The transport component 112 interprets the received requests and, using the services of router 114, sends the actions contained in the request to an executor 116, which is coupled to router 114. Executor 116 executes the actions contained in the request and generates responses to be sent to the source of the request. For example, executor 116 may execute one or more of actions 118, 120, and 122. Transport component 112 receives the response from executor 116 and communicates the response to the client device that sent the original request.
The server may have a set of pre-defined supported actions that can be executed by the executor 116. However, executor 116 is also capable of executing other actions that are not contained in the set of pre-defined supported actions. For example, executor 116 can execute actions that are self-described and/or self-executing.
In one embodiment, transport component 112 is implemented as a standalone server application. Alternatively, transport component 112 is part of another application or system in server 100. In a particular embodiment, transport component 112 has some knowledge of the corresponding transport component on the client. The transport component 112 also has some knowledge of the various actions, action responses and other data associated with the actions.
In a specific implementation, the architecture described above with respect to server 100 is a component of another server architecture. For example, a Java implementation provides an HTTP transport core component that hosts the architecture described above inside a generic HTTP server plug-in module. This module receives incoming HTTP requests and sends HTTP responses based on the received requests. The module is the runtime environment for the router and the executor discussed above. This implementation allows the architecture described above to operate in several different HTTP server environments.
In a particular embodiment of handheld computer 102, client 104 contains a transport component similar to transport component 112 in server 100. Similarly, client 104 contains a router and an executor similar to router 114 and executor 116 in server 100. The transport component in client 104 communicates with transport component 112 via the network messaging and transport layer. Client 104 has some knowledge regarding the actions and other functions that are supported by server 100. Thus, client 104 may communicate with different servers, knowing the actions supported by each server. The router and executor in client 104 work in combination with the transport component in the client to receive and process requests from an application. Additionally the router and executor in client 104 assist with processing data contained in responses and providing that data to the appropriate application in handheld computer 102.
Although not shown in
At block 204 of
After identifying the actions associated with the requested operation, the handheld computer establishes a communication session with the server (block 208). Typically this communication session is a wireless communication session. Once the communication session is established, the handheld computer sends one or more action requests and other data to the server (block 210). As discussed in greater detail below, a particular request may contain multiple actions as well as metadata that applies to all of the actions in the request.
After receiving the action requests form the handheld computer, the server executes the requested actions and returns one or more results to the handheld computer (block 212). The server then sends any other data to the handheld computer (block 214). This other data may include application program updates, data to be synchronized with the handheld computer and the like. After receiving the responses and other data from the server, the handheld computer terminates the communication session with the server (block 216). The handheld computer then acts on the received results and other data (block 218). For example, the handheld computer may display the new email messages received from the server and synchronize any such data received from the server.
Although the example of
The handheld computer then establishes a communication session with the server and sends a request containing multiple actions to the server (block 406). This request may resemble request 300 shown in
The handheld computer then terminates the communication session with the server (block 410). After the communication session is terminated, the server executes the remaining actions in the request (block 412). At a later time, the handheld computer establishes another communication session with the server (block 414). At this point, the server has finished executing the remaining actions in the request, so the server sends the results of the remaining actions in the request to the handheld computer (block 416). The handheld computer then terminates the communication session with the server (block 418).
In alternate embodiments, one or more new requests may be communicated to the server during the second communication session. The actions associated with these requests may be executed and communicated to the handheld computer before the second communication session is terminated. However, if any actions are not executed before the second communication session is terminated, execution will be completed and the results will be communicated to the handheld computer during a future communication session. Thus, it may be necessary to establish any number of communication sessions for the handheld computer to receive all responses to multiple requests submitted to the server.
An analog-digital (A/D) converter 514 is coupled to processor 506. One or more channels from A/D converter 232 maybe used to convert analog input provided by the digitizer or by another analog input mechanism.
The handheld computer 500 may include one or more expansion ports for coupling to accessory devices, such as cradles, modems, memory units, re-chargers and other devices. Examples of expansion ports include serial ports, Universal serial Bus (USB) ports, CompactFlash slots and infra-red ports. In an embodiment shown, a first expansion port 520 enables one or more types of expansion modules to be connected to processor 506. The handheld computer 500 may also include a second expansion port (not shown) to couple to another accessory device. Each expansion port may be coupled to processor 506, although the components that receive a signal from one of the expansion ports are determined by the type of accessory device selected.
The accessory device that may be coupled to an expansion port may be identified by primary functions of their internal components. Each accessory device may include one or more of the following set of components: a radio-frequency transmitter and/or receiver, a processor, an input mechanism, additional memory, a battery, or another A/D converter.
One or more buttons 512 are coupled to processor 506 and A/D converter 514. Buttons 512 provide a mechanism for a user to provide input to the handheld computer 500, such as selecting a menu option, launching an application program, or navigating through an application program. A transceiver 516 is coupled to processor 506 and an antenna 518. Transceiver 516 is capable of sending and receiving signals across a wireless communication link using antenna 518. This configuration allows handheld computer 500 to communicate with servers and other wireless devices.
The handheld computer illustrated in
In the various examples and descriptions provided herein, the handheld computer generates requests and the server generates responses based on one or more actions included in the requests. However, in alternate embodiments, the server may generate one or more requests that are processed by the handheld computer. The handheld computer then generates one or more responses that are communicated to the server. This alternate embodiment uses procedures similar to those discussed herein with respect to
The following materials describe several example actions, request formats, response formats and various description formats that can be used with the systems and methods discussed herein.
Fetch Messages (id 110)
Retrieves a set of messages, bounded by some conditions, including unique IDs. This Action may be used to request a single message based on its ID, search for new ones, synch, and others. The messages are returned with UIDs intact. The amount of the message data returned, as well as what level of attachment data to return, is configurable at the time of execution. In general, the message structure is based on the MIME extensions to RFC822.
The Bound is the means for limiting the message set returned to the client. There are two main types of Bounds, Logical and Conditional.
Logical bounds represent an AND or an OR of some other bounds.
Conditional Bounds represent conditions that can be tested for truth, indicating whether or not the Bound is satisfied. There are several types of Bounds for testing different kinds of conditions, such as strings being equal, integers being greater, etc. The general form of the Conditional Bound is:
For String bounds, the Condition is defined as:
The available string condition bounds are:
For Integer bounds, the Condition is defined as:
The available integer condition bounds are:
For Date bounds, the Condition is defined as:
The available date condition bounds are:
For Boolean bounds, the Condition is defined as:
The available Boolean condition bounds are:
For Message ID bounds, the Condition is defined as:
The available message ID condition bounds are:
Content descriptors are the mechanism through which the client can indicate to the server which types of content it would like to pull down in this initial fetch.
The response to this type of action contains the appropriate message data, with some meta information.
The individual messages contain the following set of information
Where a Part is:
A “MultiPart” represents a parent node in a hierarchical structure of parts:
An “Other” part represents any part for which specific additional information is not known:
A “Plain Text” part represents any part for which it is possible for the server to transform or decode the content into plain-text:
Delete Message (id 100)
This Action deletes a message from the back-end message store. The message is referenced by its ID. The response will include appropriate errors if the message has already been deleted or is otherwise unavailable.
The response to this Action contains just a single piece of information, the status.
Send Message (id 115)
Sends a message to recipient(s) through the server. All fully-resolved address information is provided by the client. The reply-to and from information is based on the meta-data discussed earlier. The Action supports the notion of messages that are forwards of or replies to existing messages. The significance of this is that messages with large attachments do not need to be fully retrieved to be forwarded with attachment data intact. The response will include appropriate errors if a referenced existing message for reply or forward has been deleted or is otherwise unavailable.
The response to this Action contains just a single piece of information, the status.
Get Message Content (id 99)
This Action retrieves additional bytes of a message for which headers and initial data have already been retrieved. This is designed to allow the client to sequentially retrieve more and more of an existing message, or to retrieve attachment data not previously fetched for that message, given the existing message ID. The response will include appropriate errors if a referenced existing message has been deleted or is otherwise unavailable.
The response to this Action contains a status code and the actual fetched content.
Stat (id 120)
The Stat Action retrieves the IDs and read/unread state of all existing server-side messages. This is designed to allow the client to resolve out-of-synch issues with the server.
The response will include an optionally large amount of information, depending on the number of messages available on the server. There will be numerous ID/Flag pairs in the response.
Set Message Read State (id 114)
This Action sets the read/unread state for messages on the server. This allows the client to synch the server-side status of the messages, meaningful to the user when accessing the mail store via another interface.
The response to this Action contains just a single piece of information, the status.
General Form
In all subsequent discussion of this format, the use of the following delimiter characters is assumed.
In discussions of the text format, the > and < characters are used to indicate the start and end of the format specification, but are not included within it. Entities in a format specification are separated by delimiters, which are indicated as <DELIM_N> as defined above. In general, entries within the various format specifications can be omitted if they are optional in the Action-level specification, leaving two delimiters side-by-side.
The present application claims priority to Provisional Patent Application Ser. No. 60/303,412, filed Jul. 9, 2001, the disclosure of which is hereby incorporated by reference in its entirety. The present application also claims priority to Provisional Patent Application Ser. No. 60/303,391, filed Jul. 9, 2001, the disclosures of which is also incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5530693 | Averbuch et al. | Jun 1996 | A |
| 5758088 | Bezaire et al. | May 1998 | A |
| 5784562 | Diener | Jul 1998 | A |
| 5872926 | Levac et al. | Feb 1999 | A |
| 5907678 | Housel et al. | May 1999 | A |
| 5974461 | Goldman et al. | Oct 1999 | A |
| 5999942 | Talati | Dec 1999 | A |
| 6055424 | Tornqvist et al. | Apr 2000 | A |
| 6107944 | Behr et al. | Aug 2000 | A |
| 6134582 | Kennedy | Oct 2000 | A |
| 6151628 | Xu et al. | Nov 2000 | A |
| 6167426 | Payne et al. | Dec 2000 | A |
| 6167441 | Himmel | Dec 2000 | A |
| 6285683 | Lin | Sep 2001 | B1 |
| 6336135 | Niblett et al. | Jan 2002 | B1 |
| 6393569 | Orenshteyn | May 2002 | B1 |
| 6442687 | Savage | Aug 2002 | B1 |
| 6477543 | Huang et al. | Nov 2002 | B1 |
| 6484150 | Blinn et al. | Nov 2002 | B1 |
| 6546425 | Hanson et al. | Apr 2003 | B1 |
| 6563800 | Salo et al. | May 2003 | B1 |
| 6606486 | Cubbage et al. | Aug 2003 | B1 |
| 6618763 | Steinberg | Sep 2003 | B1 |
| 6636733 | Helferich | Oct 2003 | B1 |
| 6647409 | Sherman et al. | Nov 2003 | B1 |
| 6671355 | Spielman et al. | Dec 2003 | B1 |
| 6795710 | Creemer | Sep 2004 | B1 |
| 6810405 | LaRue et al. | Oct 2004 | B1 |
| 6819945 | Chow et al. | Nov 2004 | B1 |
| 6847632 | Lee et al. | Jan 2005 | B1 |
| 6888927 | Cruickshank et al. | May 2005 | B1 |
| 6917806 | Chng et al. | Jul 2005 | B2 |
| 6941326 | Kadyk et al. | Sep 2005 | B2 |
| 6961567 | Kuhn | Nov 2005 | B1 |
| 7003327 | Payne et al. | Feb 2006 | B1 |
| 7020685 | Chen et al. | Mar 2006 | B1 |
| 7051080 | Paul et al. | May 2006 | B1 |
| 7069293 | Cox et al. | Jun 2006 | B2 |
| 7092998 | Frietas et al. | Aug 2006 | B2 |
| 7103370 | Creemer | Sep 2006 | B1 |
| 7218921 | Mendiola et al. | May 2007 | B2 |
| 7266379 | Blight et al. | Sep 2007 | B2 |
| 7362311 | Filner et al. | Apr 2008 | B2 |
| 7627680 | Hutcheson et al. | Dec 2009 | B2 |
| 20010016845 | Tribbensee | Aug 2001 | A1 |
| 20010020892 | Helferich | Sep 2001 | A1 |
| 20010047272 | Frietas et al. | Nov 2001 | A1 |
| 20020002596 | Sugiarto et al. | Jan 2002 | A1 |
| 20020065064 | Griffith et al. | May 2002 | A1 |
| 20020065879 | Ambrose et al. | May 2002 | A1 |
| 20020083322 | Lagosanto et al. | Jun 2002 | A1 |
| 20020103881 | Granade et al. | Aug 2002 | A1 |
| 20020109718 | Mansour et al. | Aug 2002 | A1 |
| 20020116500 | Arora et al. | Aug 2002 | A1 |
| 20020143971 | Govindarajan et al. | Oct 2002 | A1 |
| 20020174106 | Martin | Nov 2002 | A1 |
| 20030050046 | Conneely et al. | Mar 2003 | A1 |
| 20030078960 | Murren et al. | Apr 2003 | A1 |
| 20040199574 | Franco et al. | Oct 2004 | A1 |
| 20050113092 | Coppinger et al. | May 2005 | A1 |
| 20050148356 | Ferguson et al. | Jul 2005 | A1 |
| 20050176451 | Helferich | Aug 2005 | A1 |
| 20060030306 | Kuhn | Feb 2006 | A1 |
| 20070178899 | Kuhn | Aug 2007 | A1 |
| Number | Date | Country |
|---|---|---|
| 1914640 | Apr 2006 | EP |
| Number | Date | Country | |
|---|---|---|---|
| 20030158892 A1 | Aug 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60303412 | Jul 2001 | US | |
| 60303391 | Jul 2001 | US |
