WO2000077679A9 - Method and apparatus for incremental download from server to client - Google Patents

Method and apparatus for incremental download from server to client

Info

Publication number
WO2000077679A9
WO2000077679A9 PCT/CA2000/000706 CA0000706W WO0077679A9 WO 2000077679 A9 WO2000077679 A9 WO 2000077679A9 CA 0000706 W CA0000706 W CA 0000706W WO 0077679 A9 WO0077679 A9 WO 0077679A9
Authority
WO
WIPO (PCT)
Prior art keywords
archive
objects
persistent storage
gateway
list
Prior art date
Application number
PCT/CA2000/000706
Other languages
French (fr)
Other versions
WO2000077679A3 (en
WO2000077679A2 (en
Inventor
Stephen Maryka
Bertrand Michaud
Greg Dick
Original Assignee
Wind River Internat Inc
Stephen Maryka
Bertrand Michaud
Greg Dick
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Wind River Internat Inc, Stephen Maryka, Bertrand Michaud, Greg Dick filed Critical Wind River Internat Inc
Priority to AU53818/00A priority Critical patent/AU5381800A/en
Publication of WO2000077679A2 publication Critical patent/WO2000077679A2/en
Publication of WO2000077679A3 publication Critical patent/WO2000077679A3/en
Publication of WO2000077679A9 publication Critical patent/WO2000077679A9/en

Links

Classifications

    • 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • 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
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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

Definitions

  • the present invention relates generally to file- transfers over a commumcation medium and more particularly relates to a method and system for transferring objects from one computer to another.
  • NC network computing
  • PDAs personal digital assistants
  • Java 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.
  • 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.
  • JDMK' Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 U.S.A.
  • 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 arc 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.
  • 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 the objects included in the download are already resident on the device.
  • the server uses 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.
  • 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.
  • Figure 1 is a schematic diagram of a system for transferring objects between two computers in accordance with an embodiment of the present invention
  • Figure 2 is a flow-chart of a method for transferring objects between two computers in accordance with an embodiment of the present invention
  • Figure 3 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2
  • Figure 4 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2;
  • Figure 5 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2;
  • Figure 6 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2;
  • Figure 7 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2.
  • System 20 includes two computers, a device 22 and a server 24.
  • Device 22 is an 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.
  • PDA personal digital assistant
  • 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.
  • 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 CA, and is generally operable to function as a network computing server.
  • 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.
  • Java-based framework 28 that is associated with Java-based objects (O t O 2 ...O 8 ) which in a present embodiment are JavaBeans.
  • Java-based objects O t O 2 ...O 8
  • JavaBeans Java-based objects
  • Specifications for frameworks and JavaBeans can be found in Java Dynamic Management Kit 3.0 Programming Guide, Chapter 10, 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 U.S.A. (“JDMK”) and Sun Microsystems, JavaBeansTM, Version 1.01, Hamilton, G., Editor, 1996, Sun Microsystems Inc., Mountain View California (“JavaBeans Specification").
  • 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.
  • client-adapter 30 provides a software interface between the software and the network interface means on device 22.
  • 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.
  • client-adapter means can be used for other types of programming, as will occur to those of skill in the art.
  • framework 28 is a type of registry for registering the existence of objects (O, O 2 ...O 8 ). It will be further understood that objects (O, O 2 ...O 8 ) 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 (O, O 2 ...O g ) 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 (O, O 2 ...O 8 ) thus eliminating the need for a separate framework 28.
  • 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.
  • registry 31 is an m-bean repository in accordance with the JDMK and lists objects (O, O 2 ...O g ) within framework 28.
  • 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 (O, O 2 ...O g ).
  • repository 33 has a plurality of storage blocks (SB,...SB n ), where SB, contains objects (O, O 2 O 4 ), SB 2 contains objects (O 5 ... O 8 ) and SB 3 ...SB n are empty.
  • SB storage block
  • SB n each storage block (SB, ... SB n ) need not contain an identical number of objects, and that the exact size of each storage block (SB, ...SB n) can be dynamically allocated.
  • storage blocks SB 3 ... SB n 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.
  • Repository 33 is also associated with a repository-manager object that manages the storage and retrieval of data from the persistent storage means.
  • storage blocks (SB, ... SB N ) are Java Archives (“JAR”) and repository 33 is a Java Archive (“JAR”) repository.
  • 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).
  • 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.
  • Software within server 24 includes an application APP and a gateway managed-object G M0 , which is created by performing a managed-object generation operation on gateway G.
  • gateway managed- object G M0 is a client-bean ("c-bean”), or proxy, shell, wrapper or other suitable representation of gateway G.
  • gateway managed-obj ect G M0 is a representation for gateway G
  • application APP can transparently access gateway G, through method calls to gateway managed-object G MO .
  • 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.
  • Both application APP and gateway managed-object G M0 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.
  • server-adapter 36 provides a software interface between the software and the network interface means on server 24.
  • Server 24 also includes four objects (O,, O 5 , O 9 , O ]0 ) which are stored in file storage means 38, and are intended for transfer to device 22 and execution or activation thereon.
  • objects (O,, O 5 , O 9 , O, 0 ) are all JavaBeans, and objects O, and O 5 in storage means 38 are the same as objects O, and O 5 resident in device 22.
  • a method for transferring objects between server 24 and device 22 will now be discussed with reference to the flowchart of Figure 2 and system 20.
  • the method of Figure 2 is commenced based on a determination that device 22 requires objects (O,, O 5 , O 9 , O, 0 ) for an application, and that these objects are currently stored in file storage means 38.
  • 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 G MO .
  • 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 (O,, ... O 4 ), SB 2 contains objects (O 5 ... O g ) and that storage block SB 3 ... SB N are available for storage.
  • step 120 the objects required for transfer are determined.
  • 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 O, and object O 5 are already resident on device 22 and it is therefore only necessary to transfer object O 9 and object O 10 from server 24 to device 22.
  • Application APP also notes that storage block SB 3 is empty and large enough to store object O 9 and object O 10 . It will be apparent that if application APP determined that no obj ects 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.
  • archive 40 is a Java Archive ("JAR") and includes a checksum or any other suitable verification means attached thereto.
  • archive 40 is transferred from server 24 to the random access memory of device 22 via communication medium 26, as indicated in dashed line.
  • the archive 40 is passed as a parameter within a method call to gateway G.
  • 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.
  • 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.
  • the checksum associated with archive 40 is also used to verify the integrity of archive 40 during the storage procedure.
  • 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.
  • step 210 the archive-commit flag is set 'off, and a list-commit flag is set 'on'.
  • 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.
  • 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 O 9 and object 10, 0 in the persistent storage area associated with registry 31.
  • 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. However, if the operation of device 22 is not disrupted during step 220, then object O 9 and O 10 are listed within registry 31 as shown in Figure 6, and the method of the present embodiment proceeds to step 230.
  • the list-commit flag is set off.
  • object O 9 and O, 0 are activated by registry 31 which instantiates object O 9 and O 10 within framework 28, as shown in Figure 7. Accordingly, object O 9 and O, 0 now become available to applications executing on device 22.
  • the present invention provides a novel method and system for 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.
  • 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.
  • the invention can increase efficient use of the device resources by not loading redundant components on the device.

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.

Description

METHOD AND APPARATUS FOR INCREMENTAL DOWNLOAD FROM SERVER TO CLIENT
Field of the Invention
The present invention relates generally to file- transfers over a commumcation medium and more particularly relates to a method and system for transferring objects from one computer to another.
Background of the Invention
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.
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, California 94303 U.S.A. ("JDMK').
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 arc 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 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.
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 the 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.
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.
Brief Description of the Drawings The present invention will now be explained, by way of example only, with reference to certain embodiments and the attached Figures in which:
Figure 1 is a schematic diagram of a system for transferring objects between two computers in accordance with an embodiment of the present invention;
Figure 2 is a flow-chart of a method for transferring objects between two computers in accordance with an embodiment of the present invention;
Figure 3 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2; Figure 4 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2;
Figure 5 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2;
Figure 6 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2; and
Figure 7 is a schematic diagram of the system of Figure 1 showing the performance of a step of the method of Figure 2.
Detailed Description of the Invention Referring now to Figure 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 an 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.
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.
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 CA, 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.
Software within device 22 includes a Java-based framework 28 that is associated with Java-based objects (Ot O2...O8) which in a present embodiment are JavaBeans. Specifications for frameworks and JavaBeans can be found in Java Dynamic Management Kit 3.0 Programming Guide, Chapter 10, 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 U.S.A. ("JDMK") and Sun Microsystems, JavaBeans™, Version 1.01, Hamilton, G., Editor, 1996, Sun Microsystems Inc., Mountain View California ("JavaBeans Specification").
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.
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 (O, O2...O8). It will be further understood that objects (O, 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 (O, O2...Og) 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 (O, O2...O8) thus eliminating the need for a separate framework 28.
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 (O, O2...Og) within framework 28.
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 (O, O2...Og). As shown in Figure 1 , repository 33 has a plurality of storage blocks (SB,...SBn), where SB, contains objects (O, O2 O4), SB2 contains objects (O5 ... O8) and SB3 ...SBn are empty. It is to be understood that each storage block (SB, ... SBn) need not contain an identical number of objects, and that the exact size of each storage block (SB, ...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.
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 (SB, ... SBN) are Java Archives ("JAR") and repository 33 is a Java Archive ("JAR") repository.
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. Software within server 24 includes an application APP and a gateway managed-object GM0, which is created by performing a managed-object generation operation on gateway G. It will be understood that gateway managed- object GM0 is a client-bean ("c-bean"), or proxy, shell, wrapper or other suitable representation of gateway G. As gateway managed-obj ect GM0 is a representation for gateway G, application APP can transparently access gateway G, through method calls to gateway managed-object GMO.
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.
Both application APP and gateway managed-object GM0 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.
Server 24 also includes four objects (O,, O5, O9, O]0) 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 (O,, O5, O9, O,0) are all JavaBeans, and objects O, and O5 in storage means 38 are the same as objects O, and O5 resident in device 22.
A method for transferring objects between server 24 and device 22 will now be discussed with reference to the flowchart of Figure 2 and system 20. In a present embodiment, the method of Figure 2 is commenced based on a determination that device 22 requires objects (O,, O5, O9, O,0) 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 (O,, ... O4), SB2 contains objects (O5 ... Og) and that storage block SB3 ... SBN are available for storage.
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 O, 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. It will be apparent that if application APP determined that no obj ects 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.
At step 140, the objects required by device 22 are packaged into an archive in preparation for transfer and specifically, object O9 and O,0 are packaged into an archive 40, as shown in Figure 3. In a present embodiment, archive 40 is a Java Archive ("JAR") and includes a checksum or any other suitable verification means attached thereto.
At step 160, as shown in Figure 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.
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.
At step 200, as snown in Figure 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.
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.
Assuming that archive 40 is successfully committed to persistent storage, as shown in Figure 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. As indicated in Figure 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 10, 0 in the persistent storage area associated with registry 31. It is to be understood that if during operation of device 22 device 22 experiences a power failure or otherwise shuts down 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. However, if the operation of device 22 is not disrupted during step 220, then object O9 and O10 are listed within registry 31 as shown in Figure 6, and the method of the present embodiment proceeds to step 230.
At step 230, the list-commit flag is set off. At step 240, object O9 and O,0 are activated by registry 31 which instantiates object O9 and O10 within framework 28, as shown in Figure 7. Accordingly, object O9 and O,0 now become available to applications executing on device 22.
While the embodiments discussed 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 obj ects 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.
The present invention provides a novel method and system for 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.
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 the device resources by not loading redundant components on the device.

Claims

We claim:
1. A method for transferring at least a portion of a group of obj ects 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 object.
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 obj ects 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 obj ect 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.
1 5. 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.
PCT/CA2000/000706 1999-06-14 2000-06-14 Method and apparatus for incremental download from server to client WO2000077679A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU53818/00A AU5381800A (en) 1999-06-14 2000-06-14 Method and apparatus for incremental download from server to client

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/332,069 1999-06-14
US09/332,069 US6490616B1 (en) 1999-06-14 1999-06-14 Method and apparatus for incremental download from server to client

Publications (3)

Publication Number Publication Date
WO2000077679A2 WO2000077679A2 (en) 2000-12-21
WO2000077679A3 WO2000077679A3 (en) 2001-10-04
WO2000077679A9 true WO2000077679A9 (en) 2002-08-29

Family

ID=23296602

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2000/000706 WO2000077679A2 (en) 1999-06-14 2000-06-14 Method and apparatus for incremental download from server to client

Country Status (3)

Country Link
US (2) US6490616B1 (en)
AU (1) AU5381800A (en)
WO (1) WO2000077679A2 (en)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000207219A (en) * 1999-01-18 2000-07-28 Fujitsu Ten Ltd Communication system for between on-vehicle terminal and center, and the on-vehicle terminal used for communication system
US6928468B2 (en) * 1999-10-29 2005-08-09 Koninklijke Philips Electronics N.V. System for broadcasting software applications and portable data communications device for use in such a system
US7085805B1 (en) * 2000-07-07 2006-08-01 Sun Microsystems, Inc. Remote device management in grouped server environment
US7584269B2 (en) * 2001-03-09 2009-09-01 International Business Machines Corporation Method for providing kiosk service offerings in a personal area network
US7054955B2 (en) * 2001-06-27 2006-05-30 Microsoft Corporation System and method for recovering from a failed synchronization session
US7194503B2 (en) * 2001-06-29 2007-03-20 Microsoft Corporation System and method to query settings on a mobile device
US7702791B2 (en) 2001-07-16 2010-04-20 Bea Systems, Inc. Hardware load-balancing apparatus for session replication
US7409420B2 (en) 2001-07-16 2008-08-05 Bea Systems, Inc. Method and apparatus for session replication and failover
WO2003009126A1 (en) * 2001-07-19 2003-01-30 Digeo, Inc. System and method for managing television programs within an entertainment system
US20030018970A1 (en) * 2001-07-19 2003-01-23 Digeo, Inc. Object representation of television programs within an interactive television system
US6826601B2 (en) 2001-09-06 2004-11-30 Bea Systems, Inc. Exactly one cache framework
US7113980B2 (en) * 2001-09-06 2006-09-26 Bea Systems, Inc. Exactly once JMS communication
US7403996B2 (en) 2002-02-21 2008-07-22 Bea Systems, Inc. Systems and methods for migratable services
WO2003073311A1 (en) * 2002-02-21 2003-09-04 Bea Systems, Inc. System and method for message driven bean service migration
US7178050B2 (en) * 2002-02-22 2007-02-13 Bea Systems, Inc. System for highly available transaction recovery for transaction processing systems
US7152181B2 (en) 2002-02-22 2006-12-19 Bea Systems, Inc. Method for highly available transaction recovery for transaction processing systems
JP3952893B2 (en) * 2002-07-30 2007-08-01 株式会社日立製作所 Network device and automatic program update method
US6891860B2 (en) * 2002-08-21 2005-05-10 Defywire, Inc. Method and apparatus for establishing multiple bandwidth-limited connections for a communication device
US7240104B2 (en) * 2002-08-21 2007-07-03 Defywire, Inc. Method and apparatus for managing resources stored on a communication device
US7086051B2 (en) * 2002-08-21 2006-08-01 Defywire, Inc. Method and apparatus for just-in-time provisioning application-related information at a communication device
US7127480B2 (en) 2003-12-04 2006-10-24 International Business Machines Corporation System, method and program for backing up a computer program
US7296273B2 (en) * 2003-12-04 2007-11-13 International Business Machines Corporation System, method and program tool to reset an application
US7627871B2 (en) * 2004-06-14 2009-12-01 Alcatel-Lucent Usa Inc. Instructing management support software of a first software component to set up a communication channel between the first software component and a second software component
FR2875319B1 (en) * 2004-09-16 2008-04-11 Renault Sas ON-BOARD SYSTEM AND CALCULATOR TO PUT UP DATA UNLOADING IN CASE OF STOPPING THE COMPUTER
CN107069970A (en) * 2017-05-24 2017-08-18 国网江西省电力公司电力科学研究院 A kind of miniature energy router apparatus based on open service platform
US11593085B1 (en) 2020-02-03 2023-02-28 Rapid7, Inc. Delta data collection technique for machine assessment
US11886413B1 (en) 2020-07-22 2024-01-30 Rapid7, Inc. Time-sliced approximate data structure for storing group statistics

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2203573A (en) 1987-04-02 1988-10-19 Ibm Data processing network with upgrading of files
JP2852381B2 (en) 1988-06-24 1999-02-03 富士通株式会社 IC card system simulator
FR2667419A1 (en) 1990-10-02 1992-04-03 Gemplus Card Int Memory-card application-program debugging process and debugging system
GB9208275D0 (en) 1992-04-15 1992-06-03 Int Computers Ltd Data management mechanism
US5805897A (en) * 1992-07-31 1998-09-08 International Business Machines Corporation System and method for remote software configuration and distribution
US5608909A (en) 1994-04-15 1997-03-04 Microsoft Corporation Method and system for caching presentation data of a source object in a presentation cache
JPH0844498A (en) 1994-07-29 1996-02-16 Hitachi Ltd Storage device with compressing function and computer system having the device
US5835721A (en) * 1995-08-21 1998-11-10 Apple Computer, Inc. Method and system for data transmission over a network link between computers with the ability to withstand temporary interruptions
JPH0962560A (en) 1995-08-30 1997-03-07 Fuji Xerox Co Ltd Database device
US6128771A (en) 1996-02-09 2000-10-03 Sun Microsystems, Inc. System and method for automatically modifying database access methods to insert database object handling instructions
GB2311390B (en) 1996-03-18 2000-03-22 Ibm Initial program load in data processing network
US5940074A (en) * 1996-06-03 1999-08-17 Webtv Networks, Inc. Remote upgrade of software over a network
US5974461A (en) * 1996-06-03 1999-10-26 Webtv Networks, Inc. Method for automatically regenerating information at a client system in the event of power or communication disruption between the client system and the server
US6049838A (en) * 1996-07-01 2000-04-11 Sun Microsystems, Inc. Persistent distributed capabilities
AU5595398A (en) 1996-12-03 1998-06-29 Strategic Analysis, Inc. Method and apparatus for formatting smart cards and card readers
US6049892C1 (en) * 1997-02-24 2002-06-04 Ethos Software Corp Process and apparatus for downloading data from a server computer to a client computer
US6161123A (en) * 1997-05-06 2000-12-12 Intermec Ip Corporation Providing reliable communication over an unreliable transport layer in a hand-held device using a persistent session
US6161145A (en) * 1997-05-08 2000-12-12 International Business Machines Corporation Updating server-related data at a client
US6061721A (en) 1997-10-06 2000-05-09 Sun Microsystems, Inc. Bean-based management system
EP0915419A3 (en) 1997-10-06 2003-11-12 Sun Microsystems, Inc. Remote object access
US5966702A (en) 1997-10-31 1999-10-12 Sun Microsystems, Inc. Method and apparatus for pre-processing and packaging class files
US5974454A (en) * 1997-11-14 1999-10-26 Microsoft Corporation Method and system for installing and updating program module components
US6202091B1 (en) * 1997-12-08 2001-03-13 Nortel Networks Limited Process and apparatus for initializing a computer from power up
US6385729B1 (en) * 1998-05-26 2002-05-07 Sun Microsystems, Inc. Secure token device access to services provided by an internet service provider (ISP)
US6237039B1 (en) * 1998-06-30 2001-05-22 Webtv Networks, Inc. Method and apparatus for downloading auxiliary data to a client from a network during client idle periods
US6314459B1 (en) * 1998-08-13 2001-11-06 U.S. Philips Corporation Home-network autoconfiguration
US6449642B2 (en) * 1998-09-15 2002-09-10 Microsoft Corporation Method and system for integrating a client computer into a computer network
US6499137B1 (en) * 1998-10-02 2002-12-24 Microsoft Corporation Reversible load-time dynamic linking
US6247126B1 (en) * 1999-01-25 2001-06-12 Dell Usa, L.P. Recoverable software installation process and apparatus for a computer system
US6347331B1 (en) * 1999-04-26 2002-02-12 International Business Machines Corporation Method and apparatus to update a windows registry from a hetrogeneous server
US6510550B1 (en) * 1999-05-12 2003-01-21 Intel Corporation Method and apparatus for providing intermittent connectivity support in a computer application

Also Published As

Publication number Publication date
AU5381800A (en) 2001-01-02
WO2000077679A3 (en) 2001-10-04
WO2000077679A2 (en) 2000-12-21
US6490616B1 (en) 2002-12-03
US20030046442A1 (en) 2003-03-06

Similar Documents

Publication Publication Date Title
US6490616B1 (en) Method and apparatus for incremental download from server to client
US6083279A (en) Platform independent technique for transferring software programs over a network
US7698390B1 (en) Pluggable device specific components and interfaces supported by cluster devices and systems and methods for implementing the same
US6314567B1 (en) Apparatus and method for transferring state data when performing on-line replacement of a running program code and data
US6732267B1 (en) System and method for performing remote BIOS updates
US7366824B2 (en) Updating electronic files using byte-level file differencing and updating algorithms
US7921433B2 (en) Method and system for providing version control of parameters in a command-based API using java serialization
RU2302089C2 (en) System for updating software in wireless devices
US8392906B2 (en) Enabling parallel websphere runtime versions
US7370322B1 (en) Method and apparatus for performing online application upgrades in a java platform
US6912569B1 (en) Method and apparatus for migration of managed application state for a Java based application
US20070169099A1 (en) Firmware update system for facilitating firmware update in mobile handset
US20060242395A1 (en) Operating system boot from network location
US20080301425A1 (en) Method And System To Support ISCSI Boot Through Management Controllers
EP1366411A2 (en) Local transaction management
KR20010103748A (en) Techniques for permitting access across a context barrier on a small footprint device using an entry point object
US6687799B2 (en) Expedited memory dumping and reloading of computer processors
EP1579341A2 (en) Method and apparatus for shared libraries on mobile devices
US7143405B2 (en) Methods and arrangements for managing devices
WO2002075531A1 (en) Method for loading and executing an application in an embedded environment
JP5395108B2 (en) Apparatus and method for upgrading firmware in embedded systems
US8484616B1 (en) Universal module model
EP1859595B1 (en) Asynchronous network stack operation in a pre boot environment
CN113661482A (en) Transmission of process state and/or components in a computing environment
EP1384149A2 (en) Method and apparatus for implementing state machines as enterprise javabean components

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
AK Designated states

Kind code of ref document: C2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1-10, DESCRIPTION, REPLACED BY NEW PAGES 1-10; PAGES 11-14, CLAIMS, REPLACED BY NEW PAGES 11-14; PAGES 1/7-7/7, DRAWINGS, REPLACED BY NEW PAGES 1/7-7/7; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

NENP Non-entry into the national phase

Ref country code: JP