|Publication number||US20020103005 A1|
|Application number||US 09/770,162|
|Publication date||Aug 1, 2002|
|Filing date||Jan 26, 2001|
|Priority date||Jan 26, 2001|
|Also published as||US8170610, US8331985, US20100191891, US20120254106|
|Publication number||09770162, 770162, US 2002/0103005 A1, US 2002/103005 A1, US 20020103005 A1, US 20020103005A1, US 2002103005 A1, US 2002103005A1, US-A1-20020103005, US-A1-2002103005, US2002/0103005A1, US2002/103005A1, US20020103005 A1, US20020103005A1, US2002103005 A1, US2002103005A1|
|Inventors||La Vaughn Watts, Nobuyuki Sato, Gary Huber|
|Original Assignee||Watts La Vaughn F., Sato Nobuyuki Albert, Huber Gary Douglas|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Referenced by (28), Classifications (7), Legal Events (1)|
|External Links: USPTO, USPTO Assignment, Espacenet|
 This application is related to commonly assigned patent application Ser. No. 09/740,138, filed Dec. 18, 2000 and entitled “A COMBINATION PERSONAL DATA ASSISTANT AND PERSONAL COMPUTING DEVICE” having La Vaughn F. Watts, Jr. and Ronald D. Shaw as inventors.
 1. Field of the Invention
 This invention relates generally to a computing system and more particularly to a mobile computing system integrating dissimilar computing architectures and receiving messages and files, with the messages and files arranged to conserve memory space with minimal user intervention.
 2. Description of the Related Art
 There are currently two popular types of mobile computing systems. The mobile Personal Computer (PC) system is a fully functional data processing system, typically having the same functionality as a desktop PC or a workstation PC. The mobile PC system (PC system) can run under any number of standard operating systems (OS), such as one of the releases of Windows® by the Microsoft Corporation. In implementing the PC system in a mobile computing architecture, several relatively undesirable features are apparent. First, the batteries of the PC system must be recharged after a relatively short time, typically in the order of a few hours. Despite improvements in battery technology, the quest for lighter and more compact portable units have tended to reduce the space allocated to the batteries so that time between charging of the batteries has not been significantly improved. The batteries used in the PC system, however, are capable of relatively rapid charging. As with the desktop PC unit and the workstation PC from which they are derived, the OS needed for the PC system requires a relatively long time from the activation of the power switch to the time when the processing system is available for actual computation. The PC system, however, has remarkable flexibility and can provide processing capability of extraordinary power. PC systems also have great memory capacity, having disk drives that can store significant amounts of information.
 More recently the personal digital assistant (PDA) system has been developed to take advantage of operating systems (OS) such as Palm® OS and Windows®. These operating systems, in conjunction with a PDA system, permit a reduced or specialized functionality computing system.
 PDA systems are relatively small in physical size and can perform a variety of useful functions such as arrange calendars; schedule appointments; send and receive e-mail; provide presentations; create documents; and provide communications. The PDA OS can permit exchange of files between the PDA systems and a PC system with Microsoft Windows® files. While the reduced functionality can be a disadvantage of the PDA system, the PDA vsystem has several advantages. An advantage is the time between charging of the batteries can be greatly extended, a result of the reduced functionality and the absence of disk storage units. The PDA system has its memory loaded in a memory circuit, such as a flash memory, which allows the PDA system to become active much quicker than a PC system. This memory, however, has limited capacity and can quickly be filled up.
 Current PC systems and PDA systems have the capability to communicate and receive messages such as email, particular through wireless communication technologies. The PC systems with their large memory capacity can receive and store a great number of messages before memory space is exhausted. PC systems, however, with their draining power requirement cannot continuously be left on while in battery mode. Therefore a PC system is limited in the number of messages it receives because it cannot continually be left on. A PDA system with its low battery consumption has the capability to remain on for a very long time. A PDA system, however, with its limited memory capacity can quickly run out of memory. Without operator intervention, a PDA system with its memory capacity fully filled, is not able to receive incoming messages. Therefore current PC systems and PDA systems are limited in their abilities to receive incoming messages such as email.
 A need has been felt for a mobile computing architecture having the desirable features of both the PC systems and of the PDA systems. In particular, the computing architecture would have the feature of an expanded time between battery charges. Another feature of the computing architecture would be the ability to continually receive incoming messages such as email and store messages until a user reads the messages. Yet another feature would be provide for a computing architecture that archives messages and allows incoming messages to be continually received with minimal user intervention.
 The aforementioned and other features are accomplished, according to the present invention, by providing a mobile computing architecture that includes a PC system and a pDA system which independently have access to a communication device, allowing either system to communicate and receive messages regardless of the active state of the other System.
 Messages are synchronized between the PDA system and the PC system so either system is able to read messages that have been received by the other system. The PC system with its large memory capacity is able to archive and store messages, therefore the PDA is Able to free up memory space by deleting records whenever its memory is filled and new messages are unable to be stored.
 To conserve battery power, the PC system is deactivated or placed in a suspend state while the PDA system continues to receive messages. As the memory of the PDA system is filled with new non-synchronized messages, synchronized messages in the PDA memory are automatically deleted. When the PDA memory array is filled with new non-synchronized messages the PC system can be activated to synchronize messages, archive messages, and clear messages in order to free up space for incoming messages. The user may also be informed to read new messages and take action to free up space.
 The present invention may be better understood, and it's numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the figures designates a like or similar element.
FIG. 1 illustrates a block diagram of a personal computer (PC) system.
FIG. 2 illustrates a block diagram of a personal digital assistant (PDA) system.
FIG. 3 illustrates a combined PC and PDA computing architecture.
FIG. 4 illustrates a combined PC and PDA computing architecture that provides communication access to either the PC system or the PDA system.
FIG. 5A illustrates a memory array for a PDA system synchronized to a memory array for a PC system.
FIG. 5B illustrates filled memory arrays for the PC system and the PDA system.
FIG. 5C illustrates cleared and empty records of memory arrays for the PC system and the PDA system.
FIG. 5D illustrates a PDA memory array and a PC memory with synchronized and non-synchronized records.
FIG. 5E illustrates a PDA memory array 500 with free space and an empty PC memory array 530.
 While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail, it should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.
 Now referring to FIG. 1 illustrated is a block diagram of a PC system. The PC system of FIG. 1 is typical of systems based on the Intel Pentium® and equivalent type processors. A PC CPU 100 is connected by a bus 115 to a north bridge controller 105. Bus 115 typically is a peripheral component interconnect (PCI) bus. The north bridge controller 105 interfaces to a system memory 125. Between the system memory 125 and the north bridge controller 105 is a cache memory 135. The cache memory 135 is used as “temporary” memory, particularly in displaying information to a user. From the north bridge controller 105 is a south bridge controller 110 used to interface to peripheral or input output (10) devices. A bus 120 connects the north bridge controller 105 to the south bridge controller 110. The bus 120 is also typically a PCI bus. From the south bridge controller a bus 130 connects peripheral or 10 devices. Bus 130 can be a PCI bus.
 Now referring to FIG. 2 illustrated is a block diagram of a PDA system. In a PDA system a PDA CPU 200 interfaces to a companion processor 205. The companion processor 205 handles interfacing to peripherals and to a system memory 210. From the companion processor 205 is a bus 215. Bus 215 can be a low pin count (LPC) bus and communicate to peripherals and 10 devices.
 Now referring to FIG. 3 illustrated is a combined PC and PDA computing architecture. A PC system 300 is connected to a switch 310 by a bus 345. The bus 345 can be an LPC bus. The switch 310 is connected to a PDA system 305 by a bus 350. The bus 350 can also be an LPC bus. Either the PC system 300 or the PDA system 305 can have control over the common peripherals and 10 devices, including a display 320. The switch 310 isolates either the PC system 300 or the PDA system 305, placing one of the systems in control of the entire computer system. Input and output control is conducted through a serial or super input output controller (SIO) 325. The SIO 325 is connected to the PDA system 305 by the bus 350 and another bus 355. Bus 350 allows the PC system 300 to interface to the SIO 325 and the PDA system 305, with the PC system 300 acting as a “master” device and the PDA system 305 as a “slave.” When the PDA system 305 is in control of the computing architecture, the PDA system 305 communicates to the S10 325 by a bus 355. The bus 355 can be an LPC bus. The S10 325 provides video control to the display 320 by bus 335 when either the PC system 300 or the PDA system 305 is in control. When in control, the PDA system 305 provides video content by way of bus 340. When the PC system 300 is in control of the computing architecture video content is provided by way of bus 330. Other embodiments of the architecture can include providing a separate and independent connection by way of busses to other common devices from the PC system 300 and the PDA system 305. Common devices can include wireless communication technologies.
 Now referring to FIG. 4, illustrated is a combined PC and PDA computing architecture that provides communication access to either the PC system or the PDA system. In a PC system the south bridge controller can directly connect to a communication device 400 by the PCI bus 130. In a PDA system the companion processor 205 can be connected to the communication device 400 by the LPC bus 215. This computing architecture allows either the PC system or the PDA system to have access to communication, in particular wireless technology. Access by either the PC system or the PDA system is possible, regardless of the active status of either system. Therefore if the PDA system is off, the PC system is able to receive messages such as email. If the PC system is off, the PDA system is able to receive messages.
 Referring back to FIG. 3, the PC system 300 and the PDA system 305 are connected by the bus 345 and the bus 350, and are able to exchange data between their respective memory. Further the connection allows both systems to synchronize messages that are received and eventually archived in the memory of the PC system 300 or the PDA system 305. Considering the limited memory capacity of the PDA system 305, archiving messages would best be undertaken by the PC system 300 with its significantly larger memory.
 Now referring to FIG. 5A illustrated is a memory array for a PDA system synchronized to a memory array for a PC system. A PDA memory array 500 has several records for messages such as email or information. A PC memory array 530 has corresponding records to store or refer to messages or information. The records of the memory arrays may be read or unread by a user. The PC memory array 530 may be a separate logical or physical device to the PC system hard drive (permanent storage unit). Therefore in certain embodiments, the PDA memory array 500 is synchronized directly to the PC system hard drive.
 The PC system with its large capacity storage has the ability to clear records in its memory array 530 and place messages in its hard drive. Since the PDA memory array 500 and PC memory array 530 are synchronized whenever the PC memory array 530 retrieves messages from the hard drive, the PDA memory array 500 is able to read the messages. In this particular example, “Record 1” 512 of PDA memory array 500 is synchronized to “Record 1” 532 of PC memory array 530. Going down each memory array, “Record 2” 514 is synchronized to “Record 2” 534; “Record N” 516 is synchronized to “Record N” 536; and “Record N+1” 518 is synchronized to “Record N+1” 538. A direct one to one correspondence of each record of the respective memory arrays of the PDA and PC system is made available. In this particular example “Record N+1” 518 of PDA memory array 500 is empty and available to receive a new message, therefore “Record N+1” 538 the corresponding record of PC memory array 530 is also empty. “Record N+P” 520 and “Record N+P” 540 are also empty. In this particular embodiment the records that are empty are not synchronized until a message is received or placed in the corresponding record of the other system's memory array. In this embodiment, the memory array of the respective systems are filled from the first record to the last, in this case the last record is “Record N+P” 520 of PDA memory array 500 and “Record N+P” 540 of PC memory array 530.
 Now referring to FIG. 5B illustrated are filled memory arrays for the PC system and the PDA system. As messages are received by either system the memory arrays fill up until the end of memory (EOM) of each array is reached. In the case of the PDA memory array 500 the EOM 522 is after “Record N+P” 520, and for the PC memory array 530, the EOM 630 is after “Record N+P” 542.
 In order to receive new messages such as email, the record arrays must be cleared. Now referring to FIG. 5C illustrated are cleared and empty records of memory arrays for the PC system and the PDA system. In certain applications, the first records such as “Record 1” 512, “Record 1” 532, “Record 2” 514, and “Record 2” 534 are cleared and emptied to provide for incoming messages. The records are deleted after the old messages that occupied the records are placed in the hard drive of the PC system. With the empty records, new messages may be received by either system then the filled records are synchronized with corresponding records of the memory array of the other system.
 When the PC system is active, the computing architecture is able to determine when the memory arrays are completely filled and all records are occupied. The PC system can request that the user archive into the hard disk selected records, delete those selected records from the memory arrays, thus providing empty records in which new messages can be received. An alternative method would be to automatically, without user intervention, archive and delete the oldest records first.
 When the PC is inactive, and the PDA is receiving incoming messages, there is a greater concern of running out of records in the PDA memory array 500. A typical scenario is the following. In order to save battery power, the PC system is made inactive or placed into a suspend state. The PC system is not able to receive messages, however, the computer architecture is able to continue receiving messages through the PDA system. Messages come in, take up record space, and without some operator intervention, accumulate, and fill up the PDA memory array 500. New messages cannot be received until messages are deleted and records clear. A predetermined method to delete old messages to free up records to receive new messages can be arranged. This arrangement however, presents a problem when a user has not read all of the messages and older unread messages are deleted without the user saving or having the opportunity to read the message.
 Now referring to FIG. 5D illustrated are a PDA memory array and a PC memory With synchronized and non-synchronized records. When the PC system is inactive, the PDA system continues to receive messages and its records are filled with the messages. Since the PC system is inactive, the records of PC memory array 530 that correspond to records of PDA memory array 500 that are filled with new messages are not synchronized. “Record 1” 512 of PDA memory array 500 is not synchronized to “Record 1” 532 of PC memory array 530. Therefore “Record 1” 532 is “empty” and contains no message (information). As new messages are received by the PDA system, while the PC is inactive the records fill up, however, only the records in PDA memory array 500 are filled. Illustrated is a filled PDA memory array 500. “Record 1” 512, “Record 2” 514, and all records up to and including “Record N” are filled records in PDA memory array 500. These new messages contained in PDA memory array 500, however, are not synchronized with their corresponding records in PC memory array 530 which are “Record 1” 532, “Record 2” 534 up to and including “Record N” 536. In this particular example, “Record N+1” 518 of PDA memory array 500 is synchronized to “Record N+1” 538 of PC memory array 530. And all records up to and including “Record N+P” 520 of PDA memory array 500 are synchronized with “Record N+P” 540 of PC memory array 530.
 Since the PC memory array 500 can archive old messages into hard drive memory, the older synchronized files can be archived and the records deleted, thus freeing up space for new messages. Now referring to FIG. 5E illustrated is PDA memory array 500 with free space and an empty PC memory array 530. After archiving the messages of the synchronized records, in this particular example, “Record N+1” 538 up to and including “Record N +P” 540 of PC memory array 500, the records “Record N+1” 518 up to and including “Record N+P” 520 of PDA memory array 500 are deleted, freeing up these records in order to receive new messages. The user can be made aware that messages have been deleted from the PDA system, and that they may be retrieved since they have been archived in the PC system.
 This archiving and deletion process takes place until all the records of the PDA memory array 500 are filled. This process occurs while the PC system is inactive or suspended. When the PC system is activated, synchronization of the records can take place. As the PDA system remains active and receiving messages, and the PC system remains inactive, the PDA memory array 530 fills up with non-synchronized messages. When the EOM 522 of PDA memory array 530 is reached, the PDA system can either look to a predetermined preference to delete records and provide space for incoming messages or the PDA system can alert the user that the PDA memory array 500 is filled and request action from the user.
 In order to avoid having the user manually look at, read, and select records to delete from the PDA memory array 500, the following can take place. The PDA system can activate or wake up from a suspend state the PC system when PDA memory array 500 is full. As the PC system is awoken, records from the PDA memory array 500 are synchronized to the PC memory array 530. As files are synchronized, records from the PDA memory array 500 are erased and the space made available for new messages. Alternatively, the PDA system can stop receiving messages and allow the user to read the messages, and delete the messages from the records after they have been read.
 Variations of the synchronization process can include providing alerts to the user as to messages that are being deleted from the memory arrays. The user can also be informed of actions that are needed to be taken such as reading messages or manually activating the PC system. A provision can be made for the PDA memory array 500 to contain headers for the records contained therein. The headers of the individual records are used to identify that messages have been purged and archived to the PC system memory. The user also is made aware that the messages can be retrieved from the PC system memory. Embodiments of the invention can include provision for the user to set preferences as to messages that may be received and stored in the PDA memory array 500 without purging. Also the preference can include automatically purging certain messages. A flag may be set for incoming messages which identifies them as important messages that require the user's attention. Alternatively, “junk e-mail” or other unwanted messages without a special flag, messages that would take up valuable record space in the PDA memory array, may be automatically purged and sent or not sent to the PC system memory.
 Although the present invention has been described in connection with several embodiments, the invention is not intended to be limited to the specific forms set forth herein, but on the contrary, it is intended to cover such alternatives, modifications, and equivalents as can be reasonably included with in the spirit and scope of the invention as defined by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US2151733||May 4, 1936||Mar 28, 1939||American Box Board Co||Container|
|CH283612A *||Title not available|
|FR1392029A *||Title not available|
|FR2166276A1 *||Title not available|
|GB533718A||Title not available|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7003309 *||May 23, 2002||Feb 21, 2006||Rohm Co., Ltd.||Master-slave communication system and electronic apparatus utilizing such system|
|US7062593 *||Mar 18, 2002||Jun 13, 2006||Via Technologies, Inc.||Circuit system and method for data transmission between LPC devices|
|US7184003||Jan 13, 2003||Feb 27, 2007||Dualcor Technologies, Inc.||Personal electronics device with display switching|
|US7216242||Feb 9, 2005||May 8, 2007||Dualcor Technologies, Inc.||Personal electronics device with appliance drive features|
|US7231531||Feb 28, 2003||Jun 12, 2007||Dualcor Technologies, Inc.||Personal electronics device with a dual core processor|
|US7623893||Feb 25, 2008||Nov 24, 2009||Dualcor Technologies, Inc.||Personal electronics device with common application platform|
|US7921239||Aug 8, 2008||Apr 5, 2011||Dell Products, Lp||Multi-mode processing module and method of use|
|US7929946 *||May 24, 2005||Apr 19, 2011||Rathus Spencer A||Remote subscriber identification (RSID) system and method|
|US8037333||Oct 31, 2008||Oct 11, 2011||Dell Products, Lp||Information handling system with processing system, low-power processing system and shared resources|
|US8065540||Oct 31, 2008||Nov 22, 2011||Dell Products, Lp||Power control for information handling system having shared resources|
|US8131904||Aug 8, 2008||Mar 6, 2012||Dell Products, Lp||Processing module, interface, and information handling system|
|US8134565||Aug 8, 2008||Mar 13, 2012||Dell Products, Lp||System, module and method of enabling a video interface within a limited resource enabled information handling system|
|US8255595||Feb 25, 2011||Aug 28, 2012||Dell Products, Lp||Enabling access to peripheral resources at a processor|
|US8369811||Jul 17, 2009||Feb 5, 2013||Dell Products, Lp||System and method for radio antenna sharing in an information handling system|
|US8370673||Oct 30, 2008||Feb 5, 2013||Dell Products, Lp||System and method of utilizing resources within an information handling system|
|US8463957||Jul 25, 2012||Jun 11, 2013||Dell Products, Lp||Enabling access to peripheral resources at a processor|
|US8489557 *||Mar 22, 2010||Jul 16, 2013||Research In Motion Limited||Method, system and apparatus for archiving data|
|US8520014||Feb 3, 2012||Aug 27, 2013||Dell Products, Lp||System, module, and method of enabling a video interface within a limited resource enabled information handling system|
|US8583953||Oct 19, 2011||Nov 12, 2013||Dell Products, Lp||Power control for information handling system having shared resources|
|US8682274 *||Dec 31, 2012||Mar 25, 2014||Dell Products, Lp||System and method for radio antenna sharing in an information handling system|
|US8769328||Aug 6, 2012||Jul 1, 2014||Dell Products, Lp||System and method of utilizing resources within an information handling system|
|US8799695||Aug 16, 2012||Aug 5, 2014||Dell Products, Lp||Information handling system with processing system, low-power processing system and shared resources|
|US8863268||Oct 29, 2008||Oct 14, 2014||Dell Products, Lp||Security module and method within an information handling system|
|US8934755||Jun 8, 2012||Jan 13, 2015||Dell Products, Lp||System and method for managing multiple independent graphic sources in an information handling system|
|US20060285663 *||May 24, 2005||Dec 21, 2006||Rathus Spencer A||Remote Subscriber Identification (RSID) system and method|
|US20110231371 *||Sep 22, 2011||Research In Motion Limited||Method, system and apparatus for archiving data|
|US20110246526 *||Oct 6, 2011||Yuri Finkelstein||Service level agreement based storage access|
|US20130115896 *||May 9, 2013||Dell Products, Lp||System and Method for Radio Antenna Sharing in an Information Handling System|
|U.S. Classification||455/556.2, 707/E17.005, 455/557|
|Cooperative Classification||G06F17/30578, Y02B60/188|
|Jan 26, 2001||AS||Assignment|
Owner name: DELL PRODUCTS, L.P., TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WATTS, LA VAUGHN F., JR.;SATO, NOBUYUKI ALBERT;HUBER, GARY DOUGLAS;REEL/FRAME:011500/0911
Effective date: 20010126