Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20030046442 A1
Publication typeApplication
Application numberUS 10/271,680
Publication dateMar 6, 2003
Filing dateOct 15, 2002
Priority dateJun 14, 1999
Also published asUS6490616, WO2000077679A2, WO2000077679A3, WO2000077679A9
Publication number10271680, 271680, US 2003/0046442 A1, US 2003/046442 A1, US 20030046442 A1, US 20030046442A1, US 2003046442 A1, US 2003046442A1, US-A1-20030046442, US-A1-2003046442, US2003/0046442A1, US2003/046442A1, US20030046442 A1, US20030046442A1, US2003046442 A1, US2003046442A1
InventorsStephen Maryka, Bertrand Michaud, Greg Dick
Original AssigneeStephen Maryka, Bertrand Michaud, Greg Dick
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Method and apparatus for incremental download from server to client
US 20030046442 A1
Abstract
A method and system for transferring objects between computers, especially a server and a device in a Java environment, is provided. A server connected to the device interrogates the device to determine whether the device has the available resources to accept a download, and to determine if any of objects included in the download are already resident on the device. Using a gateway object on the device, and a gateway managed-object on the server, the server passes an archive of the necessary objects, not presently available on the device, to the gateway via the gateway managed-object. The gateway then instructs a persistent storage repository on the device to commit the archive to persistent storage. A flag is set at the start of the archive-committing process, such that if the device loses power during the archive-committing process, upon re-initialization of the device, the device can determine that the archive-committing process failed and will instruct the persistent storage to free-up storage area used during the archive-committing process. The transferal of objects can then be recommenced once the server and device reestablish communication. The present invention can provide an effective means to ensure a stable recovery of the device upon re-initialization, should the file transfer and/or archive-commit process fail due to a power failure to the device. Further, the invention can increase efficient use of device resources by not loading redundant components on the device and can reduce bandwidth requirements and/or download times as redundant information is not transferred.
Images(8)
Previous page
Next page
Claims(20)
We claim:
1. A method for transferring at least a portion of a group of objects to a first computer from a second computer, said first computer having a central processing unit, random access memory and a persistent storage means, said first and second computers connected by a communication medium, said method comprising the steps of:
interrogating said first computer for configuration information;
determining required objects for transfer based on an operation that considers, at least in part, said configuration information and said group of objects;
packaging said required objects into an archive;
transferring said archive to said random access memory;
setting an archive-commit flag on;
committing said archive to said persistent storage;
setting said archive commit flag off;
setting a list-commit flag on;
committing a list of said required objects to said persistent storage;
setting said list-commit flag off; and
activating said required objects in said random access memory.
2. The method according to claim 1 wherein said objects are JavaBeans beans based on the JavaBeans specification.
3. The method according to claim 1 wherein said archive is a Java ARchive.
4. The method according to claim 1 wherein said archive is committed to a repository area of said persistent storage.
5. The method according to claim 1 wherein said list is committed to a registry area of said persistent storage.
6. A method in the initializing a device comprising the steps of:
determining whether an archive was being committed to persistent storage when said device was powered-off; and
instructing said persistent storage to clear the portion of said archive committed to persistent storage when said step of determining establishes that an archive was being committed when said device was powered-off.
7. The method according to claim 4 wherein said archive is a Java Archive of JavaBean objects.
8. The method according to claim 1 wherein said archive is committed to a repository area of said persistent storage.
9. A method in the initialization of a device comprising the steps of:
determining whether a list of objects from an archive was being committed to a registry area of persistent storage when said device was powered-off; and
examining said archive to determine a remaining list of objects to be committed to said registry area when said step of determining establishes that a list was being committed when said device was powered-off; and
committing the remainder of said list established from said examining step.
10. The method according to claim 6 wherein said archive is a Java Archive of JavaBean objects.
11. The method according to claim 6 wherein said archive is committed to a repository area of said persistent storage.
12. A system for transferring at least a portion of a group of objects between computers, comprising:
a first computer having a central processing unit, random access memory, a persistent storage repository for storing archives of objects, a persistent storage registry for storing a list of said objects, and a first network interface means, said first computer operable to execute said objects, and operable to execute a gateway object having privileges to interact with said repository and said register;
a second computer having a second interface means connectable to said first computer via a communication medium, said second computer having a file storage means for storing a group of objects, said second computer being operable to execute an application and a gateway managed object, said gateway managed object being a proxy for said gateway object so that said application can interrogate said gateway object for configuration information of said device and transfer an archive of at least a portion of said group via said gateway managed object to said gateway object, said archive packaged based on an operation that considers, at least in part, said configuration information;
such that when said gateway object receives said archive, said gateway object instructs said repository to commit said archive to said repository and a list of objects in said archive to said registry, said device setting at least one flag during said commission of said archive and said list to allow device recovery upon initialization if said device loses power during said commission.
13. The system according to claim 12 wherein said objects are JavaBeans beans based on the JavaBeans specification.
14. The system according to claim 12 wherein said archive is a Java ARchive.
15. The system according to claim 12 wherein said configuration information includes an inventory of available random access memory on said device.
16. The system according to claim 12 wherein said configuration information includes an inventory of available persistent storage on said device.
17. The system according to claim 12 wherein said configuration information includes a list of objects from said group of objects which are already resident in said device.
18. The system according to claim 12 wherein said gateway managed object is determined using the mogen tool from the Java Dynamic Management Kit.
19. The system according to claim 12 wherein said first computer is a Java-based intelligent device and said second computer is a Java-based network computing server.
20. The system according to claim 12 including a first flag set during said commission of said archive and a second flag set during said commission of said list.
Description
FIELD OF THE INVENTION

[0001] The present invention relates generally to file transfers over a communication medium and more particularly relates to a method and system for transferring objects from one computer to another.

BACKGROUND OF THE INVENTION

[0002] The development of network computing (“NC”) technology has spawned the development of several intelligent devices, ranging from simple thin-client desk-top computers, to internet-aware screen phones, mobile phones, personal digital assistants (“PDAs”), public kiosks, smart-card based banking devices, etc. The Java computer language has been an important feature of this technological development, as it provides a “Write Once, Run Anywhere” platform which is an effective way to transfer an application from a server to a device for local execution on the device. Thus, Java provides the ability to transparently deliver, via a communications mechanism such as a general purpose network or a special purpose communications port, software to a variety of devices having different hardware platforms and has become a standard language for internet applications.

[0003] Additional transfer functionality is provided in the more recent Java Dynamic Management Kit, and discussed in Java Dynamic Management Kit 3.0 Programming Guide, 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, Calif. 94303 U.S.A. (“JDMK”).

[0004] While Java and the JDMK provide effective ways to pass or transfer a software application to a device, they do not provide solutions to certain problems that can arise with file transfers. For example, existing solutions do not provide a robust recovery mechanism once power is restored, should power to the device be interrupted during a transfer. Further, where the communication medium has reduced bandwidth, it can be desirable to only download the components of the application which are not already resident on the device. In addition, Java and the JDMK do not provide an infrastructure for managing the persistent storage of Java objects.

SUMMARY OF THE INVENTION

[0005] It is an object of the present invention to provide a novel method and system for transferring objects between computers which obviates or mitigates at least one of the disadvantages of the prior art.

[0006] The present invention provides a method and system for transferring objects between computers, especially a server and a device in a Java environment. A server connected to the device interrogates the device to determine whether the device has the available resources to accept a download, and to determine if any of objects included in the download are already resident on the device. Using a gateway object on the device, and a gateway managed-object on the server, the server passes an archive of the necessary objects, specifically those not presently available on the device, to the gateway via the gateway managed-object. The gateway then instructs a persistent storage repository on the device to commit the archive to persistent storage.

[0007] A flag is set at the start of the archive-committing process, such that if the device loses power during the archive-committing process, upon re-initialization of the device, the device can determine that the archive-committing process failed and will instruct the persistent storage to free-up storage area used during the archive-committing process. The transferal of objects can then be recommenced once the server and device reestablish communication.

[0008] The present invention can provide an effective means to ensure a stable recovery of the device upon re-initialization, should the file transfer and/or archive-commit process fail due to a power failure to the device. Further, the invention can increase efficient use of device resources by not loading redundant components on the device and can reduce bandwidth requirements and/or download times as redundant information is not transferred.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The present invention will now be explained, by way of example only, with reference to certain embodiments and the attached Figures in which:

[0010]FIG. 1 is a schematic diagram of a system for transferring objects between two computers in accordance with an embodiment of the present invention;

[0011]FIG. 2 is a flow-chart of a method for transferring objects between two computers in accordance with an embodiment of the present invention;

[0012]FIG. 3 is a schematic diagram of the system of FIG. 1 showing the performance of a step of the method of FIG. 2;

[0013]FIG. 4 is a schematic diagram of the system of FIG. 1 showing the performance of a step of the method of FIG. 2;

[0014]FIG. 5 is a schematic diagram of the system of FIG. 1 showing the performance of a step of the method of FIG. 2;

[0015]FIG. 6 is a schematic diagram of the system of FIG. 1 showing the performance of a step of the method of FIG. 2; and

[0016]FIG. 7 is a schematic diagram of the system of FIG. 1 showing the performance of a step of the method of FIG. 2.

DETAILED DESCRIPTION OF THE INVENTION

[0017] Referring now to FIG. 1, a system for transferring objects between two computers is indicated generally at 20. System 20 includes two computers, a device 22 and a server 24. Device 22 is any intelligent device as will occur to those of skill in the art, and examples of such devices include a ‘thin-client terminal’, an internet-aware screen phone, mobile phone, personal digital assistant (“PDA”), public kiosk and/or smart-card based banking device, etc. and is operable to execute software applications created in a language such as Java.

[0018] In a present embodiment of the invention, device 22 is Java-based and has a basic set of hardware resources including a central processing unit (not shown), and a persistent storage means (not shown) such as EEPROM, flash memory, floppy disc etc. Device 22 further includes random access memory (not shown) and a communications means, such as a network interface card or other network interface means (not shown) to allow device 22 to communicate over a communication medium 26 such as the internet.

[0019] Server 24 is any suitable server, as will occur to those of skill in the art, such as the Sun Enterprise 450 server sold by Sun Microsystems of Palo Alto Calif., and is generally operable to function as a network computing server. In an embodiment of the invention, server 24 is Java-based and includes a central processing unit (not shown), random access memory (not shown), a data storage means 38, and a communications means, such as a network interface card or other network interface means (not shown) to allow server 24 to communicate over communication medium 26.

[0020] Software within device 22 includes a Java-based framework 28 that is associated with Java-based objects (O1, O2 . . . O8) which in a present embodiment are JavaBeans. Specifications for frameworks and JavaBean can be found in Java Dynamic Management Kit 3.0 Programming Guide, Chapter 10, 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, Calif. 94303 U.S.A. (“JDMK”) and Sun Microsystems, JavaBeans™, Version 1.01, Hamilton, G., Editor, 1996, Sun Microsystems Inc., Mountain View Calif. (“JavaBeans Specification”).

[0021] Framework 28 is associated with a client-adapter 30, which connects framework 28 to external software applications via the network interface means and over communication medium 26. It will be apparent to those of skill in the art that client-adapter 30 provides a software interface between the software and the network interface means on device 22. In a present embodiment, client-adapter 30 is the client component of an adapter determined using the adapter tool provided with the JDMK, and discussed in detail in Chapter 5 of JDMK. However, it will be apparent that other client-adapter means can be used for other types of programming, as will occur to those of skill in the art.

[0022] It will be understood by those of skill in the art that framework 28 is a type of registry for registering the existence of objects (O1, O2 . . . O8). It will be further understood that objects (O1, O2 . . . O8) form at least a portion of at least one software application intended for execution by a user of device 22. In other embodiments, there can be a different number of objects, and/or objects (O1, O2 . . . O8) can be another type of program-language or component architecture, such as ActiveX, COM or CORBA objects, as will occur to those of skill in the art. It will be further understood that a registry or framework 28 can be incorporated into each object (O1, O2 . . . O8) thus eliminating the need for a separate framework 28.

[0023] Framework 28 also includes a persistent storage registry 31, that is resident in the persistent storage means of device 22, and is used to establish the contents of framework 28 on initialization or start up of device 22. Registry 31 is associated with a registry-manager object that manages the contents of registry 31. In a present embodiment registry 31 is an m-bean repository in accordance with the JDMK and lists objects (O1, O2, . . . O8) within framework 28.

[0024] Device 22 also includes a persistent storage repository 33 that is associated with a portion of the persistent storage means of device 22 and can store objects (O1, O2 . . . O8). As shown in FIG. 1, repository 33 has a plurality of storage blocks (SB1 . . . SBn), where SB1 contains objects (O1, O2 . . . O4), SB2 contains objects (O5 . . . O8) and SB3 . . . SBn are empty. It is to be understood that each storage block (SB1 . . . SBn) need not contain an identical number of objects, and that the exact size of each storage block (SB1 . . . SBn) can be dynamically allocated. As such, storage blocks SB3 . . . SBn can be considered a contiguous block of available storage space. It will be further understood that in other embodiments of the invention, certain temporary objects resident in framework 28 need not be stored in repository 33.

[0025] Repository 33 is also associated with a repository-manager object that manages the storage and retrieval of data from the persistent storage means. In a present embodiment of the invention, storage blocks (SB1 . . . SBn) are Java Archives (“JAR”) and repository 33 is a Java ARchive (“JAR”) repository.

[0026] Framework 28 also includes a gateway G which in the present embodiment is a managed-bean object or “m-bean”, (the specifications for which are discussed in Chapter 3 of JDMK). Once device 22 is initialized, gateway G has unique privileges to interact (via a method call or other suitable means) with and manage the contents of register 31 and repository 33.

[0027] Software within server 24 includes an application APP and a gateway managed-object GMO, which is created by performing a managed-object generation operation on gateway G. It will be understood that gateway managed-object GMO is a client-bean (“c-bean”), or proxy, shell, wrapper or other suitable representation of gateway G. As gateway managed-object GMO is a representation for gateway G, application APP can transparently access gateway G, through method calls to gateway managed-object GMO.

[0028] In a present embodiment, the managed-object generation operation is the “mogen” tool provided with the Java Dynamic Management Kit, and discussed in “Generating a C-bean” of Chapter 2 of Sun Microsystems, Java Dynamic Management Kit. It is to be understood, however, that other managed-object generation operations can be used as will occur to those of skill in the art.

[0029] Both application APP and gateway managed-object GMO are associated with a server-adapter 36, for connection to external software applications via communication medium 26. The previously-mentioned specifications are applicable to server-adapter 36, which is complementary to client-adapter 30, and collectively server-adapter 36 and client-adapter 30 compose an adapter determined using the adapter tool provided with the JDMK, and discussed in Chapter 5 of JDMK. Similar to client-adapter 30, server-adapter 36 provides a software interface between the software and the network interface means on server 24.

[0030] Server 24 also includes four objects (O1, O5, O9, O10) which are stored in file storage means 38, and are intended for transfer to device 22 and execution or activation thereon. In a present embodiment objects (O1, O5, O9, O10) are all JavaBeans, and objects O1 and O5 in storage means 38 are the same as objects O1 and O5 resident in device 22.

[0031] A method for transferring objects between server 24 and device 22 will now be discussed with reference to the flowchart of FIG. 2 and system 20. In a present embodiment, the method of FIG. 2 is commenced based on a determination that device 22 requires objects (O1, O5, O9, O10) for an application, and that these objects are currently stored in file storage means 38. At step 100, device 22 is interrogated to determine its configuration. In a present embodiment, this is accomplished by application APP which makes a method-call to gateway G via gateway managed-object GMO. During this method-call, application APP determines the amount of persistent storage space available on device 22, and a list of objects currently stored in device 22 and/or any other properties of device 22 necessary for a file transfer. Application APP determines that SB, contains objects (O1 . . . O4), SB2 contains objects (O5 . . . O8) and that storage block SB3 . . . SBn are available for storage.

[0032] At step 120, the objects required for transfer are determined. In a present embodiment, step 120 is accomplished by application APP, which compares the configuration data obtained at step 100 with the list of objects needed by device 22. Application APP thus determines that object O1 and object O5 are already resident on device 22 and it is therefore only necessary to transfer object O9 and object O10 from server 24 to device 22. Application APP also notes that storage block SB3 is empty and large enough to store object O9 and object O10.

[0033] It will be apparent that if application APP determined that no objects were required for transfer to device 22, or where there was insufficient storage blocks to store the objects required for transfer, then the method would terminate and could be recommenced from step 100 at a later time, if necessary.

[0034] At step 140, the objects required by device 22 are packaged into an archive in preparation for transfer and specifically, object O9 and object O10 are packaged into an archive 40, as shown in FIG. 3. In a present embodiment, archive 40 is a Java Archive (“JAR”) and includes a checksum or any other suitable verification means attached thereto.

[0035] At step 160, as shown in FIG. 4, archive 40 is transferred from server 24 to the random access memory of device 22 via communication medium 26, as indicated in dashed line. In a present embodiment, the archive 40 is passed as a parameter within a method call to gateway G.

[0036] At step 180 an archive-commit flag, which in a present embodiment is present in gateway G, is set ‘on’. It will be understood that in other embodiments, the archive-commit flag can be implemented in a variety of different ways. As will be discussed in greater detail below, the archive-commit flag is used during initialization or boot-up to determine whether an archive was being committed when the operation of device 22 was disrupted.

[0037] At step 200, as shown in FIG. 5, gateway G instructs repository 33 to commit archive 40 to persistent storage. Gateway G makes a method call to the repository-manager associated with repository 33 to write archive 40 to persistent storage associated with repository 33. In a present embodiment, the checksum associated with archive 40 is also used to verify the integrity of archive 40 during the storage procedure.

[0038] It is to be understood that if device 22 experiences a power failure or otherwise shuts down during step 200, then during a subsequent initialization of device 22, gateway G will determine that its archive-commit flag is ‘on’, and determine that a power-failure or shut down occurred during step 200. Accordingly, gateway G will query the repository-manager querying as to whether archive 40 was successfully committed to storage. If successful, the method proceeds to step 210. However, if unsuccessful, the repository-manager will free-up any storage blocks being used during step 200 and, once device 22 reestablishes communication with server 22, application APP will then begin at step 100 and re-attempt the file transfer.

[0039] Assuming that archive 40 is successfully committed to persistent storage, as shown in FIG. 5, then method of the present embodiment proceeds to step 210 where the archive-commit flag is set ‘off’, and a list-commit flag is set ‘on’. In a present embodiment, the list-commit flag is present in gateway G, and is used by gateway G during initialization or boot-up to determine whether an archive was being committed when the operation of device 22 was disrupted.

[0040] As indicated in FIG. 6, at step 220 gateway G instructs registry 31 to commit the list of objects within archive 40 to persistent storage. Specifically, gateway G makes a method call to the registry-manager objects associated with registry 31 to list object O9 and object O10 in the persistent storage area associated with registry 31. It is to be understood that if the operation of device 22 if device 22 experiences a power failure or otherwise shuts down then during step 220, then during the subsequent initialization of device 22, gateway G will discover that the list-commit flag is ‘on’, and accordingly determine that step 220 failed. Accordingly, gateway G can commence a recovery operation of step 220 by instructing registry 31 to examine the contents of repository 33 to ascertain the list of objects that should be present in registry 31, and use this information to complete step 220.

[0041] However, if the operation of device 22 is not disrupted during step 220, then object O9 and object O10 are listed within registry 31 as shown in FIG. 6, and the method of the present embodiment proceeds to step 230.

[0042] At step 230, the list-commit flag is set off At step 240, object O9 and object O10 are activated by registry 31 which instantiates object O9 and object O10 within framework 28, as shown in FIG. 7. Accordingly, object O9 and object O10 now become available to applications executing on device 22.

[0043] While the embodiments discussed herein are directed to particular implementations of the present invention, it will be apparent that the sub-sets and variations to these embodiments are within the scope of the invention. For example, while the embodiments herein are directed to JavaBean objects, it will be apparent that other types of objects can be implemented in accordance with the teachings of the invention. It is also contemplated that the archive-commit flag and list-commit flags can be implemented in a variety of forms and recovery-means within device 22, in order to provide a robust mechanism to recover from a failed download and/or archive-commit procedure should device 22 lose power during such operations.

[0044] The present invention provides a novel method and system transferring objects between computers. The present invention is particularly useful in systems incorporating the Java Dynamic Management Kit, as it provides a means where only the required objects are actually transferred from the server to the device to improve the overall efficiency of the download.

[0045] Further, flags in the device can be used to determine whether a file transfer failed during initialization of the device, thereby improving the overall reliability of file transfers and providing an effective means of system recovery. File transfer reliability is further improved by the use of a verification means such as a checksum attached to the archive file before file transfer. This checksum can be used by the device to ensure the overall integrity of the objects when the objects are committed to persistent storage areas within the device. In addition, the invention can increase efficient use of device resources by not loading redundant components on the device.

Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US6826601Sep 4, 2002Nov 30, 2004Bea Systems, Inc.Exactly one cache framework
US7054955 *Jun 27, 2001May 30, 2006Microsoft CorporationSystem and method for recovering from a failed synchronization session
US7113980Sep 4, 2002Sep 26, 2006Bea Systems, Inc.Exactly once JMS communication
US7127480Dec 4, 2003Oct 24, 2006International Business Machines CorporationSystem, method and program for backing up a computer program
US7152181Jan 13, 2003Dec 19, 2006Bea Systems, Inc.Method for highly available transaction recovery for transaction processing systems
US7178050Jan 13, 2003Feb 13, 2007Bea Systems, Inc.System for highly available transaction recovery for transaction processing systems
US7296273Dec 4, 2003Nov 13, 2007International Business Machines CorporationSystem, method and program tool to reset an application
US7380155Feb 12, 2007May 27, 2008Bea Systems, Inc.System for highly available transaction recovery for transaction processing systems
US7392302Feb 13, 2003Jun 24, 2008Bea Systems, Inc.Systems and methods for automated service migration
US7392317Mar 7, 2007Jun 24, 2008Bea Systems, Inc.Systems and methods for migratable services
US7403996Feb 13, 2003Jul 22, 2008Bea Systems, Inc.Systems and methods for migratable services
US7406618Jan 4, 2006Jul 29, 2008Bea Systems, Inc.Apparatus for highly available transaction recovery for transaction processing systems
US7409420Oct 31, 2001Aug 5, 2008Bea Systems, Inc.Method and apparatus for session replication and failover
US7620842Jul 28, 2006Nov 17, 2009Bea Systems, Inc.Method for highly available transaction recovery for transaction processing systems
WO2003073311A1 *Feb 20, 2003Sep 4, 2003Bea Systems IncSystem and method for message driven bean service migration
Classifications
U.S. Classification719/316, 709/221
International ClassificationG06F9/445, H04L29/08, H04L29/06
Cooperative ClassificationH04L67/06, H04L67/2861, H04L67/34, H04L67/42, G06F9/44521
European ClassificationG06F9/445L, H04L29/06C8, H04L29/08N33, H04L29/08N5, H04L29/08N27U
Legal Events
DateCodeEventDescription
Oct 15, 2002ASAssignment
Owner name: WIND RIVER INTERNATIONAL LTD., CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MARYKA, STEPHEN;MICHAUD, BERTRAND;DICK, GREGORY;REEL/FRAME:013410/0070
Effective date: 19990614