US20040203670A1 - Wireless mobile devices having improved operation during network unavailability - Google Patents
Wireless mobile devices having improved operation during network unavailability Download PDFInfo
- Publication number
- US20040203670A1 US20040203670A1 US10/789,687 US78968704A US2004203670A1 US 20040203670 A1 US20040203670 A1 US 20040203670A1 US 78968704 A US78968704 A US 78968704A US 2004203670 A1 US2004203670 A1 US 2004203670A1
- Authority
- US
- United States
- Prior art keywords
- list
- mobile device
- channel
- cache memory
- processing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/59—Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
Abstract
Improved techniques for reducing delays faced by users of mobile devices due to unavailability of wireless networks are disclosed. The techniques facilitate the reduction of delays faced by users of mobile devices during unavailability of wireless networks. A first technique allows mobile devices to communicate with remote servers using asynchronous communications, namely asynchronous requests. Such asynchronous communications allow the processing at a mobile device to continue while the asynchronous request is processed in the background. A second technique pertains to the use of content channels with mobile devices. The content channels are stored and retained in cache memory so that their resources are guaranteed to be locally available, regardless of availability of wireless networks. A third technique pertains to improved list processing within mobile devices such that lists can be manipulated without server interaction. These various techniques can be used separately or in combination.
Description
- This application is a Divisional Application of U.S. application Ser. No. 09/170,879, now U.S. Pat. No.______, entitled “WIRELESS MOBILE DEVICES HAVING IMPROVED OPERATION DURING NETWORK UNAVAILABILITY,” the content of which is hereby incorporated by reference.
- This application claims the benefit of U.S. Provisional Application No. 60/100,663, filed Sep. 16, 1998, and entitled “WIRELESS MOBILE DEVICES HAVING IMPROVED OPERATION DURING NETWORK UNAVAILABILITY”, the content of which is hereby incorporated by reference.
- This application is particularly related to U.S. application Ser. No. 09/172,105, now U.S. Pat. No. 6,289,212, filed concurrently herewith, and entitled “METHOD AND APPARATUS FOR PROVIDING ELECTRONIC MAIL SERVICES DURING NETWORK UNAVAILABILITY”, the content of which is hereby incorporated by reference. This application is also related to (i) U.S. application Ser. No. 08/977,572, now U.S. Pat. No. 6,119,167, filed Jul. 11, 1997, and entitled “PUSHING AND PULLING DATA IN NETWORKS”, and (ii) U.S. application Ser. No. 09/070,668, now U.S. Pat. No. 6,314,108, filed Apr. 30, 1998, and entitled “METHOD AND APPARATUS FOR PROVIDING NETWORK ACCESS OVER DIFFERENT WIRELESS NETWORKS”, the contents of which are hereby incorporated by reference.
- 1. Field of the Invention
- The present invention relates to wireless networks, and more particularly, to operation of wireless mobile devices during unavailability of wireless networks.
- 2. Description of the Related Art
- Wireless networks are often used to transmit messages from one location in a network to a destination location in the network. These messages contain data to be supplied to the destination location. More specifically, the messages include a header portion and a data portion. The header portion includes an address of the destination location, and the data portion contains data. The destination location is, for example, a mobile device or a server. A mobile device typically interacts with wireless networks to receive various types of notifications or to request and receive data from another network to which the wireless network is connected.
- FIG. 1 is a block diagram of a conventional
wireless communication system 10. Thewireless communication system 10 includes aserver 12, awireless network 14, andmobile devices 16. There are n mobile devices 16-1 through 16-n. Theserver 12 is typically a computer system that operates to send and receive messages to and from themobile devices 16. The messages are often blocks of data that are to be transmitted to themobile device 16. As examples, the data can pertain to various types of notifications, electronic mail, news data, configuration information, data files, library files, program files, etc. The messages can also be requests for information (e.g., certain data) that are transmitted from themobile devices 16 to theserver 12. Theserver 12 may also connect to other wired or wireless networks to receive messages from or forward messages to other computer systems. As an example, theserver 12 can be connected to the Internet. For example, theserver 12 can be a proxy server (or link server) coupled to the Internet or a network gateway coupled to a network. The tremendous growth of the Internet in recent years has fueled the need to provide mobile devices such as mobile telephones, personal digital assistants (PDAs) and the like with access to information and services available on the Internet. - The
wireless network 14 typically uses radio transmissions to communicate with themobile devices 16. Thewireless network 14 can use a variety of different networks and communication protocols. Examples of wireless networks include Cellular Digital Packet Data (CDPD), Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) and Time Division Multiple Access (TDMA) to name a few, and each of these wireless networks has different data transfer characteristics such as latency, bandwidth, protocols and connection methods. As examples, protocols can be Internet Protocol (IP), Short Messaging System (SMS) and Unstructured Supplementary Service Data (USSD), and connection methods can include packet switched or circuit switched. - As an example, a message to be sent by the
server 12 to the mobile device 16-2 would contain an address that particularly identifies the mobile device 16-2. The message is then provided by theserver 12 to thewireless network 14. For example, one wireless data network is a packet switched network using a Small Message Server Center (SMSC) which has a relatively small packet size (e.g., 140 bytes). Thewireless network 14 causes the message to be properly routed to the mobile device 16-2 (i.e., in accordance with the address). The transmission between thewireless network 14 and mobile device 16-2 is wireless. The mobile device 16-2 receives the message that has been transmitted to thewireless network 14. The mobile device 16-2 can then store the message and perform predetermined processing actions such as, for example, notifying a user of the mobile device 16-2 of the reception of the message. - In some wireless networks, the server and the mobile devices can be connected by two or more channels. In one case, the server and mobile devices can be connected over a one-way data channel and a two-way data channel. A representative network (e.g., GSM) having such characteristics can use a Short Message Service Center (SMSC) to provide the one-way data channel and an Interworking Function (IFW) to provide the two-way data channel. In such a network, the one-way data channel is often considered a narrowband channel and the two-way data channel is often considered a wideband channel. As an example, the narrowband channel can transfer data at a rate of about 400 bits per second (bps), while the wideband channel can transfer data at a rate of at least 14400 bps. It is thus not uncommon that a server and a mobile device be connected (or connectable) by both a two-way channel and a one-way channel. Typically, the server and the client will decide to use either or both of the channels depending on the urgency of the data, the cost willing to incur, etc. Use of a two-way channel often causes the mobile device to incur charges (i.e., fees) from a carrier that provides the service to the mobile device. In contrast, use of a one-way, narrowband channel is often available at no cost or at a fixed cost regardless of usage.
- One problem with the conventional wireless communication systems is that the operation of mobile devices are very much dependent on availability of their wireless network. In other words, when the wireless network is unavailable, the mobile devices may stop processing user inputs as they wait for a response from a remote server via the wireless network. Unavailability of a wireless network can result from a user of a mobile device exceeding their geographic range of coverage. Unavailability also effectively results from a wireless network having high latencies or a wireless network having sporadic connectivity. Because of the dependency of the operation of mobile devices on the availability of wireless networks, mobile devices often have to wait for resources from a remote server.
- Mobile devices are often provided with cache memories that temporarily store previously requested and obtained resources from remote servers. A cache memory is helpful in reducing the dependency of mobile devices on network availability. However, the cache memory is only helpful when the newly requested resource happens to reside in the cache memory. Hence, if the newly requested resource was not previously requested, then the newly requested resource would not be stored in the cache memory. Also, even if the newly requested resource were at one point in time stored in the cache memory, a reclamation or clean-up algorithm could have removed it from the cache memory to provide space for newer requested resources.
- Another problem with the conventional wireless communication systems is that the dominating application model has a synchronous nature. The synchronous nature causes the application to wait for responses to requests to remote servers (unless satisfied by the cache memory). The wait times are unacceptably long when the wireless network is unavailable to the mobile devices.
- One popular application is a network browser that is used on mobile devices to browse a network such as the Internet. Such as network browser is known as a web browser. The network browser is often requesting resources from remote servers over the wireless network. Hence, network browsers are particularly sensitive to network unavailability (e.g., due to out of coverage, high latencies, or sporadic connectivity). Consequently, it is common for network unavailability to induce significant waits for the users of network browsers on mobile devices.
- Thus, there is a need for techniques to reduce delays faced by users of mobile devices due to unavailability of wireless networks.
- Broadly speaking, the invention relates to improved techniques for reducing delays faced by users of mobile devices due to unavailability of wireless networks. The invention has at least three aspects that facilitate the reduction of delays faced by users of mobile devices during unavailability of wireless networks. A first aspect of the invention allows mobile devices to communicate with remote servers using asynchronous communications, namely asynchronous requests. Such asynchronous communications allow the processing at a mobile device to continue while the asynchronous request is processed in the background. A second aspect of the invention pertains to the use of content channels with mobile devices. The content channels are stored and retained in cache memory so that their resources are guaranteed to be locally available, regardless of availability of wireless networks. A third aspect of the invention pertains to improved list processing within mobile devices such that lists can be manipulated without server interaction. These various aspects of the invention can be used separately or in combination.
- The invention can be implemented in numerous ways, including as a method, a computer readable medium, an apparatus, and a system. Several embodiments of the invention are discussed below.
- As a method for sending a resource request of a mobile device to a remote server through a wireless network, an embodiment of the invention includes the acts of: receiving a resource request, the requested resource being associated with the remote server; determining whether the requested resource is of a synchronous type resource request or of a an asynchronous type resource request; placing the resource request in an outgoing queue and not awaiting a resource reply when the resource request is determined to be an asynchronous type resource request; and when the resource request is determined to be a synchronous type resource request, performing the acts of (i) determining whether the requested resource is present in a local cache memory of the mobile device; (ii) supplying the requested resource from the local cache memory when it is determined that the requested resource is present in the local cache memory; and (iii) sending the resource request to the remote server through the wireless network and awaiting a resource reply when it is determined that the requested resource is not present in the local cache memory.
- As a mobile device that connects to a remote server through a network, an embodiment of the invention includes: an application that executes on the mobile device, the application produces outgoing messages that are to be sent to the remote server; an asynchronous message queue that stores outgoing messages from the application that are to be sent from the mobile device to the remote server; and an asynchronous message manager that manages the sending of the outgoing messages from the asynchronous message queue to the remote server through the network.
- Optionally, the mobile device can further include a cache memory that stores resources likely to be requested by the application, a channel manager that loads a content channel into the cache memory from the remote server through the wireless network, and a list manager that manages lists provided on the mobile device such that lists can be manipulated without interaction with the remote server through the network.
- As a method for storing a content channel from a remote server onto a mobile device through a wireless network, the content channel including resources, an embodiment of the invention includes the acts of: receiving an instruction to load the content channel into a cache memory of the mobile device; determining whether the content channel can fit within a reserved portion of the cache memory of the mobile device; and loading the content channel into the reserved portion of the cache memory from the remote server through the wireless network when the determining determines that the content channel is able to fit within the reserved portion of the cache memory.
- As a method for manipulating a list resident on a mobile device used with a wireless communication system, an embodiment of the invention comprising the acts of: displaying a list on a display device of the mobile device, the list being displayed from a descriptive file; receiving, at the mobile device, a list command to modify the displayed list; locating a list object stored within the mobile device, the list object corresponding to the displayed list; modifying the list object in accordance with the list command; obtaining, from the list object, a pointer to the descriptive file; locating a portion of the descriptive file to be modified using at least the pointer; and modifying the located portion of the descriptive file in accordance with the list command.
- As a computer readable medium including computer program code for sending a resource request of a mobile device to a remote server through a wireless network, an embodiment of the invention includes: computer program code for receiving a resource request, the requested resource being associated with the remote server; computer program code for determining whether the requested resource is of a synchronous type resource request or of a an asynchronous type resource request; computer program code for placing the resource request in an outgoing queue and not awaiting a resource reply when the resource request is an asynchronous type resource request; and computer program code for sending the resource request to the remote server through the wireless network and awaiting a resource reply when the resource request is a synchronous type resource request.
- The advantages of the invention are numerous. Several advantages that embodiments of the invention may include are as follows. One advantage of the invention is that operation of mobile devices is less dependent on network availability. As a result, users of mobile devices experience better responsiveness and less waiting. Another advantage of the invention is that both synchronous and asynchronous messaging are available to mobile devices. Still another advantage of the invention is that a programmer or content author can determine how navigation is performed, namely whether synchronous requests or asynchronous requests are used. Yet another advantage of the invention is that lists can be manipulated on mobile devices without having to support or provide the significant amounts of resources needed to provide scripting. Another advantage of the invention is the ability to obtain and guarantee the presence of certain content channels at mobile devices.
- Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.
- The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
- FIG. 1A is a block diagram of a conventional wireless communication network;
- FIG. 1B is a block diagram of a mobile device according to an embodiment of the invention;
- FIG. 2A is a block diagram of a communication system according to an embodiment of the first aspect the invention;
- FIG. 2B is a flow diagram of mobile device integrated synchronous and asynchronous processing according to an embodiment of the invention;
- FIG. 3 is a flow diagram of asynchronous message send processing according to an embodiment of the invention;
- FIG. 4 is a flow diagram of asynchronous response receive
processing 400 according to an embodiment of the invention; - FIG. 5 is a flow diagram of basic channel initialization processing according to an embodiment of the invention;
- FIG. 6 is a flow diagram of out-of-band initialization processing according to an embodiment of the invention;
- FIGS. 7A and 7B are flow diagrams of direct initialization processing according to an embodiment of the invention;
- FIG. 8 is a diagram of a user interface having a displayed list according to an embodiment of the invention;
- FIG. 9 is a flow diagram of general mobile device action processing according to an embodiment of the invention;
- FIG. 10 is a flow diagram of list command processing according to an embodiment of the invention; and
- FIG. 11 is a block diagram of a representative communication system for use with the invention.
- In a wireless communication system, a wireless network (wireless carrier network) generally supports connection of a plurality of mobile devices to a wired network. The mobile devices communicate with server machines on the wired network to request and receive various resources. The wired network can be of different types. One type of wired network is the Internet. The invention pertains to the facilitating of operation of mobile devices when the wireless network is unavailable such that the mobile devices are unable to communicate with the server machines on the wired network.
- The invention relates to improved techniques for reducing delays faced by users of mobile devices due to unavailability of wireless networks. The invention has at least three aspects that facilitate the reduction of delays faced by users of mobile devices during unavailability of wireless networks. A first aspect of the invention allows mobile devices to communicate with remote servers using asynchronous communications, namely asynchronous requests. Such asynchronous communications allow the processing at a mobile device to continue while the asynchronous request is processed in the background. A second aspect of the invention pertains to the use of content channels with mobile devices. The content channels are stored and retained in cache memory so that their resources are guaranteed to be locally available, regardless of availability of wireless networks. A third aspect of the invention pertains to improved list processing within mobile devices such that lists can be manipulated without server interaction. These various aspects of the invention can be used separately or in combination. When these aspect are used in combination, applications can be created that smoothly operate regardless of periodic unavailability of the network.
- Embodiments of the invention are discussed below with reference to FIGS. 1B-11. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.
- FIG. 1B is a block diagram of a
mobile device 100 according to an embodiment of the invention. Themobile device 100 is particularly suited for wireless communications through a wireless network where connectivity is sporadic or high-latency conditions are present. - The
mobile device 100 includes anapplication 102 that couples to acache memory 104 through aninterface 106. Theapplication 102 is, for example, a network browser (web browser) application that allows a user of themobile device 100 to request and receive resources provided on a remote network (e.g., Internet) that themobile device 100 is able to communicate with. Thecache memory 104 stores resources that have been previously requested and received by themobile device 100. Additionally, as will be discussed below, thecache memory 104 is also used to store various channels and lists that are used to improve performance of themobile device 100. - The
mobile device 100 also includes asynchronous request manager 108 and anasynchronous message manager 110. Thesynchronous request manager 108 manages the synchronous sending and receiving of messages with respect to the remote network awireless communication link 109. The operation of thesynchronous request manager 108 is described in greater detail below with respect with to FIG. 2B. Theasynchronous message manager 110 manages the asynchronous sending of messages with respect to the network via a wireless communication link 111. Theasynchronous message manager 110 is provided so that themobile device 100 can communicate with the remote network in an asynchronous manner. The ability of themobile device 100 to communicate in an asynchronous manner is particularly useful in cases where the wireless network has high-latency conditions or suffers from sporadic connectivity. The operation of theasynchronous message manager 110 is further discussed below with respect to FIG. 3. - The
asynchronous message manager 110 connects to anasynchronous message queue 112 that stores messages that are to be sent to the remote network via theasynchronous message manager 110 and the wireless communication link 111. In general, the messages awaiting transmission to the remote network remain in theasynchronous message queue 112 until theasynchronous message manager 110 determines that the wireless network is available, and then proceeds to service the particular messages stored in theasynchronous message queue 112 such that they are sent to the remote network through the wireless communication link 111 of the wireless network when the wireless network is available. - The
push manager 114 receives pushed messages (e.g., resources) from the remote network over awireless communication link 115. These pushed messages that are received by thepush manager 114 over thewireless communication link 115 are either in response to requests that have been asynchronously sent by themobile device 100 or provided (“pushed”) by a remote server to themobile device 100 connects via the wireless network. - The
mobile device 100 also includes achannel manager 116 and alist manager 118. Thechannel manager 116 operates to load certain content channels into thecache memory 104 of themobile device 100. The content channels are loaded into thecache memory 104 by thechannel manager 116 so that the performance of themobile device 100 is improved with respect to the particular content associated with the content channels loaded in thecache memory 104. In particular, should a user of themobile device 100 request (via the application 102) a resource associated with a content channel stored in thecache memory 104, then the requested resource can be rapidly supplied toapplication 102 via thecache memory 104. Otherwise, when a requested resource is not found in thecache memory 104, the availability of the requested resource at the mobile device is relatively slow because the request must be sent to either thesynchronous request manager 108 or theasynchronous message manager 110 to obtain the resource from a remote server located on the remote network. - The
list manager 118 operates to store one or more lists in a memory 120 (e.g., random-access memory). In one embodiment, thelist manager 120 stores the one or more lists in a persistent memory (such as a persistent portion of the cache memory 104). The lists that are stored in thememory 120 are used to enable thelist manager 118 to manipulate various lists that are used by user interfaces associated with theapplication 102. The user interfaces operate to display the various lists on adisplay 122. Such lists are thus able to be modified locally within themobile device 100 without the need for availability of the wireless network. Thememory 120 can also store resources from the remote network that are used to configure or operate themobile device 100. - Although not shown in FIG. 1, often a mobile device communicates with the remote network through a proxy server. Namely, the mobile device connects to the proxy server through the wireless network and the proxy server in turn connects to the remote network.
- The first aspect of the invention is to provide a mobile device that provides asynchronous communications to a server machine of a wired network. Conventionally, mobile devices (namely, applications executing thereon) have largely requested resources from a remote server through a two-way synchronous channel from the mobile device to the wireless network. The problem with use of a synchronous channel is that the mobile device is inactive while it awaits the response from the remote server. In cases where the wireless network is unavailable (e.g., out-of-range or suffering from high latencies), the mobile device is forced to waits for inordinate periods of time. According to the first aspect of the invention, the mobile devices can use asynchronous communications with the remote server when either the request need not be sent immediately or the response from the remote server is not needed immediately. The network unavailability is temporary such as due to high latencies or sporadic connectivity. With asynchronous communications, an application on the mobile device does not await the sending of the request or the receiving of the response from the remote server.
- The first aspect of the invention is described in greater detail below with respect to FIGS. 2A-4. According to the first aspect of the invention, a mobile device provides asynchronous communications (alone or in combination with synchronous communications) to a server machine of a wired network. With asynchronous communications, the mobile device does not await the sending of the request or receiving of the response from the remote server.
- FIG. 2A is a block diagram of a
communication system 200 according to one embodiment of the first aspect the invention. In this embodiment, thecommunication system 200 utilizes a proxy server between a mobile device and an origin server. Although the proxy server is advantageous, a communication system according to the invention could also operate without the proxy server. - The
communication system 200 includes amobile device 202 and aproxy server 204. The communication between themobile device 202 and theproxy server 204 is through wireless communication channels of a wireless network. The wireless communication channels can be one-way channels or two-way channels. Among other things, themobile device 202 includes an application 206 (i.e., a network browser), acache memory 208, apush manager 210, anasynchronous message queue 212, and anasynchronous message manager 214. - The
mobile device 202 communicates with theproxy server 204 to obtain resources from an origin server located on a remote network. The origin server contains information or resources that themobile device 202 may desire. Initially, the application 206 (i.e., network browser) requests a resource that originates on the origin server. However, often the request need not be immediately serviced and thus can be performed in an asynchronous manner. Asynchronous means that theapplication 206 making the request does not wait to receive the resource; instead, the resource is to be acquired independent of further operation of theapplication 206. As an example, asynchronous requests are particularly useful in certain situations such as where an origin server (remote server) needs to eventually be updated with some event or action that has occurred on themobile device 202, but themobile device 202 does not need to wait until the origin server is updated before it continues. - Thus, where the request is asynchronous, the
application 206 will forward the request to theasynchronous message queue 212. From the perspective of theapplication 206, once the request has been successfully queued, processing by theapplication 206 continues. Then, theasynchronous message manager 214 will manage the retrieval of messages (i.e., resource requests) from theasynchronous message queue 212 and their supply to theproxy server 204 over a wireless communication channel. - In one embodiment, the
application 206 determines whether a particular request should be processed in an asynchronous manner or a synchronous manner. For example, program code of theapplication 206 can direct outgoing requests to the remote network to either a synchronous request manager or theasynchronous message manager 214. Only the asynchronous communication path is depicted in FIG. 2A because the synchronous path is conventionally available. - At the
proxy server 204 the incoming asynchronous messages are temporarily stored in anasynchronous message queue 216. A queue manager 218 at theproxy server 214 operates to service theasynchronous message queue 216. The queue manager 218 forward the messages (i.e., requests) from theasynchronous message queue 216 to the appropriate origin server on the remote network over anetwork link 220. Reply messages from the origin server are directed through the queue manager 218 to a push queue 222. The push queue 222 stores the reply messages until they can be transmitted to themobile device 202 over a wireless communication channel. The wireless communication channel can be a one-way channel or a two-way channel, but is often a one-way channel from theproxy server 204 to themobile device 202. - With the wireless communication channel through the wireless network is available, the reply messages are transmitted from the push queue222 to the
push manager 210 of themobile device 202 via the wireless communication channel. Thepush manager 210 then supplies the incoming reply messages to thecache memory 208. Thepush manager 210 can also notify theapplication 206 that the requested resource has been received. Additionally, thepush manager 210 can also receive reply messages that are not stored in thecache memory 208 but are simply instead used to cause themobile device 202 to perform some action at themobile device 202. As an example, a reply message could instruct themobile device 202 to alter the content of thecache memory 208 or to issue an alert to the user of themobile device 202. - FIG. 2B is a flow diagram of mobile device integrated synchronous and
asynchronous processing 250 according to an embodiment of the invention. The mobile device integrated synchronous andasynchronous processing 250 is, for example, performed by theapplication 102 illustrated in FIG. 1. - The mobile device integrated synchronous and
asynchronous processing 250 begins with adecision block 252 that determines whether a user action has occurred. When thedecision block 252 determines that a user action has not occurred, then the mobile device integrated synchronous andasynchronous processing 250 simply awaits the occurrence of a user action. However, once thedecision block 252 determines that a user action has occurred, then adecision block 254 determines whether the user action is a resource request. When thedecision block 254 determines that the user action is not a resource request, then the mobile device integrated synchronous andasynchronous processing 250 operates to perform 256 other processing. The various types of other processing are not associated with the invention. For example, the other processing may include navigation operations with respect to a user interface of the mobile device. Followingblock 256, themobile device processing 250 returns to repeat thedecision block 252 and subsequent blocks to process additional user actions. - On the other hand, when the
decision block 254 determines that the user action is a resource request, then adecision block 258 determines whether the request is designated to be a synchronous type of request or an asynchronous type of request. As will be discussed below, the designation of synchronous or asynchronous types can be provided by an application developer in creating the application so that the desired operation can be controlled. In any event, when thedecision block 258 determines that the requested resource is of an asynchronous type, then the request is placed 260 in an outgoing queue. The outgoing queue is, for example, theasynchronous message queue 112 illustrated in FIG. 1 or theasynchronous message queue 212 illustrated in FIG. 2A. Followingblock 260, the mobile device integrated synchronous andasynchronous processing 250 returns to repeat thedecision block 252 and subsequent blocks so that additional user actions can be processed. - Alternatively, when the
decision block 258 determines that the request is of a synchronous type, then adecision block 262 determines whether the request resource is present in a cache memory (e.g., thecache memory 104, 208). When the decision block 263 determines that the requested resource is in the cache memory, then the requested resource is retrieved 264 from the cache memory. The requested resource is then displayed 266 on a display screen of the mobile device. Followingblock 266, the mobile device integrated synchronous andasynchronous processing 250 returns to repeat thedecision block 252 and subsequent blocks so that additional user actions can be processed. - On the other hand, when the
decision block 262 determines that the requested resource is not in the cache memory, then the request is sent 268 to a server. The server can be a server machine coupled to a remote network, such as a proxy server or a remote content server. Next, adecision block 270 determines whether a response to the request has been received from the server. When thedecision block 270 determines that a response has not yet been received, then the mobile device integrated synchronous andasynchronous processing 250 awaits the response to arrive. While waiting for the response, the user is waiting because a synchronous type of request causes the application program to wait for the response to the request before continuing. Once the response has been received, the requested resource is displayed 272. Additionally, in certain embodiments, the requested resource would also be stored in the cache memory upon being received. Followingblock 272, the mobile device integrated synchronous andasynchronous processing 250 returns to repeat thedecision block 252 and subsequent blocks so that additional user actions can be processed. - While
blocks - As noted above, the designation of synchronous or asynchronous types can be provided by an application developer in creating the application so that the desired operation can be controlled. With a wireless markup language (WML) programmed application for use on a mobile device, an example of application code that issues an asynchronous request is as follows:
<ASYNC METHOD=POST URL=”/code/del.cgi”> <FIELD NAME=”items” VALUE=”$ITEMS”/> </ASYNC> - The prefix “ASYNC” indicates that asynchronous message transfer is to be used. The method used is a POST method. The Universal Resource Locator (URL) is the location at a remote server where the message is to be sent. The variable “$ITEMS” in the items field contains a delimited list of items to be deleted.
- In contrast, an example of application code that issues a synchronous request is as follows:
<GO URL=”/channel/msg.wml”> VAR NAME=”from” VALUE=joe@xyz.com/> VAR NAME=”subject” VALUE=”lunch?”/> VAR NAME=”msg” VALUE=”Are you available for lunch today?”/> </GO> - Note that no “ASYNC” prefix is used. Hence, it is assumed that synchronous message transfer is to be used. Here, the message pertains to an e-mail message that is supplied to the URL which handles the delivery of the message. The data for the e-mail message is sent with the request to the designated URL.
- FIG. 3 is a flow diagram of asynchronous message send processing300 according to an embodiment of the invention. The asynchronous message send processing 300 is, for example, performed by the
asynchronous message manager 110 illustrated in FIG. 1 or theasynchronous message manager 214 illustrated in FIG. 2A. - The asynchronous message send processing300 begins with a
decision block 302 that determines whether a wireless network is available to the mobile device. Wireless networks often have sporadic connectivity or high latency due to out-of-range, congestion, etc. and thus are temporarily unavailable to mobile devices. When thedecision block 302 determines that the wireless network is not available, then the asynchronous message send processing 300 simply awaits the availability of the wireless network. Once the wireless network becomes available, then adecision block 304 determines whether an asynchronous message queue is empty. The asynchronous message queue is within the mobile device and is, for example, theasynchronous message queue 112 illustrated in FIG. 1 or theasynchronous message queue 112 illustrated in FIG. 2A. - When the
decision block 304 determines that the asynchronous message queue is empty, then the asynchronous message send processing 300 returns to repeat thedecision block 302 and subsequent blocks because there is presently no message waiting to be processed in the asynchronous message queue. On the other hand, when the asynchronous message queue is not empty, then an entry in the asynchronous message queue that is to be sent is selected 306. The selected entry in the asynchronous message queue is then sent 308 to a server via the wireless network. The server can be a proxy server or a remote server on a remote network. Typically, the selected entry is a request for a resource located at the server on the remote network. - After sending the selected entry to the server, a
decision block 310 determines whether a send error has occurred. In other words, thedecision block 310 waits for an acknowledgment that the server has received the selected entry that has been sent. When thedecision block 310 determines that no send error occurred during the sending of the selected entry to server, then the selected entry is removed 312 from the asynchronous message queue. On the other hand, when thedecision block 310 determines that a send error has occurred, adecision block 314 determines whether a retry is desired to resend the selected entry to the server. When thedecision block 314 determines that a retry is desired, then processing returns to repeatblock 308 and subsequent blocks. Alternatively, when thedecision block 314 determines that a retry is not desired, then processing to theblock 312. Followingblock 314, theasynchronous send processing 300 returns to repeat thedecision block 302 and subsequent blocks so that additional entries in the queue can be processed. - FIG. 4 is a flow diagram of asynchronous response receive
processing 400 according to an embodiment of the invention. The asynchronous response receiveprocessing 400 is, for example, performed by thepush manager 114 illustrated in FIG. 1 or thepush manager 210 illustrated in FIG. 2A. - The asynchronous response receive
processing 400 begins with adecision block 402 that determines whether a push message has been received. In one embodiment, a push engine at theproxy server 204 sends a push message obtained from the push queue 222 to thepush manager 210 of themobile device 202 via a wireless communication channel of the wireless network. When thedecision block 402 determines that a push message has not been received, then the asynchronous response receiveprocessing 400 simply awaits the reception of a push message. Once thedecision block 402 determines that a push message has been received, adecision block 404 determines whether the received push message is to be stored in a cache memory. The cache memory is, for example, thecache memory 104 illustrated in FIG. 1 or thecache memory 208 illustrated in FIG. 2A. When thedecision block 404 determines that the received push message should be stored in the cache memory, then the received push message is stored 406 in the cache memory. On the other hand, when thedecision block 404 determines that the received push memory should not be stored in the cache memory, then block 406 is bypassed. - Next, the application is informed408 of the message arrival. Typically, the message is a resource that was previously requested by the application. Hence, often the application is interested in being informed of its arrival. Following
block 408, adecision block 410 determines whether user notification is desired. When thedecision block 410 determines that user notification is desired, the presentation or notification of the previously requested resource is scheduled 412 on the mobile device. Here, the presentation or notification can take a variety of forms, including triggering an audio notification to the user that a previously requested resource is now available or providing a visual notification on a display device of the mobile device. On the other hand, when theuser notification 410 determines that user notification is not desired, then block 412 is bypassed. Followingblock 412, the asynchronous response receiveprocessing 400 has completed its processing of the received push message, and thus returns to repeat thedecision block 402 and subsequent blocks so that additional received push messages can be processed. - The second aspect of the invention pertains to the use of content channels with a mobile device. The content channels facilitate disconnected operation of a mobile device from a wireless network. In particular, by loading content channels into a cache memory of the mobile device before they are needed, the mobile device is less likely to need to access the wireless network. In the case where the wireless network has high-latency or sporadic connectivity, this aspect is particularly useful. The second aspect of the invention is described in greater detail below with respect to FIGS. 5-7E.
- FIG. 5 is a flow diagram of basic
channel initialization processing 500 according to an embodiment of the invention. The basicchannel initialization processing 500 is, for example, performed by thechannel manager 116 illustrated in FIG. 1. - The basic
channel initialization processing 500 reserves 502 a portion of a cache memory for a content channel. The portion of the cache memory of a mobile device is reserved for storage of the content channel. As an example, the cache memory can be thecache memory 104 illustrated in FIG. 1. The reservation of a portion of the cache memory serves to dedicate the portion of the cache memory to the storage of content channels, and thus ensures that resources from content channels will able to be stored in the mobile device. Next, resources of the content channel are pre-loaded 504 from a server into the reserved portion of the content channel. Here, in the background processing or initial provisioning processing, the resources associated with the content channel are loaded into the reserved portion of the cache memory so that an application can later rapidly retrieve any of the content associated with the content channel. These resources are able to be rapidly retrieved because they are located locally within the cache memory and thus no external request to a remote server through the wireless network is needed. - Additionally, the resources of the content channel that are stored in the reserved portion of the cache memory (RAM) are protected506 from cache clean-up or refresh processing. In this regard, the resources associated with the content channel are not subjected to removal from the cache memory or clean-up algorithms which could otherwise over-write or remove the resources of the content channel from the cache memory. In other words, the resources associated with the content channel remain in the cache memory until they are specifically instructed to be removed or refreshed. In other words, the reserved portion of the cache memory provides persistent storage. Following
block 506, the basicchannel initialization processing 500 is complete and ends. - During operation, a user of a mobile device is able to select from certain content channels that they wish to have resident locally on their mobile device. A mobile device can also be provisioned or pre-configured to request certain content channels. Content channels can offer a wide range of content to users. Some examples of content channels include: a stock channel, a sports channel, a traffic channel, etc. The ability to ensure that certain content channels exist on a mobile device is an important advantage because it enables the mobile device to perform processing that would require the contents of the content channels without regard to whether the wireless network is available. Hence, even when the network is not available, the mobile device is able to operate properly because the appropriate content channel has been pre-loaded on the mobile device.
- FIG. 6 is a flow diagram of out-of-
band initialization processing 600 according to an embodiment of the invention. Out-of-band initialization pertains to initialization performed when a mobile device is provisioned for use. The out-of-band initialization processing 600 begins with adecision block 602 that determines whether a content channel is to be loaded. When thedecision block 602 determines that no content channel is to be loaded, then the out-of-band initialization processing is not invoked. On the other hand, when thedecision block 602 determines that a content channel is to be loaded, then a channel specification is received 604. A channel specification describes the content channel. Typically, the channel specification would be received from a remote server (e.g., a proxy server or a content server). - Next, a
decision block 606 determines whether the particular content channel will fit in the available reserved memory. A channel specification specifies the amount of reserved memory it requires, and this amount can be compared with an available amount of memory space in the reserved portion of the cache memory for the storing of content channels. When thedecision block 606 determines that the particular content channel does not fit in the available reserved memory, then adecision block 608 determines whether on-channel failure notifications are requested. When thedecision block 608 determines that on-channel failure notifications are requested, then the on-channel failure notifications are performed 610. On the other hand, when thedecision block 608 determines that no on-channel failure notifications are required, then theblock 610 is bypassed. Followingblock 610, the out-of-band initialization processing 600 is complete and ends without loading the particular content channel in the cache memory. - On the other hand, when the
decision block 606 determines that the particular content channel does fit in the amount of available reserved memory, a channel manager is informed 612 of the channel specification Universal Resource Identifier (URI). This allows the channel manager to setup the content channel. The channel manager is, for example, thechannel manager 116 illustrated in FIG. 1. Next, any desired on-channel creation notifications are performed 614. Additionally, the channel contents are loaded 616 into the cache memory. Theloading 616 of the channel content is performed either in a background mode or during initialization of a mobile device. Followingblock 616, the out-of-band initialization processing 600 is complete and ends. - FIGS. 7A and 7B are flow diagrams of
direct initialization processing 700 according to an embodiment of the invention. Thedirect initialization processing 700 is activated by a user request to install a particular content channel in a mobile device. As an example, thechannel manager 116 illustrated in FIG. 1 is able to perform thedirect initialization processing 700. - The
direct initialization processing 700 begins with adecision block 702. Thedecision block 702 determines whether a request to install a content channel has been received. As long as such a request has not been received, thedirect initialization processing 700 simply awaits the reception of such a request. Once thedecision block 702 determines that a request to install a content channel has been received, then a channel specification is requested 704. The channel specification describes the content channel to be installed. After requesting the channel specification, the channel specification is received 706. The channel specification is typically received 706 from a remote server through the wireless network. - Next, a
decision block 708 determines whether the content channel is able to fit in the available reserved memory of the cache memory. When thedecision block 708 determines that the content channel does not fit in the available reserved memory, then a user is notified 710 that there is not enough memory to install the content channel. As an example, the notification can display a message on a display device of the mobile device. Then, adecision block 712 determines whether any on-channel failure notifications are requested. When thedecision block 712 determines that there are on-channel failure notifications to be performed, the on-channel failure notifications are performed 714. Alternatively, when thedecision block 712 determines that there are no on-channel failure notifications to be performed, theblock 714 is bypassed. Next, the display associated with the mobile device is returned 716 to the previous screen prior to requesting the channel installation because the content channel has not been installed. Following block 716, thedirect initialization processing 700 is complete and ends. - On the other hand, when the
decision block 708 determines that the content channel does fit within the available reserved memory within the cache memory, then the user is notified 718 that the content channel can be installed. Next, adecision block 720 determines whether installation is still desired by the user. When installation is not confirmed by the user, then thedirect installation processing 700 is aborted and the display associated with the mobile device is returned 722 to the previous screen prior to requesting the installation of the content channel. Followingblock 722, thedirect initialization processing 700 is complete and ends. - Alternatively, when the
decision block 720 confirms the initialization request, the channel manager is informed 724 of the channel specification URI. This allows the channel manager to setup the content channel. Then any desired on-channel creation notifications are performed 726. The contents of the channel are then loaded 728 into the reserved portion of the cache memory. After loading the content of the channel into the cache memory, the display device of the mobile device then displays 730 a top-level resource of the content channel that has been installed. Thereafter, the user of the mobile device is able to navigate through the contents of the channel as desired. Followingblock 730, thedirect initialization processing 700 is complete and ends. - The
initialization processing <HANDLE TYPE=”OnChannelOverflow” HREF=”/cgi-bin/channelOverflow.cgi”/> - The content channel is loaded into a reserved portion of the cache memory. This reserved portion of the cache memory can also be referred to as a channel storage section of the cache memory. The loading or pre-loading of the various resources of a channel is referred to as channel crawling. Hence, the loading associated with
block 616 of FIG. 6 and withblock 728 of FIG. 7A can be performed by channel crawl processing described below. Channel crawl processing generally operates to sequence through a resource (primary resource) and those resources that are linked to the primary resource. The primary resource is identified by a channel specification and is, for example, often presented as a URI. - FIGS. 7C-7F are flow diagrams of
channel crawl processing 720 according to an embodiment of the invention. Thechannel crawl processing 720 initially locks 722 the cache memory. In effect, when locked, the cache memory becomes operable in a read-only manner. Next, the channel is marked 724 as being incomplete. Completeness in this context indicates that the entire channel is present in the cache memory. Hence, “incomplete” indicates that the entire channel is not present in the cache memory (namely, the channel storage section). In addition, all resources of the channel are marked 726 as “pending removal”. Pending removal signifies that the particular resources of the channel are eligible to be removed if the channel crawling does not indicate that the resource should remain within the channel storage section of the cache memory. Next, a variable “space used” is set 728 to zero (0). The space used variable is used to count up the amount of space being consumed by a channel as resources are added to the channel. Typically, a channel specification will indicate a maximum amount of memory storage within the channel storage section) it is permitted to consume. - Next, channel resource processing is performed730. The
channel resource processing 730 is, for example, described with respect to FIGS. 7D-7F which describe channel resource processing. The channel resource processing operates to obtain (as needed) and assign resources of the channel into the channel storage section of the cache memory. - Following the
channel resource processing 730, adecision block 732 determines whether the status is currently “terminate crawling” which indicates that thechannel crawl processing 720 should end. When thedecision block 732 determines that the status is not “terminate crawling,” adecision block 734 determines whether the status is “addition complete”. When the status is “addition complete,” then the channel is marked 736 as being complete. Otherwise, the channel is assumed to be incomplete and processing continues. - Following the
block 736, thedecision block 734 when the status is not “addition complete,” or thedecision block 732 when the status is “terminate crawling,” thechannel crawl processing 720 has finished crawling through the channel and now is prepared to complete its processing. In particular, removal of the remaining resources in the channel that are still marked “pending removal” is permitted 738. Once the remaining resources are permitted 738 to be removed, the cache memory can remove them or write over them at a later time as is needed. Followingblock 738, the cache memory is unlocked 740. Once unlocked, the cache memory is available for use by various applications. Followingblock 740, thechannel crawl processing 720 is complete and ends. - FIGS. 7D-7F are flow diagrams illustrating
channel resource processing 742 according to an embodiment of the invention. Thechannel resource processing 742 pertains to an embodiment of the channel resource processing associated withblock 730 in FIG. 7C. - The
channel resource processing 742 initially begins with adecision block 744. Thedecision block 744 determines whether a link level is greater than a maximum link level. When the link level is greater than the maximum link level, then the status is set 746 to “addition complete”. Followingblock 746, thechannel resource processing 742 is complete and returns. - Alternatively, when the
decision block 744 determines that the link level is not greater than the maximum link level, adecision block 748 determines whether the resource being processed is already in the channel and not designated “pending removal”. When thedecision block 748 determines that the resource is already in the channel and not designated “pending removal,” then thechannel resource processing 742 understands that the resource has been previously processed. Hence, in this case, thechannel resource processing 742 also sets 746 the status to “addition complete” and then returns. - On the other hand, when the
decision block 748 determines that the resource is either not in the channel or not “pending removal”, then adecision block 750 determines whether the resource is in the cache memory and also “fresh”. As an example, entries in a cache memory are “fresh” when their expiration date has not been exceeded. When thedecision block 750 determines that the resource is not both in the cache and “fresh”, then the resource is requested 752 in an asynchronous manner. Asynchronous requests of this type were discussed above and allow the processing to proceed without waiting for the resource. Next, the status is set 754 to “addition incomplete”. Followingblock 754, thechannel resource processing 742 is complete and returns. - Alternatively, when the
decision block 750 determines that the resource is both in the cache and “fresh”, then adecision block 756 determines whether the resource size is greater than the available channel space. Here, thedecision block 756 is determining whether the particular resource being processed is able to fit within the available channel space that has been allocated for storage of the channel. The available channel space is determined from the space used variable. When thedecision block 756 determines that the resource size is greater than the available channel space, then overflow notifications are performed 758. Then, the status is set 760 to “terminate crawling”. Followingblock 760, thechannel resource processing 742 is complete and completely returns to the channel crawl processing 720 (at the decision block 732). - On the other hand, when the
decision block 756 determines that the resource size is not greater than the available channel space, then the resource is added 762 to the channel. Then, the space used variable is increased 764 by the resource size. The resource stored in the channel portion of the cache memory is also marked 766 as “not pending removal”. In effect, this places the resource in the channel storage section of the cache memory where it is protected. Next, the link level is incremented 768. The link level indicates the level of the channel which is being currently processed. Although not shown, all returns described also decrement the link level. Complete returns actually return to the initial level and set the link level accordingly. - At this point, the base level resource has been processed. Next, the
channel response processing 742 operates to process the links to other resources that are embedded within the primary resource. This processing of the links is performed in a recursive manner as is detailed below. - The
channel resource processing 742 performschannel resource processing 770 on links within the resource. Hence, at this point, for a link within the resource, the processing returns in a recursive manner to repeat thechannel resource processing 742 beginning atblock 744. When a return occurs, the processing will be exiting theblock 770 in FIG. 7E. However, prior to that, the links are crawled down (via its links) to maximum level so as to bring in the corresponding resources into the channel. Once the processing exits theblock 770, adecision block 772 determines whether the status is “terminate crawling.” When thedecision block 772 determines that the status is “terminate crawling,” then thechannel resource processing 742 completely returns to thechannel crawl processing 720 where it will be exitingblock 730 in FIG. 7C. - On the other hand, when the
decision block 772 determines that the status is not “terminate crawling,” adecision block 776 determines whether the status is “addition incomplete.” When thedecision block 776 determines that the status is “addition incomplete,” then the resource is marked 776 as incomplete. Following thedecision block 776 when the status is not “addition incomplete,” adecision block 778 determines whether there are more links in the resource to be processed. If thedecision block 778 determines that there are more links to be processed, then processing returns to repeatblock 770 and subsequent blocks. - On the other hand, when the
decision block 778 determines that there are no more links in the resource to be processed, then adecision block 780 determines whether the resource being processed is complete. When thedecision block 780 determines that the resource is complete, then the status is set 782 to “addition complete.” Then, followingblock 782, the channel resource processing for the particular link, the link level is decremented 783. Following block 783, thechannel resource processing 742 returns. Here, thechannel resource processing 742 is returning up one level where processing will continue. Alternatively, when thedecision block 780 determines that the resource is not complete, then the status is set 784 to “addition incomplete,” Then the link level is decremented 784. Followingblock 784, thechannel resource processing 742 for the particular link is complete and thus returns to the prior level. - As described above in the
channel resource processing 742, when resources are not available in the cache, or the resources are “stale” if they are in the cache, asynchronous requests for the resources are made. Here, the asynchronous requests are forwarded to a remote server and a reply from the remote server forwards the requested resource back to the mobile device that has issued the request. When such incoming requests are received by the mobile device, they are processed as described below with respect to FIG. 7G. - FIG. 7G is a flow diagram of asynchronous
request completion processing 786 according to an embodiment of the invention. The asynchronous request completion processing initially begins with adecision block 788. Thedecision block 788 determines whether the incoming resource (i.e., the requested resource) is a command. When thedecision block 788 determines that the incoming resource is a command, then the command is processed 790. Here, the processing of commands is separate from the processing of resources that were previously requested such as during the channel crawl processing. Followingblock 790, the asynchronous request completion processing is complete and ends because, in such case, the incoming resource was a command that was received and not a resource that was previously asynchronously requested. - On the other hand, when the
decision block 788 determines that the incoming resource is not a command, then it is assumed that the incoming resource is a resource that was previously asynchronously requested by the mobile device (e.g.,asynchronous message manager 110 or 214). Hence, the incoming resource is stored 792 in the cache memory. Then, adecision block 794 determines whether the incoming resource is destined for the channel (i.e., for the channel storage section of the cache memory). Here, the asynchronousrequest completion processing 786 determines whether the incoming resource is part of a channel that is to be provided on the mobile device. When the incoming resource is destined for a channel, then the channel crawl processing is restarted 796 to determine whether the incoming resource can be added to the channel. In one embodiment, the restarting of the channel crawl processing is utilized to cause the channel to be updated in accordance with the incoming resource as well as to generally update its status and resources. Alternatively, when the resource is not destined for a channel, theblock 796 is bypassed. Followingblock 796, as well as following thedecision block 794 when the resource is not destined for a channel, the asynchronousrequest completion processing 786 is complete and ends. - The third aspect of the invention pertains to improved list processing within mobile devices such that lists can be manipulated without server interaction. Accordingly, improved operation of mobile devices results because list processing can be performed even during periods of network unavailability. The third aspect of the invention is described in greater detail below with respect to FIGS. 8-10.
- FIG. 8 is a diagram of a user interface having a displayed
list 800 according to an embodiment of the invention. The displayedlist 800 is, for example, displayed on a display screen (display device) of a mobile device. Thelist 800 includes afirst item 802, asecond item 804 and athird item 806. The threeitems list 800 can be manipulated using navigation buttons on the mobile device in conjunction withuser command buttons user command button 808 performs a read command for a selected one of the list items, and theuser command button 810 performs a delete command to delete a selected one of the list items. The displayedlist 800 is defined by a representative descriptive file, such as “headers.wml” which is a wireless markup language (WML) file that defines thelist 800. - Conventionally, if the
list 800 were to be modified, the mobile device would need to interact with the server sponsoring thelist 800. For example, if the user of the mobile device were to select thefirst list entry 802 and then select theuser command button 810, the user would request that thefirst list item 802 be removed from thelist 800. However, to implement the change to thelist 800, the mobile device would need to tell the server sponsoring the list (e.g., a remote server) that the user has requested a certain modification. Then, the mobile device would wait for the remote server to modify the master list at the sponsoring server, and then forward an updated descriptive file (e.g., “headers.wml” file) to the mobile device. One problem with the conventional approach is that it requires interaction with the server which tends to introduce undesired latencies and involve significant waiting periods for the user due to periodic wireless network unavailability. - According to the third aspect of the invention, lists displayed on display screens of mobile devices are able to be manipulated without interaction with remote servers through a wireless network. In other words, the displayed lists are able to be manipulated by local processing on the mobile device without any need for wireless network availability. Thereafter, the appropriate sponsoring servers can be informed (e.g., asynchronously) of the modifications that have been made to the lists so that the server can update the master list.
- As shown in FIG. 8, a data structure referred to as a
list object 812 is provided on the mobile device. Thelist object 812 is used to manage and manipulate the displayedlist 800. Thelist object 812 is referred to as “headerlist.lst” and, in this example, corresponds to the “headers.wml” file which pertains to the displayedlist 800. Thelist object 812 includes alist specification 814 that defines the characteristics of the list. Additionally, thelist object 812, after being initiated by a list manager (e.g., list manager 118), includes various list elements that correspond to entries in the list. In particular, thelist object 812 illustrated in FIG. 8 includes afirst list element 816, asecond list element 818 and athird list element 820. Thelist elements entries list 800. - The
list specification 814 contains information on the characteristics of the list. These characteristics include: a base URI for the list, ascending or descending display order, a target element, maximum number of items in the list, a reclamation algorithm, access control and notification handlers. The base URI points to a descriptive file for the list (e.g., headers.wml). The target element is a pointer to a portion of the descriptive file of the displayed list that can be altered by the list manager. The maximum number of items indicates the maximum number of items that the list can hold. The reclamation algorithm indicates a technique by which the memory space being consumed by the list can be reclaimed. The access control indicates which domains on remote servers are permitted to access files associated with the list. The notification handlers operate to trigger certain requests or actions (via URLs) when events occur with respect to the list. For example, a sponsoring server (remote server) is notified when modifications are locally made to a list. Examples of notification handles include: OnDelete, OnInsert, OnLock, OnUnLock, and OnGetList. - Each of the
list elements first list element 816 would have a title “Joe” and thus, thefirst list item 802 in the displayedlist 800 is entitled “Joe”. However, thelist item list 800. The resource location is a pointer to the resource behind the list element. For example, if thefirst list element 816 corresponds to an e-mail from “Joe”, then the resource location (resource_location-1) is a file describing the contents of the email (e.g., joe.wml). The sort key for a list element is used to sort the elements or entries of a list. - The manipulation of a displayed list by local processing is explained by the following representative example. Assume that the
list entry 802 of the displayedlist 800 is being deleted by a user of the mobile device. To initiate the deletion of thelist entry 802, the user would select thelist entry 802 and then activate theuser command button 810. In response to the activation of theuser command button 810, the list manager would locate thecorresponding list element 816 within thelist object 812 that is associated with the displayedlist 800. Then, the list manager would modify thelist object 812 by removing thelist item 816 from thelist object 812. Next, the list manager would locate the target element within the descriptive file (headers.wml) for the displayedlist 800 using the contents of thelist specification 814. Then, within the target element, the list manager would find a target portion pertaining to thelist entry 802 within the descriptive file. One approach to finding the appropriate target portion would be to search the target element using the title (e.g., Joe) of the list entry sought. Once at the target portion within the descriptive file, the list manager would edit the descriptive file by removing the content associated with thelist entry 802. Besides the searching and editing approach, another approach is to regenerate the target elements (or the whole descriptive file) to match the current state of the list elements within the list object. By modifying (e.g., edit or regenerate) the descriptive files for the displayedlist 800, the mobile device is caused to redisplay the displayedlist 800 such that thelist entry 802 is no longer present. At this point, the displayedlist 800 has only two list entries (804 and 806) and thelist object 812 would have only two list elements (818 and 820). Note that all this processing occurs locally on the mobile device without any interaction with the appropriate server via a wireless network. However, to keep the server notified of changes to displayed lists, the notification handlers contained or pointed to by thelist specification 814 are utilized. In this representative example, an on-delete notification handler can be selected and a URL designated by that notification handler can be used to send a notification message to the appropriate server. In one embodiment, the notification messages sent by the mobile machine are asynchronously sent using asynchronous messaging techniques described above. - Although the
list elements list object 802, the list entries could form part of the descriptive file associated with the displayedlist 800. Such an approach may be more memory efficient. - An exemplary list specification (in a WML format) for a user's stock portfolio that can list up to ten (10) stocks as well as delete particular stocks is as follows:
<LIST BASE=”http://stocks.uplanet.com/” HREF=”portfolio.wml” ID=”stocklist”> <!-- maximum of 10 items in the portfolio --> <RESOURCES MAXITEMS=”10” RECLAIM=”FIFO”/> <!-- when the user deletes an item from the list, remove it from the portfolio --> <NOTIFY TYPE=”OnDelete” HREF=”delete.cgi”/> </LIST>. - The target document can be the following WML deck, with a single card shown. The text in the card presents the title of the list. Also, a menu option provides a link to a menu of commands that can operate on the currently selected options.
<WML> <CARD> <DO TYPE=”OPTION” LABEL=”Menu” ONCLICK=”menu.wml”/> My Stock Portfolio <SELECT ID=”stocklist” KEY=”K”> <!-- list entries will be placed here as OPTIONs --> </SELECT> </CARD> </WML> - FIG. 9 is a flow diagram of general mobile device action processing900 according to an embodiment of the invention. The general mobile device action processing 900 indicates how a list manager is activated.
- The general
mobile device processing 900 begins with adecision block 902 that determines whether user action has occurred. If no user action has occurred, then the generalmobile device processing 900 awaits the reception of user action. Alternatively, adecision block 904 is provided to determine whether pushed content has arrived. When thedecision block 904 determines that no pushed content has arrived, then the generalmobile device processing 900 awaits the arrival of pushed content. Hence, the generalmobile device processing 900 is in a wait state until either user action has occurred or pushed content has arrived at the mobile device. Once either of these has occurred, the generalmobile device processing 900 continues. - When the general
mobile device processing 900 continues, adecision block 906 determines whether the invoking action is a list command. When thedecision block 906 determines that the invoking action is a list command, then the list command is forwarded 908 to the list manager. The list manager then processes the list command. As an example, a list command can be signified by having the prefix “listmgr:”. On the other hand, when thedecision block 906 determines that the invoking action for either the user action or the received push content is not a list command, then other action processing 910 is performed. The other action processing 910 can be convention processing of commands. Followingblock 910 as well as followingblock 908, the generalmobile device processing 900 is complete and ends. While the generalmobile device processing 900 is described as generalized processing, it should be recognized that FIG. 9 is illustrated to indicate how and when certain commands are directed to a list manager for their processing. - FIG. 10 is a flow diagram of
list command processing 1000 according to an embodiment of the invention. Thelist command processing 1000 is, for example, performed by thelist manager 118 illustrated in FIG. 1. - The
list command processing 1000 begins with adecision block 1002. Thedecision block 1002 determines whether a list command has been received. Until a list command has been received, thelist command processing 1000 is in a wait state. Once the decision block determines that a list command has been received, thelist command processing 1000 continues. Once thelist command processing 1000 continues, a list object is modified 1004 based on the list command. Next, the target element within the target document is identified 1006. Then, within the target element that has been identified, a portion of the target element to be modified is located 1008. Then, the portion of the target element is modified 1010 based on the list command. For example, if the list command requested deletion of a list entry, then a portion of the target element would be removed from the target document. On the other hand, if the list command requested insertion, then additional content would be inserted into the target document at the portion (i.e., a particular position) of the target element. - After having modified the target document in accordance with the list command, an appropriate notification handler is identified1012. Typically, the appropriate notification handler can be selected based on the type of list command that has been processed. After identifying 1012 the appropriate notification handler, the appropriate notification handler is invoked 1014 to notify a sponsoring server (remote server) of the modifications made to the target document. The sponsoring server typically holds a master of the target document and thus the notification to the sponsoring server allows the server to modify the master document in accordance with the user's actions on the mobile device. In one embodiment, the notification provided to the server is performed by an asynchronous message that is sent by an asynchronous message handler such as described above. Asynchronous notification is preferred because the mobile device need not wait for any server actions which, if required, would induce latencies or delays to the user of the mobile device. Following
block 1014, thelist command processing 1000 is complete and ends. - FIG. 11 is a block diagram of a
representative communication system 1100 for use with the invention. Thecommunication system 1100 includes awired section 1102 and awireless section 1104. Thewired section 1102 includes a network 1106 and anetwork gateway 1108. In one embodiment, the network 1106 is the Internet, which represents a large number of interconnected computers. In another embodiment, the network 1106 is an intranet or private network of computers. - The
network gateway 1108 operates to provide a gateway from thewired section 1102 and thewireless section 1104. Thenetwork gateway 1108 serves as a primary transition point between the wireless communication of thewireless section 1104 and the wired communication of thewired section 1102. Thenetwork gateway 1108 receives the incoming content request from thecarrier network 1114 and performs protocol conversion as necessary. Thenetwork gateway 1108 will normally perform some protocol translation and other account management and verification operations. Thenetwork gateway 1108 includes an accountinformation storage area 1110 that stores account, configuration and other information. Thewireless section 1104 includes acarrier network 1114 and at least one remotewireless computing device 1116. Thenetwork gateway 1108 also receives messages from the network 1106 and forwards them to the appropriate remote computing devices. - The
remote computing device 1116 can, for example, be a mobile phone, a Personal Digital Assistant (PDA), or a portable general purpose computer. The remotewireless computing device 1116 includes adisplay 1118 for displaying screens or pages of information, aremote wireless browser 1120, andnavigation buttons remote wireless browser 1120 is usually an application program that executes on theremote computing device 1116. Theremote wireless browser 1120 provides the screens or pages of information to be displayed on thedisplay 1118. Thenavigation buttons display 1118 by theremote wireless browser 1120. The remotewireless computing device 1116 can also include an alphanumeric keypad (not shown) that allows a user to enter alphanumeric information, though such is not necessary as alphanumeric information can also be entered using a dial screen displayed on thedisplay 1118 with selections being made using thenavigation buttons remote wireless browser 1120, a user is able to access information located on the network 1106. According to the invention, theremote wireless browser 1120 of themobile device 1116 is able to operate with substantially less waiting for server interaction, which is particularly beneficial when thewireless section 1104 is unable to communicate with thewired section 1102. - Typically, the
wireless section 1104 will include a plurality ofremote wireless browsers 1120, each of which executes on a different remote computing device. The configuration and other information stored in the accountinformation storage area 1110 can store service limitations, security limitations, pre-selected content channels, preference information, screen configuration information, and the like for each of theremote wireless browsers 1120. The accountinformation storage area 1110 can also store data or pages of data that are of interest to theremote wireless browsers 1120. The stored data or pages can operate as a cache of information previously requested from the network 1106 or can operate as an information server within thenetwork gateway 1108. For example, as an information server, the storage pages can represent pages to be displayed by the remote wireless browsers. - In one embodiment, the
remote wireless browser 1120 understands and displays WML content type which was designed for mobile devices. The specification for WML, “Wireless Application Protocol Wireless Markup Language Specification” (WAP WML), Apr. 30, 1998 is hereby incorporated by reference. - The advantages of the invention are numerous. Several advantages that embodiments of the invention may include are as follows. One advantage of the invention is that operation of mobile devices is less dependent on network availability. As a result, users of mobile devices experience better responsiveness and less waiting. Another advantage of the invention is that both synchronous and asynchronous messaging are available to mobile devices. Still another advantage of the invention is that a programmer or content author can determine how navigation is performed, namely whether synchronous requests or asynchronous requests are used. Yet another advantage of the invention is that lists can be manipulated on mobile devices without having to support or provided the significant amounts of resources needed to provide scripting. Another advantage of the invention is the ability to obtain and guarantee the presence of certain content channels at mobile devices.
- The many features and advantages of the present invention are apparent from the written description, and thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.
Claims (16)
1-29 (Cancelled).
30. A method for storing a content channel from a remote server onto a mobile device through a wireless network, the content channel including resources, said method comprising the acts of:
(a) receiving an instruction to load the content channel into a cache memory of the mobile device;
(b) determining whether the content channel can fit within a reserved portion of the cache memory of the mobile device; and
(c) loading the content channel into the reserved portion of the cache memory from the remote server through the wireless network when said determining (b) determines that the content channel is able to fit within the reserved portion of the cache memory.
31. A method as recited in claim 30 , wherein said method further comprises:
(d) performing automatic notifications to either the mobile device or the remote server based on the success or failure of the storing of the content channel on the mobile device.
32. A method as recited in claim 30 , wherein the content channel is defined by a channel specification.
33. A method as recited in claim 30 , wherein the reserved portion of the cache memory is protected from cache clean-up or refresh processing being used in a remaining portion of the cache memory, thus once loaded the presence of the content channel within the cache memory is guaranteed.
34. A method for manipulating a list resident on a mobile device used with a wireless communication system, said method comprising the acts of:
(a) displaying a list on a display device of the mobile device, the list being displayed from a descriptive file;
(b) receiving, at the mobile device, a list command to modify the displayed list;
(c) locating a list object stored within the mobile device, the list object corresponding to the displayed list;
(d) modifying the list object in accordance with the list command;
(e) obtaining, from the list object, a pointer to the descriptive file; and
(f) modifying at least a portion of the descriptive file in accordance with the list command.
35. A method as recited in claim 34 , wherein said acts of (a)-(f) are performed locally by the mobile device without interaction with remote servers of the wireless communication system.
36. A method as recited in claim 34 , wherein said method further comprises:
(g) asynchronously notifying a remote server of the modification made to the displayed list.
37. A method as recited in claim 34 , wherein the descriptive file is a markup language file.
38. A method as recited in claim 34 , wherein said method further comprising:
(g) locating, prior to said modifying (f), a portion of the descriptive file to be modified using at least the pointer.
39. A method as recited in claim 38 , wherein said locating (g) of the portion of the descriptive file comprises:
(g1) identifying a target element within the descriptive file based on the pointer; and
(g2) locating within the target element the portion of the descriptive file to be modified.
40. A method as recited in claim 39 , wherein said locating (g2) comprises:
obtaining a reference indicator for a list element of the list object that has been modified; and
searching the target element for the reference indicator to locate the portion of the descriptive file to be modified.
41. A method as recited in claim 38 , wherein said modifying (f) comprises:
editing the portion of the descriptive file to be modified in accordance with the list command.
42. A method as recited in claim 34 , wherein said modifying (f) comprises:
regenerating the descriptive file in accordance with the list command.
43. A method as recited in claim 34 , wherein at least a portion of the list object is stored within the descriptive file.
44. (Cancelled).
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/789,687 US20040203670A1 (en) | 1998-09-16 | 2004-02-27 | Wireless mobile devices having improved operation during network unavailability |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10066398P | 1998-09-16 | 1998-09-16 | |
US17087998P | 1998-10-13 | 1998-10-13 | |
US10/789,687 US20040203670A1 (en) | 1998-09-16 | 2004-02-27 | Wireless mobile devices having improved operation during network unavailability |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/170,879 Division US6721288B1 (en) | 1998-09-16 | 1998-10-13 | Wireless mobile devices having improved operation during network unavailability |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040203670A1 true US20040203670A1 (en) | 2004-10-14 |
Family
ID=26797412
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/170,879 Expired - Lifetime US6721288B1 (en) | 1998-09-16 | 1998-10-13 | Wireless mobile devices having improved operation during network unavailability |
US10/789,687 Abandoned US20040203670A1 (en) | 1998-09-16 | 2004-02-27 | Wireless mobile devices having improved operation during network unavailability |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/170,879 Expired - Lifetime US6721288B1 (en) | 1998-09-16 | 1998-10-13 | Wireless mobile devices having improved operation during network unavailability |
Country Status (4)
Country | Link |
---|---|
US (2) | US6721288B1 (en) |
EP (1) | EP0993165A3 (en) |
JP (1) | JP2000148572A (en) |
KR (1) | KR20000023230A (en) |
Cited By (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010017855A1 (en) * | 2000-02-29 | 2001-08-30 | Matsushita Electric Industrial Co., Ltd. | Portable telephone with URL accessing function |
US20010056444A1 (en) * | 2000-04-07 | 2001-12-27 | Motoki Ide | Communication terminal device |
US20050015500A1 (en) * | 2003-07-16 | 2005-01-20 | Batchu Suresh K. | Method and system for response buffering in a portal server for client devices |
US20060230149A1 (en) * | 2005-04-07 | 2006-10-12 | Cluster Resources, Inc. | On-Demand Access to Compute Resources |
US20060235872A1 (en) * | 2005-04-19 | 2006-10-19 | Research In Motion Limited | Integration of push services with applications |
US20070180125A1 (en) * | 2005-07-22 | 2007-08-02 | Michael Knowles | Secure method of synchronizing cache contents of a mobile browser with a server |
US20070198634A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | Method for training a server for content delivery based on communication of state information from a mobile device browser |
US20070198715A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | System and method for communicating state management between a browser user-agent and a server |
US20070198716A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | Method of controlling delivery of multi-part content from an origin server to a mobile device browser via a server |
US20070198734A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | Method for communicating state information between a server and a mobile device browser with version handling |
US20070255910A1 (en) * | 2006-04-28 | 2007-11-01 | Research In Motion Limited | Method of reflecting on another device an addition to a browser cache on a handheld electronic device, and associated device |
US7292844B2 (en) * | 1998-11-17 | 2007-11-06 | Geobrowser Innovations, Lp | Geographical web browser, methods, apparatus and systems |
US20080045248A1 (en) * | 2006-08-18 | 2008-02-21 | Tim Neil | Associating a label with a queued message at a mobile device |
US20080098486A1 (en) * | 2006-10-20 | 2008-04-24 | Verizon Business Financial Management Corporation | Integrated data access |
US20080299960A1 (en) * | 2007-06-01 | 2008-12-04 | Kendall Gregory Lockhart | System and method for managing message transmissions on a mobile device |
US20090003340A1 (en) * | 2007-06-28 | 2009-01-01 | Rebelvox, Llc | Telecommunication and multimedia management method and apparatus |
EP2073486A1 (en) | 2007-12-17 | 2009-06-24 | Alcatel Lucent | Method for providing multimedia service to a mobile device in case of foreseen network unavailability |
US20090306999A1 (en) * | 2008-06-06 | 2009-12-10 | Microsoft Corporation | Conversational parallelism for message processing |
US7756525B1 (en) * | 2002-09-16 | 2010-07-13 | Teradata Us, Inc. | Continuous dynamic mobile querying |
US20100179980A1 (en) * | 2009-01-14 | 2010-07-15 | Movidilo S.L. | Cache system for mobile communications devices |
US20110081895A1 (en) * | 2009-10-06 | 2011-04-07 | Fujifilm Corporation | Information browsing system |
US20110093567A1 (en) * | 2009-10-15 | 2011-04-21 | Electronics And Telecommunications Research Institute | Mobile terminal for providing mobile cloud service and operation method thereof |
US8055247B1 (en) * | 2006-12-21 | 2011-11-08 | Sprint Communications Company L.P. | Mobile audible data services |
WO2014036078A2 (en) * | 2012-08-28 | 2014-03-06 | Memory Technologies Llc | Dynamic central cache memory |
US9015324B2 (en) | 2005-03-16 | 2015-04-21 | Adaptive Computing Enterprises, Inc. | System and method of brokering cloud computing resources |
US9063850B2 (en) | 2008-02-28 | 2015-06-23 | Memory Technologies Llc | Extended utilization area for a memory device |
US9164804B2 (en) | 2012-06-20 | 2015-10-20 | Memory Technologies Llc | Virtual memory module |
US9208078B2 (en) | 2009-06-04 | 2015-12-08 | Memory Technologies Llc | Apparatus and method to share host system RAM with mass storage memory RAM |
US9231886B2 (en) | 2005-03-16 | 2016-01-05 | Adaptive Computing Enterprises, Inc. | Simple integration of an on-demand compute environment |
US9247523B1 (en) | 2012-01-17 | 2016-01-26 | Cox Communications, Inc. | System, method and device for initiating actions for mobile devices prior to a mobile user entering problem zones |
US9417998B2 (en) | 2012-01-26 | 2016-08-16 | Memory Technologies Llc | Apparatus and method to provide cache move with non-volatile mass memory system |
US9634969B2 (en) | 2007-06-28 | 2017-04-25 | Voxer Ip Llc | Real-time messaging method and apparatus |
US10333862B2 (en) | 2005-03-16 | 2019-06-25 | Iii Holdings 12, Llc | Reserving resources in an on-demand compute environment |
US10375139B2 (en) | 2007-06-28 | 2019-08-06 | Voxer Ip Llc | Method for downloading and using a communication application through a web browser |
US11095583B2 (en) | 2007-06-28 | 2021-08-17 | Voxer Ip Llc | Real-time messaging method and apparatus |
US11226771B2 (en) | 2012-04-20 | 2022-01-18 | Memory Technologies Llc | Managing operational state data in memory module |
US11467883B2 (en) | 2004-03-13 | 2022-10-11 | Iii Holdings 12, Llc | Co-allocating a reservation spanning different compute resources types |
US11494235B2 (en) | 2004-11-08 | 2022-11-08 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11522952B2 (en) | 2007-09-24 | 2022-12-06 | The Research Foundation For The State University Of New York | Automatic clustering for self-organizing grids |
US11526304B2 (en) | 2009-10-30 | 2022-12-13 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US11630704B2 (en) | 2004-08-20 | 2023-04-18 | Iii Holdings 12, Llc | System and method for a workload management and scheduling module to manage access to a compute environment according to local and non-local user identity information |
US11650857B2 (en) | 2006-03-16 | 2023-05-16 | Iii Holdings 12, Llc | System and method for managing a hybrid computer environment |
US11652706B2 (en) | 2004-06-18 | 2023-05-16 | Iii Holdings 12, Llc | System and method for providing dynamic provisioning within a compute environment |
US11720290B2 (en) | 2009-10-30 | 2023-08-08 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US11960937B2 (en) | 2004-03-13 | 2024-04-16 | Iii Holdings 12, Llc | System and method for an optimizing reservation in time of compute resources based on prioritization function and reservation policy parameter |
Families Citing this family (152)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7831930B2 (en) | 2001-11-20 | 2010-11-09 | Universal Electronics Inc. | System and method for displaying a user interface for a remote control application |
KR20010093311A (en) * | 1999-02-04 | 2001-10-27 | 린다.알.스피어 | A telecommunications gateway |
KR20010021089A (en) * | 1999-07-23 | 2001-03-15 | 스테븐 디.피터스 | Method and system for providing electronic mail services to mobile devices with efficient use of network bandwidth |
US20010015977A1 (en) * | 1999-10-08 | 2001-08-23 | Stefan Johansson | Selective reception |
US20010014085A1 (en) * | 1999-10-08 | 2001-08-16 | Microsoft Corporation | Originator authentication |
US7299405B1 (en) * | 2000-03-08 | 2007-11-20 | Ricoh Company, Ltd. | Method and system for information management to facilitate the exchange of ideas during a collaborative effort |
US7653925B2 (en) | 1999-11-17 | 2010-01-26 | Ricoh Company, Ltd. | Techniques for receiving information during multimedia presentations and communicating the information |
US7213063B2 (en) * | 2000-01-18 | 2007-05-01 | Lucent Technologies Inc. | Method, apparatus and system for maintaining connections between computers using connection-oriented protocols |
AU3058101A (en) * | 2000-02-04 | 2001-08-14 | Matsushita Electric Industrial Co., Ltd. | Information terminal |
US20020016645A1 (en) * | 2000-03-31 | 2002-02-07 | Simon Jacobs | Configurable scheduling system |
EP1143350A1 (en) * | 2000-04-03 | 2001-10-10 | Koninklijke KPN N.V. | A method and a system for retrieving data of a data network |
WO2001082031A2 (en) * | 2000-04-26 | 2001-11-01 | Portable Internet Inc. | Portable internet services |
AU2001259486A1 (en) * | 2000-05-05 | 2001-11-20 | @ Hand Corporation | System and method for extending an enterprise network to mobile devices |
GB2364483A (en) * | 2000-06-30 | 2002-01-23 | Nokia Oy Ab | Accessing more than one item of information from a remote server |
US7149511B1 (en) | 2000-08-31 | 2006-12-12 | Rosetta-Wireless Corporation | Wireless intelligent personal server |
US7712125B2 (en) | 2000-09-08 | 2010-05-04 | Ack Ventures Holdings, Llc | Video interaction with a mobile device and a video device |
US7155517B1 (en) * | 2000-09-28 | 2006-12-26 | Nokia Corporation | System and method for communicating reference information via a wireless terminal |
US7562147B1 (en) * | 2000-10-02 | 2009-07-14 | Microsoft Corporation | Bi-directional HTTP-based reliable messaging protocol and system utilizing same |
DE10049146A1 (en) * | 2000-10-04 | 2002-04-11 | Orga Kartensysteme Gmbh | Information transmission over the signaling channel of a mobile radio network |
KR20020050490A (en) * | 2000-12-21 | 2002-06-27 | 구자홍 | Union remote controller information providing system and using method of the same |
SE518751C2 (en) * | 2001-01-03 | 2002-11-19 | Microsoft Corp | Method and system where an external server receives information on individual mobile terminals' radio transmission capacity |
US20020161826A1 (en) * | 2001-01-25 | 2002-10-31 | Carlos Arteaga | System and method for remote communication transactions |
US20020156896A1 (en) * | 2001-02-09 | 2002-10-24 | Peter Lin | System and method for providing a gateway between mobile two-way messaging devices and remote computer networks |
EP1379963A4 (en) * | 2001-03-19 | 2009-03-11 | Microsoft Corp | System and method for communications management and data exchange |
JP2002300654A (en) * | 2001-03-30 | 2002-10-11 | Sumitomo Heavy Ind Ltd | Portable radio terminal, method, network system, recording medium, computer program |
US6965765B2 (en) * | 2001-05-17 | 2005-11-15 | Palmsource, Inc. | Transactional message-queue communication for wirelessly networked devices system and method |
US7493210B2 (en) * | 2001-08-09 | 2009-02-17 | International Business Machines Corporation | Vehicle navigation method |
US6965770B2 (en) * | 2001-09-13 | 2005-11-15 | Nokia Corporation | Dynamic content delivery responsive to user requests |
US20030061273A1 (en) * | 2001-09-24 | 2003-03-27 | Intel Corporation | Extended content storage method and apparatus |
WO2003030026A2 (en) * | 2001-10-02 | 2003-04-10 | Symbian Limited | Mobile web browsing device |
US7233655B2 (en) * | 2001-10-03 | 2007-06-19 | Accenture Global Services Gmbh | Multi-modal callback |
US7441016B2 (en) * | 2001-10-03 | 2008-10-21 | Accenture Global Services Gmbh | Service authorizer |
US7472091B2 (en) * | 2001-10-03 | 2008-12-30 | Accenture Global Services Gmbh | Virtual customer database |
US7254384B2 (en) * | 2001-10-03 | 2007-08-07 | Accenture Global Services Gmbh | Multi-modal messaging |
US7640006B2 (en) * | 2001-10-03 | 2009-12-29 | Accenture Global Services Gmbh | Directory assistance with multi-modal messaging |
CN100366025C (en) | 2001-12-07 | 2008-01-30 | 捷讯研究有限公司 | System and method of managing information distribution to mobile stations |
JP4386732B2 (en) | 2002-01-08 | 2009-12-16 | セブン ネットワークス, インコーポレイテッド | Mobile network connection architecture |
US20030134628A1 (en) * | 2002-01-15 | 2003-07-17 | Litwin Louis Robert | On a mobile device |
US7275105B2 (en) * | 2002-01-16 | 2007-09-25 | Laszlo Systems, Inc. | Enabling online and offline operation |
EP1330094A1 (en) * | 2002-01-21 | 2003-07-23 | Hewlett-Packard Company | Process and apparatus for performing data transfer with a network |
JP2003304573A (en) * | 2002-02-08 | 2003-10-24 | Ntt Docomo Inc | Communication system, communication device, and communication method |
JP2003281058A (en) * | 2002-03-25 | 2003-10-03 | Canon Inc | Communication terminal device, e-mail reception processing method, program and storage medium |
DE10224506A1 (en) * | 2002-05-31 | 2003-12-11 | Artem Gmbh | Wireless communication system and method for operating a wireless communication system |
US9813514B2 (en) * | 2002-06-12 | 2017-11-07 | Good Technology Holdings Limited | Information repository system including a wireless device and related method |
GB0215808D0 (en) * | 2002-07-09 | 2002-08-14 | Ibm | A system and method for managing transactions in a messaging system |
US8245128B1 (en) * | 2002-07-17 | 2012-08-14 | Oracle International Corporation | Intelligent client agent for a hybrid online/offline application |
US20040203824A1 (en) * | 2002-07-26 | 2004-10-14 | Mock Von A. | Method and mobile station for determining a communication channel for a communication session |
US8010706B1 (en) * | 2002-08-05 | 2011-08-30 | Purple Communications, Inc. | Method of and system for enabling offline applications |
US20090125591A1 (en) * | 2002-09-30 | 2009-05-14 | Ficus Kirkpatrick | Instant messaging proxy apparatus and method |
US20110276636A1 (en) * | 2010-03-29 | 2011-11-10 | Konaware, Inc. | Efficient transactional messaging between loosely coupled client and server over multiple intermittent networks with policy based routing |
US7343168B2 (en) | 2002-11-08 | 2008-03-11 | Openwave Systems Inc. | Asynchronous messaging based system for publishing and accessing content and accessing applications on a network with mobile devices |
US7302254B2 (en) | 2002-11-08 | 2007-11-27 | Openwave Systems Inc. | MMS based photo album publishing system |
US8250168B2 (en) | 2003-01-03 | 2012-08-21 | Openwave Systems Inc. | Methods for accessing published contents from a mobile device |
US7660870B2 (en) | 2003-01-03 | 2010-02-09 | Openwave Systems Inc. | Method and apparatus for enhancing discoverability and usability of data network capability of a mobile device |
US7917468B2 (en) | 2005-08-01 | 2011-03-29 | Seven Networks, Inc. | Linking of personal information management data |
US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
US7853563B2 (en) | 2005-08-01 | 2010-12-14 | Seven Networks, Inc. | Universal data aggregation |
EP1634162B1 (en) | 2003-01-31 | 2010-07-14 | Visto Corporation | Asynchronous real-time retrieval of data |
GB2398199A (en) * | 2003-02-10 | 2004-08-11 | Nokia Corp | A system for transferring content audio and video data from a provider to a personal digital assistant |
GB0308991D0 (en) | 2003-04-17 | 2003-05-28 | Psion Digital Ltd | A data access replication or communication system comprising a distributed software application |
GB0308989D0 (en) * | 2003-04-17 | 2003-05-28 | Psion Digital Ltd | A data access replication or communication system comprising a message queuing communications platform |
US7673307B2 (en) * | 2003-05-29 | 2010-03-02 | International Business Machines Corporation | Managing transactions in a messaging system |
US20050037787A1 (en) * | 2003-06-27 | 2005-02-17 | Rosett-Wireless Corporation | Wireless intelligent portable-server system (WIPSS) |
DE60318847T2 (en) * | 2003-09-05 | 2009-01-15 | Sap Ag | Real-time messaging in cooperative network environments |
US20060008256A1 (en) * | 2003-10-01 | 2006-01-12 | Khedouri Robert K | Audio visual player apparatus and system and method of content distribution using the same |
US20130097302A9 (en) * | 2003-10-01 | 2013-04-18 | Robert Khedouri | Audio visual player apparatus and system and method of content distribution using the same |
US7689712B2 (en) * | 2003-11-26 | 2010-03-30 | Ricoh Company, Ltd. | Techniques for integrating note-taking and multimedia information |
DE602005006391T2 (en) * | 2004-02-27 | 2009-06-04 | Research In Motion Ltd., Waterloo | SYSTEM AND METHOD FOR ASYNCHRONOUS COMMUNICATION WITH WEB SERVICES USING MESSAGE DEFINITIONS |
US20050262055A1 (en) * | 2004-05-20 | 2005-11-24 | International Business Machines Corporation | Enforcing message ordering |
JP2006085365A (en) * | 2004-09-15 | 2006-03-30 | Ricoh Co Ltd | Proxy device, service use device, proxy program, service use program, recording medium and asynchronous operation provision method |
US7477623B2 (en) * | 2004-12-17 | 2009-01-13 | Santera Systems, Inc. | Methods, systems, and computer program products for caching and re-using bearer channels for voice-over-packet (VoP) sessions involving wireless entities |
US7877703B1 (en) | 2005-03-14 | 2011-01-25 | Seven Networks, Inc. | Intelligent rendering of information in a limited display environment |
US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
US7801530B2 (en) * | 2005-04-27 | 2010-09-21 | Cisco Technology, Inc. | Caching content at a cell site |
US8200782B2 (en) * | 2005-04-29 | 2012-06-12 | Hewlett-Packard Development Company, L.P. | Communication with a mobile device |
US7581045B2 (en) * | 2005-06-14 | 2009-08-25 | Intel Corporation | Method, system, and article of manufacture for mapping programming interfaces |
US8805929B2 (en) * | 2005-06-20 | 2014-08-12 | Ricoh Company, Ltd. | Event-driven annotation techniques |
WO2006136660A1 (en) | 2005-06-21 | 2006-12-28 | Seven Networks International Oy | Maintaining an ip connection in a mobile network |
DE102005044146A1 (en) * | 2005-09-15 | 2007-03-29 | Siemens Ag | Mobile communication device e.g. mobile telephone, for radio communication, has unit for transmitting and receiving messages that include packets, where part of packets is stored so that packets are transmitted after rebuilding connection |
US7675933B2 (en) * | 2005-09-23 | 2010-03-09 | Palm, Inc. | System and method for enabling radio operations on a wireless computing device |
US8177632B2 (en) | 2005-11-09 | 2012-05-15 | Wms Gaming Inc. | Information flow control for gaming machines requiring server support |
US7769395B2 (en) | 2006-06-20 | 2010-08-03 | Seven Networks, Inc. | Location-based operations and messaging |
US7730192B2 (en) * | 2006-03-20 | 2010-06-01 | Microsoft Corporation | Managing parallel requests in a communications environment supporting serial and parallel request handlers |
JP4819644B2 (en) * | 2006-10-12 | 2011-11-24 | 株式会社日立製作所 | Information processing system, information processing method, and information processing apparatus |
JP4872698B2 (en) * | 2007-02-14 | 2012-02-08 | 日本電気株式会社 | COMMUNICATION SYSTEM, PORTABLE TERMINAL DEVICE, SERVER DEVICE, AND COMMUNICATION METHOD |
KR100888478B1 (en) * | 2007-03-08 | 2009-03-12 | 삼성전자주식회사 | Method of Processing Action, Method of Controlling Controlled Device, Controlled Device and Control Point |
JP4937811B2 (en) * | 2007-03-29 | 2012-05-23 | 京セラ株式会社 | Mobile terminal device |
US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
US20090003387A1 (en) * | 2007-06-27 | 2009-01-01 | Microsoft Corporation | Synchronization Between Connection Manager and Extension Components |
US20090097401A1 (en) * | 2007-10-12 | 2009-04-16 | Wael William Diab | Method and system for configurable data rate thresholds for energy efficient ethernet |
US8364181B2 (en) | 2007-12-10 | 2013-01-29 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
US20090172395A1 (en) * | 2007-12-31 | 2009-07-02 | International Business Machines Corporation | System and Method for Service Virtualization Using a MQ Proxy Network |
US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
US20090193338A1 (en) | 2008-01-28 | 2009-07-30 | Trevor Fiatal | Reducing network and battery consumption during content delivery and playback |
US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
US8078158B2 (en) | 2008-06-26 | 2011-12-13 | Seven Networks, Inc. | Provisioning applications for a mobile device |
US8352868B2 (en) * | 2008-06-27 | 2013-01-08 | Google Inc. | Computing with local and remote resources including user mode control |
US20090328036A1 (en) * | 2008-06-27 | 2009-12-31 | Oqo, Inc. | Selection of virtual computing resources using hardware model presentations |
US20090327495A1 (en) * | 2008-06-27 | 2009-12-31 | Oqo, Inc. | Computing with local and remote resources using automated optimization |
US8818992B2 (en) | 2008-09-12 | 2014-08-26 | Nokia Corporation | Method, system, and apparatus for arranging content search results |
US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
US8380866B2 (en) * | 2009-03-20 | 2013-02-19 | Ricoh Company, Ltd. | Techniques for facilitating annotations |
US8657677B2 (en) * | 2009-04-28 | 2014-02-25 | Ongame Services Ab | Client account managing arrangement on an online gaming system |
US9588803B2 (en) | 2009-05-11 | 2017-03-07 | Microsoft Technology Licensing, Llc | Executing native-code applications in a browser |
US9405710B2 (en) * | 2009-06-30 | 2016-08-02 | Rovi Guides, Inc. | Systems and methods for providing interactive media guidance on a wireless communications device |
US9323921B2 (en) | 2010-07-13 | 2016-04-26 | Microsoft Technology Licensing, Llc | Ultra-low cost sandboxing for application appliances |
US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
EP2599003B1 (en) | 2010-07-26 | 2018-07-11 | Seven Networks, LLC | Mobile network traffic coordination across multiple applications |
WO2012027472A2 (en) | 2010-08-24 | 2012-03-01 | Copiun, Inc. | Constant access gateway and de-duplicated data cache server |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
WO2012060995A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US10303357B2 (en) | 2010-11-19 | 2019-05-28 | TIVO SOLUTIONS lNC. | Flick to send or display content |
CA2798523C (en) | 2010-11-22 | 2015-02-24 | Seven Networks, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
EP3422775A1 (en) | 2010-11-22 | 2019-01-02 | Seven Networks, LLC | Optimization of resource polling intervals to satisfy mobile device requests |
US9325662B2 (en) | 2011-01-07 | 2016-04-26 | Seven Networks, Llc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
US8442494B2 (en) * | 2011-02-18 | 2013-05-14 | Mitel Networks Corporation | System for updating presentations on mobile devices and methods thereof |
GB2505103B (en) | 2011-04-19 | 2014-10-22 | Seven Networks Inc | Social caching for device resource sharing and management cross-reference to related applications |
US8832228B2 (en) | 2011-04-27 | 2014-09-09 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
US8621075B2 (en) | 2011-04-27 | 2013-12-31 | Seven Metworks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
US9495183B2 (en) | 2011-05-16 | 2016-11-15 | Microsoft Technology Licensing, Llc | Instruction set emulation for guest operating systems |
EP2737742A4 (en) | 2011-07-27 | 2015-01-28 | Seven Networks Inc | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
US20130054734A1 (en) * | 2011-08-23 | 2013-02-28 | Microsoft Corporation | Migration of cloud applications between a local computing device and cloud |
US8977755B2 (en) | 2011-12-06 | 2015-03-10 | Seven Networks, Inc. | Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation |
US8918503B2 (en) | 2011-12-06 | 2014-12-23 | Seven Networks, Inc. | Optimization of mobile traffic directed to private networks and operator configurability thereof |
US9277443B2 (en) | 2011-12-07 | 2016-03-01 | Seven Networks, Llc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
US9009250B2 (en) | 2011-12-07 | 2015-04-14 | Seven Networks, Inc. | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
US9413538B2 (en) | 2011-12-12 | 2016-08-09 | Microsoft Technology Licensing, Llc | Cryptographic certification of secure hosted execution environments |
US9389933B2 (en) | 2011-12-12 | 2016-07-12 | Microsoft Technology Licensing, Llc | Facilitating system service request interactions for hardware-protected applications |
US8861354B2 (en) | 2011-12-14 | 2014-10-14 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
US9832095B2 (en) | 2011-12-14 | 2017-11-28 | Seven Networks, Llc | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
US9021021B2 (en) | 2011-12-14 | 2015-04-28 | Seven Networks, Inc. | Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system |
WO2013103988A1 (en) | 2012-01-05 | 2013-07-11 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
US9203864B2 (en) | 2012-02-02 | 2015-12-01 | Seven Networks, Llc | Dynamic categorization of applications for network access in a mobile network |
US9326189B2 (en) | 2012-02-03 | 2016-04-26 | Seven Networks, Llc | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
GB2500373A (en) | 2012-03-13 | 2013-09-25 | Ibm | Object caching for mobile data communication with mobility management |
US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
WO2013155208A1 (en) | 2012-04-10 | 2013-10-17 | Seven Networks, Inc. | Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network |
US8775631B2 (en) | 2012-07-13 | 2014-07-08 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
US20140177497A1 (en) | 2012-12-20 | 2014-06-26 | Seven Networks, Inc. | Management of mobile device radio state promotion and demotion |
US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
US9326185B2 (en) | 2013-03-11 | 2016-04-26 | Seven Networks, Llc | Mobile network congestion recognition for optimization of mobile traffic |
US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
US9736119B2 (en) * | 2014-04-07 | 2017-08-15 | Google Inc. | Relay proxy providing secure connectivity in a controlled network environment |
US10176516B2 (en) * | 2015-05-29 | 2019-01-08 | Amazon Technologies, Inc. | Offline creation of marketplace listings |
US10051075B1 (en) * | 2015-09-09 | 2018-08-14 | Google Llc | Systems and methods for maintaining an asynchronous communication via an intermediary |
US10389842B2 (en) * | 2015-09-18 | 2019-08-20 | International Business Machines Corporation | Mobile device cache updating |
WO2020091181A1 (en) * | 2018-11-01 | 2020-05-07 | 엘지전자 주식회사 | Method and apparatus for transmitting and receiving signal in wireless communication system |
Citations (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5438611A (en) * | 1991-05-20 | 1995-08-01 | Ntp Incorporated | Electronic mail system with RF communications to mobile processors originating from outside of the electronic mail system and method of operation thereof |
US5461667A (en) * | 1991-10-03 | 1995-10-24 | Viscorp | Apparatus and method for electronic device for information services |
US5487100A (en) * | 1992-09-30 | 1996-01-23 | Motorola, Inc. | Electronic mail message delivery system |
US5579472A (en) * | 1994-11-09 | 1996-11-26 | Novalink Technologies, Inc. | Group-oriented communications user interface |
US5790800A (en) * | 1995-10-13 | 1998-08-04 | Digital Equipment Corporation | Client application program mobilizer |
US5809415A (en) * | 1995-12-11 | 1998-09-15 | Unwired Planet, Inc. | Method and architecture for an interactive two-way data communication network |
US5822692A (en) * | 1993-12-29 | 1998-10-13 | Flat Connections, Inc. | Data communication device |
US5850517A (en) * | 1995-08-31 | 1998-12-15 | Oracle Corporation | Communication link for client-server having agent which sends plurality of requests independent of client and receives information from the server independent of the server |
US5903652A (en) * | 1996-11-25 | 1999-05-11 | Microsoft Corporation | System and apparatus for monitoring secure information in a computer network |
US5933478A (en) * | 1994-09-28 | 1999-08-03 | Hitachi, Ltd. | Data transfer system and handheld terminal device used therefor |
US5987609A (en) * | 1996-10-03 | 1999-11-16 | Kabushiki Kaisha Toshiba | System for remotely securing/locking a stolen wireless device via an Email message |
US6006087A (en) * | 1997-04-10 | 1999-12-21 | At&T Wireless Services, Inc. | Method and system for delivering a voice mail notification to a subscriber using cellular phone network |
US6014559A (en) * | 1997-04-10 | 2000-01-11 | At&T Wireless Services, Inc. | Method and system for delivering a voice mail notification to a private base station using cellular phone network |
US6052735A (en) * | 1997-10-24 | 2000-04-18 | Microsoft Corporation | Electronic mail object synchronization between a desktop computer and mobile device |
US6055426A (en) * | 1997-06-17 | 2000-04-25 | Highwaymaster Communications, Inc. | Notification of a mobile unit out of coverage |
US6065120A (en) * | 1997-12-09 | 2000-05-16 | Phone.Com, Inc. | Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices |
US6094681A (en) * | 1998-03-31 | 2000-07-25 | Siemens Information And Communication Networks, Inc. | Apparatus and method for automated event notification |
US6101244A (en) * | 1997-06-25 | 2000-08-08 | Murata Kikai Kabushiki Kaisha | Electronic mail-capable communication terminal device and electronic mail communication method |
US6108688A (en) * | 1996-06-12 | 2000-08-22 | Sun Microsystems, Inc. | System for reminding a sender of an email if recipient of the email does not respond by a selected time set by the sender |
US6119167A (en) * | 1997-07-11 | 2000-09-12 | Phone.Com, Inc. | Pushing and pulling data in networks |
US6181736B1 (en) * | 1997-03-25 | 2001-01-30 | Nxi Communications, Inc. | Network communication system |
US6185208B1 (en) * | 1998-04-30 | 2001-02-06 | Phone.Com, Inc. | Method and apparatus for fragmenting messages for a wireless network using group sharing of reference numbers |
US6289212B1 (en) * | 1998-09-16 | 2001-09-11 | Openwave Systems Inc. | Method and apparatus for providing electronic mail services during network unavailability |
US6314108B1 (en) * | 1998-04-30 | 2001-11-06 | Openwave Systems Inc. | Method and apparatus for providing network access over different wireless networks |
US6317831B1 (en) * | 1998-09-21 | 2001-11-13 | Openwave Systems Inc. | Method and apparatus for establishing a secure connection over a one-way data path |
US6424841B1 (en) * | 1999-02-18 | 2002-07-23 | Openwave Systems Inc. | Short message service with improved utilization of available bandwidth |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE1867295U (en) | 1962-11-24 | 1963-02-14 | Bremshey & Co | VEHICLE SEAT. |
WO1998010580A1 (en) | 1996-09-03 | 1998-03-12 | Toyota Jidosha Kabushiki Kaisha | Information communication controller and system for the same |
US6233318B1 (en) | 1996-11-05 | 2001-05-15 | Comverse Network Systems, Inc. | System for accessing multimedia mailboxes and messages over the internet and via telephone |
-
1998
- 1998-10-13 US US09/170,879 patent/US6721288B1/en not_active Expired - Lifetime
-
1999
- 1999-09-14 JP JP11261090A patent/JP2000148572A/en active Pending
- 1999-09-16 EP EP99307367A patent/EP0993165A3/en not_active Withdrawn
- 1999-09-16 KR KR1019990039948A patent/KR20000023230A/en not_active Application Discontinuation
-
2004
- 2004-02-27 US US10/789,687 patent/US20040203670A1/en not_active Abandoned
Patent Citations (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5438611A (en) * | 1991-05-20 | 1995-08-01 | Ntp Incorporated | Electronic mail system with RF communications to mobile processors originating from outside of the electronic mail system and method of operation thereof |
US5461667A (en) * | 1991-10-03 | 1995-10-24 | Viscorp | Apparatus and method for electronic device for information services |
US5487100A (en) * | 1992-09-30 | 1996-01-23 | Motorola, Inc. | Electronic mail message delivery system |
US5822692A (en) * | 1993-12-29 | 1998-10-13 | Flat Connections, Inc. | Data communication device |
US5933478A (en) * | 1994-09-28 | 1999-08-03 | Hitachi, Ltd. | Data transfer system and handheld terminal device used therefor |
US5579472A (en) * | 1994-11-09 | 1996-11-26 | Novalink Technologies, Inc. | Group-oriented communications user interface |
US5850517A (en) * | 1995-08-31 | 1998-12-15 | Oracle Corporation | Communication link for client-server having agent which sends plurality of requests independent of client and receives information from the server independent of the server |
US5790800A (en) * | 1995-10-13 | 1998-08-04 | Digital Equipment Corporation | Client application program mobilizer |
US5809415A (en) * | 1995-12-11 | 1998-09-15 | Unwired Planet, Inc. | Method and architecture for an interactive two-way data communication network |
US6108688A (en) * | 1996-06-12 | 2000-08-22 | Sun Microsystems, Inc. | System for reminding a sender of an email if recipient of the email does not respond by a selected time set by the sender |
US5987609A (en) * | 1996-10-03 | 1999-11-16 | Kabushiki Kaisha Toshiba | System for remotely securing/locking a stolen wireless device via an Email message |
US5903652A (en) * | 1996-11-25 | 1999-05-11 | Microsoft Corporation | System and apparatus for monitoring secure information in a computer network |
US6181736B1 (en) * | 1997-03-25 | 2001-01-30 | Nxi Communications, Inc. | Network communication system |
US6006087A (en) * | 1997-04-10 | 1999-12-21 | At&T Wireless Services, Inc. | Method and system for delivering a voice mail notification to a subscriber using cellular phone network |
US6014559A (en) * | 1997-04-10 | 2000-01-11 | At&T Wireless Services, Inc. | Method and system for delivering a voice mail notification to a private base station using cellular phone network |
US6055426A (en) * | 1997-06-17 | 2000-04-25 | Highwaymaster Communications, Inc. | Notification of a mobile unit out of coverage |
US6101244A (en) * | 1997-06-25 | 2000-08-08 | Murata Kikai Kabushiki Kaisha | Electronic mail-capable communication terminal device and electronic mail communication method |
US6119167A (en) * | 1997-07-11 | 2000-09-12 | Phone.Com, Inc. | Pushing and pulling data in networks |
US6052735A (en) * | 1997-10-24 | 2000-04-18 | Microsoft Corporation | Electronic mail object synchronization between a desktop computer and mobile device |
US6065120A (en) * | 1997-12-09 | 2000-05-16 | Phone.Com, Inc. | Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices |
US6094681A (en) * | 1998-03-31 | 2000-07-25 | Siemens Information And Communication Networks, Inc. | Apparatus and method for automated event notification |
US6185208B1 (en) * | 1998-04-30 | 2001-02-06 | Phone.Com, Inc. | Method and apparatus for fragmenting messages for a wireless network using group sharing of reference numbers |
US6314108B1 (en) * | 1998-04-30 | 2001-11-06 | Openwave Systems Inc. | Method and apparatus for providing network access over different wireless networks |
US6289212B1 (en) * | 1998-09-16 | 2001-09-11 | Openwave Systems Inc. | Method and apparatus for providing electronic mail services during network unavailability |
US6317831B1 (en) * | 1998-09-21 | 2001-11-13 | Openwave Systems Inc. | Method and apparatus for establishing a secure connection over a one-way data path |
US6424841B1 (en) * | 1999-02-18 | 2002-07-23 | Openwave Systems Inc. | Short message service with improved utilization of available bandwidth |
Cited By (123)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7292844B2 (en) * | 1998-11-17 | 2007-11-06 | Geobrowser Innovations, Lp | Geographical web browser, methods, apparatus and systems |
US8369263B2 (en) | 1998-11-17 | 2013-02-05 | E.O. Communication Fund, Llc | Geographical web browser, methods, apparatus and systems |
US8190170B2 (en) | 1998-11-17 | 2012-05-29 | E.O. Communication Fund, Llc | Geographical web browser, methods, apparatus and systems |
US20010017855A1 (en) * | 2000-02-29 | 2001-08-30 | Matsushita Electric Industrial Co., Ltd. | Portable telephone with URL accessing function |
US20010056444A1 (en) * | 2000-04-07 | 2001-12-27 | Motoki Ide | Communication terminal device |
US7756525B1 (en) * | 2002-09-16 | 2010-07-13 | Teradata Us, Inc. | Continuous dynamic mobile querying |
US20050015500A1 (en) * | 2003-07-16 | 2005-01-20 | Batchu Suresh K. | Method and system for response buffering in a portal server for client devices |
US11467883B2 (en) | 2004-03-13 | 2022-10-11 | Iii Holdings 12, Llc | Co-allocating a reservation spanning different compute resources types |
US11960937B2 (en) | 2004-03-13 | 2024-04-16 | Iii Holdings 12, Llc | System and method for an optimizing reservation in time of compute resources based on prioritization function and reservation policy parameter |
US11652706B2 (en) | 2004-06-18 | 2023-05-16 | Iii Holdings 12, Llc | System and method for providing dynamic provisioning within a compute environment |
US11630704B2 (en) | 2004-08-20 | 2023-04-18 | Iii Holdings 12, Llc | System and method for a workload management and scheduling module to manage access to a compute environment according to local and non-local user identity information |
US11709709B2 (en) | 2004-11-08 | 2023-07-25 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11537434B2 (en) | 2004-11-08 | 2022-12-27 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11656907B2 (en) | 2004-11-08 | 2023-05-23 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11494235B2 (en) | 2004-11-08 | 2022-11-08 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11762694B2 (en) | 2004-11-08 | 2023-09-19 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11886915B2 (en) | 2004-11-08 | 2024-01-30 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11537435B2 (en) | 2004-11-08 | 2022-12-27 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US11861404B2 (en) | 2004-11-08 | 2024-01-02 | Iii Holdings 12, Llc | System and method of providing system jobs within a compute environment |
US10333862B2 (en) | 2005-03-16 | 2019-06-25 | Iii Holdings 12, Llc | Reserving resources in an on-demand compute environment |
US11134022B2 (en) | 2005-03-16 | 2021-09-28 | Iii Holdings 12, Llc | Simple integration of an on-demand compute environment |
US9015324B2 (en) | 2005-03-16 | 2015-04-21 | Adaptive Computing Enterprises, Inc. | System and method of brokering cloud computing resources |
US11658916B2 (en) | 2005-03-16 | 2023-05-23 | Iii Holdings 12, Llc | Simple integration of an on-demand compute environment |
US10608949B2 (en) | 2005-03-16 | 2020-03-31 | Iii Holdings 12, Llc | Simple integration of an on-demand compute environment |
US9231886B2 (en) | 2005-03-16 | 2016-01-05 | Adaptive Computing Enterprises, Inc. | Simple integration of an on-demand compute environment |
US11356385B2 (en) | 2005-03-16 | 2022-06-07 | Iii Holdings 12, Llc | On-demand compute environment |
US11765101B2 (en) | 2005-04-07 | 2023-09-19 | Iii Holdings 12, Llc | On-demand access to compute resources |
US10986037B2 (en) | 2005-04-07 | 2021-04-20 | Iii Holdings 12, Llc | On-demand access to compute resources |
US11496415B2 (en) | 2005-04-07 | 2022-11-08 | Iii Holdings 12, Llc | On-demand access to compute resources |
US11522811B2 (en) | 2005-04-07 | 2022-12-06 | Iii Holdings 12, Llc | On-demand access to compute resources |
US11533274B2 (en) | 2005-04-07 | 2022-12-20 | Iii Holdings 12, Llc | On-demand access to compute resources |
US11831564B2 (en) | 2005-04-07 | 2023-11-28 | Iii Holdings 12, Llc | On-demand access to compute resources |
US10277531B2 (en) | 2005-04-07 | 2019-04-30 | Iii Holdings 2, Llc | On-demand access to compute resources |
US20060230149A1 (en) * | 2005-04-07 | 2006-10-12 | Cluster Resources, Inc. | On-Demand Access to Compute Resources |
US9075657B2 (en) * | 2005-04-07 | 2015-07-07 | Adaptive Computing Enterprises, Inc. | On-demand access to compute resources |
US20060235872A1 (en) * | 2005-04-19 | 2006-10-19 | Research In Motion Limited | Integration of push services with applications |
US9031907B2 (en) * | 2005-04-19 | 2015-05-12 | Blackberry Limited | Integration of push services with applications |
US8195763B2 (en) | 2005-07-22 | 2012-06-05 | Research In Motion Limited | Secure method of synchronizing cache contents of a mobile browser with a server |
US20070180125A1 (en) * | 2005-07-22 | 2007-08-02 | Michael Knowles | Secure method of synchronizing cache contents of a mobile browser with a server |
US20070198634A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | Method for training a server for content delivery based on communication of state information from a mobile device browser |
US20070198715A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | System and method for communicating state management between a browser user-agent and a server |
US20070198716A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | Method of controlling delivery of multi-part content from an origin server to a mobile device browser via a server |
US20070198734A1 (en) * | 2005-07-22 | 2007-08-23 | Michael Knowles | Method for communicating state information between a server and a mobile device browser with version handling |
US8005891B2 (en) | 2005-07-22 | 2011-08-23 | Research In Motion Limited | Method for training a server for content delivery based on communication of state information from a mobile device browser |
US20100269154A1 (en) * | 2005-07-22 | 2010-10-21 | Research In Motion Limited | Method of communciating state information between a server and a mobile device browser with version handling |
US8543697B2 (en) * | 2005-07-22 | 2013-09-24 | Research In Motion Limited | System and method for communicating state management between a browser user-agent and a server |
US11650857B2 (en) | 2006-03-16 | 2023-05-16 | Iii Holdings 12, Llc | System and method for managing a hybrid computer environment |
US20070255910A1 (en) * | 2006-04-28 | 2007-11-01 | Research In Motion Limited | Method of reflecting on another device an addition to a browser cache on a handheld electronic device, and associated device |
US7644149B2 (en) * | 2006-04-28 | 2010-01-05 | Research In Motion Limited | Method of reflecting on another device an addition to a browser cache on a handheld electronic device, and associated device |
US20080045248A1 (en) * | 2006-08-18 | 2008-02-21 | Tim Neil | Associating a label with a queued message at a mobile device |
US7899474B2 (en) * | 2006-08-18 | 2011-03-01 | Research In Motion Limited | Associating a label with a queued message at a mobile device |
US20080098486A1 (en) * | 2006-10-20 | 2008-04-24 | Verizon Business Financial Management Corporation | Integrated data access |
US8819806B2 (en) * | 2006-10-20 | 2014-08-26 | Verizon Patent And Licensing Inc. | Integrated data access |
US8055247B1 (en) * | 2006-12-21 | 2011-11-08 | Sprint Communications Company L.P. | Mobile audible data services |
US20080299999A1 (en) * | 2007-06-01 | 2008-12-04 | Kendall Gregory Lockhart | System and method for generating multimedia messages in a mobile device |
US20080299960A1 (en) * | 2007-06-01 | 2008-12-04 | Kendall Gregory Lockhart | System and method for managing message transmissions on a mobile device |
US20090049405A1 (en) * | 2007-06-01 | 2009-02-19 | Kendall Gregory Lockhart | System and method for implementing session-based navigation |
US9608947B2 (en) | 2007-06-28 | 2017-03-28 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US11700219B2 (en) | 2007-06-28 | 2023-07-11 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US9456087B2 (en) | 2007-06-28 | 2016-09-27 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8670531B2 (en) | 2007-06-28 | 2014-03-11 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US9621491B2 (en) | 2007-06-28 | 2017-04-11 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US9634969B2 (en) | 2007-06-28 | 2017-04-25 | Voxer Ip Llc | Real-time messaging method and apparatus |
US9674122B2 (en) | 2007-06-28 | 2017-06-06 | Vover IP LLC | Telecommunication and multimedia management method and apparatus |
US9742712B2 (en) | 2007-06-28 | 2017-08-22 | Voxer Ip Llc | Real-time messaging method and apparatus |
US9800528B2 (en) | 2007-06-28 | 2017-10-24 | Voxer Ip Llc | Real-time messaging method and apparatus |
US11943186B2 (en) | 2007-06-28 | 2024-03-26 | Voxer Ip Llc | Real-time messaging method and apparatus |
US10129191B2 (en) | 2007-06-28 | 2018-11-13 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US10142270B2 (en) | 2007-06-28 | 2018-11-27 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US10158591B2 (en) | 2007-06-28 | 2018-12-18 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8687779B2 (en) | 2007-06-28 | 2014-04-01 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US10326721B2 (en) | 2007-06-28 | 2019-06-18 | Voxer Ip Llc | Real-time messaging method and apparatus |
US20120288074A1 (en) * | 2007-06-28 | 2012-11-15 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US10356023B2 (en) | 2007-06-28 | 2019-07-16 | Voxer Ip Llc | Real-time messaging method and apparatus |
US10375139B2 (en) | 2007-06-28 | 2019-08-06 | Voxer Ip Llc | Method for downloading and using a communication application through a web browser |
US10511557B2 (en) | 2007-06-28 | 2019-12-17 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8693647B2 (en) | 2007-06-28 | 2014-04-08 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US10841261B2 (en) | 2007-06-28 | 2020-11-17 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8705714B2 (en) * | 2007-06-28 | 2014-04-22 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US11777883B2 (en) | 2007-06-28 | 2023-10-03 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8902749B2 (en) | 2007-06-28 | 2014-12-02 | Voxer Ip Llc | Multi-media messaging method, apparatus and application for conducting real-time and time-shifted communications |
US11095583B2 (en) | 2007-06-28 | 2021-08-17 | Voxer Ip Llc | Real-time messaging method and apparatus |
US8948354B2 (en) | 2007-06-28 | 2015-02-03 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US11146516B2 (en) | 2007-06-28 | 2021-10-12 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US11658927B2 (en) | 2007-06-28 | 2023-05-23 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8565149B2 (en) | 2007-06-28 | 2013-10-22 | Voxer Ip Llc | Multi-media messaging method, apparatus and applications for conducting real-time and time-shifted communications |
US11658929B2 (en) | 2007-06-28 | 2023-05-23 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8526456B2 (en) | 2007-06-28 | 2013-09-03 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US8532270B2 (en) | 2007-06-28 | 2013-09-10 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US20090003340A1 (en) * | 2007-06-28 | 2009-01-01 | Rebelvox, Llc | Telecommunication and multimedia management method and apparatus |
US20230051915A1 (en) | 2007-06-28 | 2023-02-16 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US9154628B2 (en) | 2007-06-28 | 2015-10-06 | Voxer Ip Llc | Telecommunication and multimedia management method and apparatus |
US11522952B2 (en) | 2007-09-24 | 2022-12-06 | The Research Foundation For The State University Of New York | Automatic clustering for self-organizing grids |
EP2073486A1 (en) | 2007-12-17 | 2009-06-24 | Alcatel Lucent | Method for providing multimedia service to a mobile device in case of foreseen network unavailability |
US11182079B2 (en) | 2008-02-28 | 2021-11-23 | Memory Technologies Llc | Extended utilization area for a memory device |
US11907538B2 (en) | 2008-02-28 | 2024-02-20 | Memory Technologies Llc | Extended utilization area for a memory device |
US11550476B2 (en) | 2008-02-28 | 2023-01-10 | Memory Technologies Llc | Extended utilization area for a memory device |
US11494080B2 (en) | 2008-02-28 | 2022-11-08 | Memory Technologies Llc | Extended utilization area for a memory device |
US9367486B2 (en) | 2008-02-28 | 2016-06-14 | Memory Technologies Llc | Extended utilization area for a memory device |
US11829601B2 (en) | 2008-02-28 | 2023-11-28 | Memory Technologies Llc | Extended utilization area for a memory device |
US9063850B2 (en) | 2008-02-28 | 2015-06-23 | Memory Technologies Llc | Extended utilization area for a memory device |
US20090306999A1 (en) * | 2008-06-06 | 2009-12-10 | Microsoft Corporation | Conversational parallelism for message processing |
US8370851B2 (en) * | 2008-06-06 | 2013-02-05 | Microsoft Corporation | Conversational parallelism for message processing |
US20100179980A1 (en) * | 2009-01-14 | 2010-07-15 | Movidilo S.L. | Cache system for mobile communications devices |
US11775173B2 (en) | 2009-06-04 | 2023-10-03 | Memory Technologies Llc | Apparatus and method to share host system RAM with mass storage memory RAM |
US11733869B2 (en) | 2009-06-04 | 2023-08-22 | Memory Technologies Llc | Apparatus and method to share host system RAM with mass storage memory RAM |
US9983800B2 (en) | 2009-06-04 | 2018-05-29 | Memory Technologies Llc | Apparatus and method to share host system RAM with mass storage memory RAM |
US9208078B2 (en) | 2009-06-04 | 2015-12-08 | Memory Technologies Llc | Apparatus and method to share host system RAM with mass storage memory RAM |
US10983697B2 (en) | 2009-06-04 | 2021-04-20 | Memory Technologies Llc | Apparatus and method to share host system RAM with mass storage memory RAM |
US20110081895A1 (en) * | 2009-10-06 | 2011-04-07 | Fujifilm Corporation | Information browsing system |
US20110093567A1 (en) * | 2009-10-15 | 2011-04-21 | Electronics And Telecommunications Research Institute | Mobile terminal for providing mobile cloud service and operation method thereof |
US11720290B2 (en) | 2009-10-30 | 2023-08-08 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US11526304B2 (en) | 2009-10-30 | 2022-12-13 | Iii Holdings 2, Llc | Memcached server functionality in a cluster of data processing nodes |
US9247523B1 (en) | 2012-01-17 | 2016-01-26 | Cox Communications, Inc. | System, method and device for initiating actions for mobile devices prior to a mobile user entering problem zones |
US10877665B2 (en) | 2012-01-26 | 2020-12-29 | Memory Technologies Llc | Apparatus and method to provide cache move with non-volatile mass memory system |
US9417998B2 (en) | 2012-01-26 | 2016-08-16 | Memory Technologies Llc | Apparatus and method to provide cache move with non-volatile mass memory system |
US11797180B2 (en) | 2012-01-26 | 2023-10-24 | Memory Technologies Llc | Apparatus and method to provide cache move with non-volatile mass memory system |
US11226771B2 (en) | 2012-04-20 | 2022-01-18 | Memory Technologies Llc | Managing operational state data in memory module |
US11782647B2 (en) | 2012-04-20 | 2023-10-10 | Memory Technologies Llc | Managing operational state data in memory module |
US9164804B2 (en) | 2012-06-20 | 2015-10-20 | Memory Technologies Llc | Virtual memory module |
US9116820B2 (en) | 2012-08-28 | 2015-08-25 | Memory Technologies Llc | Dynamic central cache memory |
WO2014036078A3 (en) * | 2012-08-28 | 2014-05-01 | Memory Technologies Llc | Dynamic central cache memory |
WO2014036078A2 (en) * | 2012-08-28 | 2014-03-06 | Memory Technologies Llc | Dynamic central cache memory |
Also Published As
Publication number | Publication date |
---|---|
JP2000148572A (en) | 2000-05-30 |
US6721288B1 (en) | 2004-04-13 |
EP0993165A3 (en) | 2001-09-12 |
KR20000023230A (en) | 2000-04-25 |
EP0993165A2 (en) | 2000-04-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6721288B1 (en) | Wireless mobile devices having improved operation during network unavailability | |
US6289212B1 (en) | Method and apparatus for providing electronic mail services during network unavailability | |
EP1071029A2 (en) | Method and system for providing electronic mail services to mobile devices with efficient use of network bandwidth | |
CN100531186C (en) | Object transfer control in communications network | |
US7653734B1 (en) | Method for implementing a multimedia messaging service, a multimedia messaging system, a server of a multimedia messaging system and a multimedia terminal | |
US6311210B1 (en) | Method and apparatus for sending an electronic mail message to a receiving party | |
CN100559795C (en) | Method for synchronous | |
KR100612709B1 (en) | Short message gateway, system and method of providing information service for mobile devices | |
WO2000010306A1 (en) | Method and apparatus for controlling network connections based on destination locations | |
PT1240754E (en) | Multimedia messaging service | |
EP1553498B1 (en) | Electronic mail delivery system, mail server, and mail client | |
US7277915B2 (en) | Application-based protocol and proxy selection by a mobile device in a multi-protocol network environment | |
JP2000163367A (en) | Method and architecture (system) for interactive bidirectional communication device to interact with network | |
US7570942B2 (en) | Transactional message-queue communication for wirelessly networked devices system and method | |
JP4607578B2 (en) | Communication system, compatible mobile device, and method for storing pages in mobile device | |
JP2002543496A (en) | Wireless terminal device with browser | |
JPWO2005083575A1 (en) | Data communication method, data communication system, and communication terminal device | |
US6842839B2 (en) | Capacity management | |
ES2364236T3 (en) | RADIO TERMINAL FOR NAVIGATING INTERNET. | |
EP1512086A2 (en) | Methods and system for using caches | |
US20030134628A1 (en) | On a mobile device | |
JP3869135B2 (en) | Information service system using digital wireless telephone | |
EP1669914B1 (en) | Methods and apparatus for managing the storage of e-mail message information in a mobile station | |
US20040267962A1 (en) | Method and system in wireless data communication network for transferring content to terminal equipment and corresponding terminal equipment, server and browser devices | |
JP2002366581A (en) | Bookmark management system and portable communication terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |