US20060225058A1 - Method and system for accessing and launching a java based applet as a locally installed application - Google Patents
Method and system for accessing and launching a java based applet as a locally installed application Download PDFInfo
- Publication number
- US20060225058A1 US20060225058A1 US11/099,395 US9939505A US2006225058A1 US 20060225058 A1 US20060225058 A1 US 20060225058A1 US 9939505 A US9939505 A US 9939505A US 2006225058 A1 US2006225058 A1 US 2006225058A1
- Authority
- US
- United States
- Prior art keywords
- embedded application
- checksum value
- remote device
- loader
- checksum
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/44536—Selecting among different versions
Definitions
- Embodiments of the present invention relate to the field of Java-based embedded device management applications. More particularly, embodiments of the present invention relate generally to accessing and launching a locally stored version of the Java-based embedded device management applications from a client workstation.
- An embedded application e.g., device management application
- IP Internet protocol
- the advantages of having an embedded application is that a user that is Web-enabled can access the embedded application and interact with the embedded application without having to load or install anything onto the client workstation. As a result, via any workstation that is Web-enabled, a user can access and interact with the embedded application.
- FIG. 1 is a flow diagram of the flow of information through a conventional network 100 that is capable of interfacing with the networking device 110 while ensuring that a compatible version of the embedded application is used to interface with the networking device 110 .
- an applet java based technology
- the loader 115 and the embedded application that is used to interface with the networking device 110 are stored on the networking device.
- the loader is used to launch the embedded application on a client workstation 130 .
- the loader 115 is installed into a browser window through a java plug-in (e.g., java virtual machine) located on the client workstation 130 .
- the loader 115 executes in the client workstation 130 via the browser window 140 in order to pull the embedded application from the networking device 110 to the client workstation 130 . That is, the loader 115 extracts the embedded application 125 for use on the client workstation 130 .
- client workstation 130 implements the embedded application as a Java applet, that is running within the Java virtual machine (JVM) of the browser 140 on the client workstation 130 .
- JVM Java virtual machine
- the user can access the application through another window 140 .
- the user can interface with the networking device 110 using the java based embedded application, for example to configure the networking device 110 .
- the browser interface is slow and inefficient. That is, the embedded application must be downloaded each time the client wants to interface with the networking device, which is an inefficient use of resources. Also, if two networking devices use the same version of an embedded application, two separate but identical copies of the embedded application are downloaded. Additionally, if the client is connecting to the networking device 110 through a secure socket layer (SSL) numerous dialog boxes are presented in order to guide the user through the downloading process. However, these dialog interfaces are also slow and cumbersome from the user perspective. Furthermore, since the embedded application is stored on the networking device 110 , the user is limited in terms of runtime parameters, such as memory allocated to the embedded application, etc.
- SSL secure socket layer
- various embodiments of the present invention disclose a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application.
- Embodiments of the present invention are capable of automatically upgrading the version of the embedded application that is locally stored to match the version of the embedded application stored on the remote device.
- embodiments of the present invention provide for the ability to launch directly from the client workstation, thereby bypassing a browser interface and effectively increasing the speed and efficiency when executing the java based embedded application that interfaces with the remote device.
- a method for launching an interface with a remotely located electronic device. That is, the present embodiment is capable of accessing and launching a java based applet as a locally installed application.
- the present embodiment begins by launching a loader that is locally installed.
- the loader is associated with an embedded application stored on a remote device.
- the present embodiment establishes communication with the remote device in order to access a first checksum value of the embedded application.
- the first checksum value is stored on the remote device along with the embedded application. Thereafter, the first checksum value is compared against a second checksum value of a locally stored version of the embedded application.
- the locally stored version of the embedded application is launched when the first checksum value matches the second checksum value.
- FIG. 1 is a block diagram of a conventional system that launches and executes a java based embedded application through a browser on a client workstation.
- FIG. 2 is a block diagram of an electronic device that is capable of accessing and launching a java based embedded application of a remote device as a locally installed application, in accordance with one embodiment of the present invention.
- FIG. 3 is a flow chart illustrating steps in a computer implemented method for accessing and launching a java based embedded application as a locally installed application in order to provide a local interface with the remote device, in accordance with one embodiment of the present invention.
- FIG. 4 is a flow diagram illustrating the flow of information when installing the loader and a locally stored version of an embedded application, in accordance with one embodiment of the present invention.
- FIG. 5 is a block diagram illustrating a client workstation that is capable of storing embedded applications on a per application basis, in accordance with one embodiment of the present invention.
- various embodiments of the present invention disclose a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application.
- Embodiments of the present invention are capable providing the advantages of both a java based applet model framework and an application model framework to access and launch an embedded application as a locally installed application.
- embodiments of the present invention are able to access the launcher through a browser interface, so that no other software is needed to initially load of automatically upgrading the version of the embedded application that is locally stored to match the version of the embedded application stored on the remote device.
- embodiments of the present invention provide for the ability to launch directly from the client workstation, thereby bypassing a browser interface and effectively increasing the speed and efficiency when executing the java based embedded application that interfaces with the remote device.
- FIG. 2 portions of the present invention are comprised of computer-readable and computer-executable instructions which reside, for example, in computer-readable media of an electronic system that are capable of accessing networked devices, such as, a server computer, mainframe, networked computer, workstation, hub, router, switch, firewall, access server, and the like.
- FIG. 2 is a block diagram of interior components of an exemplary electronic system 200 , upon which embodiments of the present invention may be implemented.
- Exemplary electronic system 200 includes an address/data bus 220 for communicating information, a central processor 201 coupled with the bus 220 for processing information and instructions, a volatile memory 202 (e.g., random access memory (RAM), static RAM dynamic RAM, etc.) coupled with the bus 220 for storing information and instructions for the central processor 201 , and a non-volatile memory 203 (e.g., read only memory (ROM), programmable ROM, flash memory, EPROM, EEPROM, etc.) coupled to the bus 220 for storing static information and instructions for the processor 201 .
- RAM random access memory
- EEPROM electrically erasable programmable ROM
- Exemplary electronic system 200 also includes an optional data storage device 204 (e.g., cache memory, memory card, hard drive, etc.) coupled with the bus 220 for storing information and instructions.
- Data storage device 204 is removable, in one embodiment.
- a network interface 208 e.g., signal input/output device
- network interface 208 enables the central processor unit 201 to communicate with or monitor other electronic systems (e.g., networked devices) or coupled to a communication network.
- FIG. 3 and the flow diagrams of FIGS. 4 and 5 describe the processes used for accessing and launching a java based embedded application as a locally installed application by a client workstation, in accordance with embodiments of the present invention.
- Accessing the embedded application as a locally installed application allows for a more efficient use of the embedded application since a browser interface is bypassed.
- embodiments of the present invention are capable of automatically upgrading the locally stored version of the embedded application to be compatible with the embedded application used to interface with the networking device.
- a flow chart 300 is disclosed illustrating steps in a computer implemented method for accessing and launching the embedded application that is locally stored on a client workstation, in accordance with one embodiment of the present invention.
- the method as disclosed in the present embodiment avoids the slow downloading of the application code from the remote device, as in conventional techniques. That is, the user is able to launch the application much quicker, since it is installed locally at the client workstation, without going through a browser interface.
- the present embodiment launches a loader.
- the loader is used to invoke a java based embedded application with a remote electronic device.
- the present embodiment launches a loader that is locally installed, for example on a client workstation.
- the loader is used to invoke the java based embedded application that is locally installed on the client workstation. Since the loader is installed on the client workstation, the loader can be executed without the use of a browser interface.
- the core embedded application is stored on the remote device and is used to interface with the remote electronic device. That is, the remote device is associated with and is the source of an embedded application. As such, the embedded application stored on the remote device is the default version of the embedded application used to interface with the embedded device.
- the embedded application can be a device management application that allows a user to interact with and configure the device.
- the present embodiment selects the remote device for interfacing. More specifically, the launcher is able to launch a particular embedded application of varying versions that are used to interface with one or more remote devices. As such, a remote device is selected by the present embodiment in order to determine which version of the embedded application is compatible with the particular remote device that is selected
- the present embodiment establishes communication with the remote device.
- Communication between the client workstation and the remote device is necessary to determine which version of the embedded application is stored on the remote device. That is, the version of the embedded application is the version used to interface with the remote device.
- a checksum value of the embedded application is used to determine the version of the embedded application stored on the remote device. As such, the present embodiment establishes communication to access a first checksum value of the embedded application that is stored on the remote device at 320 .
- the MD-5 hash algorithm is applied on the embedded application stored on the remote device to determine the checksum value associated with the embedded application used to interface with the remote device. As such, any embedded application having the same checksum value can be used to interface with the remote device, and is effectively running the same version of the embedded application.
- the MD-5 hash algorithm is used to calculate a 16 byte checksum in one embodiment, for example. In another embodiment, a 128 bit value is calculated for the checksum. In still other embodiments other bit values can be used to determine the checksum.
- the present embodiment accesses the second checksum value of the locally stored version of the embedded application. In this way, the present embodiment can determine if the version of the locally stored embedded application is the same or is compatible with the version of the embedded application stored on the remote device.
- the present embodiment compares the checksum values. More particularly, the present embodiment compares the first checksum value of the embedded application against the second checksum value of the locally stored version of the embedded application.
- the present embodiment determines if the first checksum value matches the second checksum value. That is, the present embodiment determines if the first checksum value of the embedded application stored at the remote device matches (e.g., is identical) to the second checksum value of the locally stored version of the embedded application.
- the present embodiment proceeds to 355 to launch the locally stored version of the embedded application. That is, when the first checksum value of the embedded application matches the second checksum value, then the locally stored version of the embedded application is launched. That is, the locally stored version of the embedded application can be used to interface with the remote device since they are of the same version.
- the present embodiment determines if there are any other locally stored versions of the embedded application. If there are more locally stored versions of the embedded application, then the present embodiment locates another version and then returns to 325 to do the checksum accessing and comparison.
- the present embodiment compares the first checksum value of the embedded application with a plurality of checksum values of a plurality of locally stored versions of the embedded application to determine if one of the plurality of checksum values, as the second checksum value, matches the first checksum value. If there is a match, then the corresponding version of the locally stored embedded application can be used to interface with the remote device.
- the present embodiment proceeds to 345 to automatically upgrade the embedded application on the client workstation. That is, the present embodiment determines that the client workstation does not have a compatible version of the embedded application stored locally on the client workstation.
- the present embodiment continues by retrieving the java based applet from the remote device for implementing the embedded application. That is, in the present case, a Java applet is transferred from the remote device to the client workstation.
- the embedded application is included within the Java applet.
- the same software code base can be used for both the applet and the embedded application which makes the software development process much smoother.
- the present embodiment is capable of downloading the embedded application using any file transfer protocol (e.g., HTTP, HTTPS, etc.) to pull the embedded application stored on the remote device and install the embedded application locally on the client workstation.
- the present embodiment stores the downloaded embedded application as the locally stored version of the embedded application.
- the embedded application is stored in the memory (e.g., hard drive) of a client workstation.
- the present embodiment then proceeds to 355 to launch the locally stored version of the embedded application to interface with the remote device.
- the present embodiment uses the installation wizard 450 to install the loader into the memory 460 (e.g., hard drive) of the client workstation 430 . Thereafter, the loader 415 can be launched directly on the client workstation without the use of the browser interface 435 .
- the memory 460 e.g., hard drive
- FIG. 4 also illustrates the flow of information when installing the embedded application 420 from the networking device 410 onto the client workstation 430 , in accordance with one embodiment of the present invention.
- the flow diagram 400 is illustrative of the operations performed at 345 and 350 of FIG. 3 .
- the embedded application can be executed through a window 427 directly and without the use of the browser interface 435 .
- the user can execute the application through window 427 to interface with the networking device 410 (e.g., for configuration purposes).
- the client workstation 520 is able to interface with three networking devices, network device 510 , networking device 512 , and networking device 514 .
- Each of the networking devices 510 , 512 , and 514 have the same embedded application A that is used to interface with the devices (e.g., for configuration purposes).
- the checksum value of the embedded application that is stored on the networking device is used to identify the version.
- the networking device 510 has a version indicated by the checksum 05F3A4.
- the networking device 512 has a version indicated by the same checksum 05F3A4.
- the same version of the embedded application (version 05F3A4) is used to interface with both the networking device 510 and 512 .
- the client workstation 520 includes a loader 530 that launches the embedded application A for all networking deices that use the embedded application A as an interface. That is, the loader 530 is used only to launch all versions of the embedded application A. A different loader is used to launch a different embedded application (e.g., embedded application B).
- the loader is invoked when the shortcut to that loader is invoked. That is, when the user wants to access the embedded application A to interface with either the networking device 510 , 512 , or 514 , the user can click the desktop shortcut for the loader 530 . As such, the loader 530 is executed to determine if the client workstation has a correct version of the embedded application stored in memory 580 for a particular networking device.
- the loader 530 communicates with that networking device to determine which version of the embedded application is proper to interface with that networking device.
- the communications module 540 is used to establishing communication with the selected networking device.
- the user provides proper authentication credentials (e.g., IP address, username, and password) to connect to the proper networking device 510 , 512 , or 514 .
- the retriever 550 accesses the proper checksum value that identifies the version of the embedded application A for the selected networking device. That is, the retriever 550 accesses the first checksum value of the embedded application A that is stored on selected networking device. More particularly, the retriever 550 connects to the selected networking device and accesses the checksum. For example, the retriever accesses a 128 bit MD5 hash value based on the version of the embedded application stored on the selected networking device.
- the comparator 560 will compare the first checksum of the embedded application A stored on the selected networking device against the second checksum of the locally stored version of the embedded application A. That is, if the same hash value version of the embedded application is installed locally on the client workstation 520 , then the present embodiment is able to launch the locally stored version of the embedded application using the launcher 570 . This occurs when the first checksum value matches the second checksum value.
- the communication module would establish communication (e.g. via HTTP, HTTPS, or any suitable communication protocol) between the client workstation 520 and the networking device 510 .
- the retriever 550 accesses the checksum of the embedded application A.
- the checksum is 05F3A4.
- the checksum is in the header of the embedded application A stored on the networking device 510 .
- the comparator 560 accesses the checksum of the locally stored version of the embedded application A.
- the comparator accesses a file name of the locally stored version of the embedded application. That is, the filename is the checksum of the locally stored embedded application. More particularly, when the embedded application is stored locally on the client workstation 520 , the locally stored application is stored using a filename that is the checksum of that embedded application.
- the communication module 540 establishes communication (e.g. via HTTP, HTTPS, or any suitable communication protocol) between the client workstation 520 and the networking device 512 .
- the retriever 550 accesses the checksum of the embedded application A.
- the checksum is also 05F3A4.
- the checksum is in the header of the embedded application A stored on the networking device 512 .
- the comparator 560 accesses the checksum of the locally stored version of the embedded application A.
- the comparator accesses a file name of the locally stored version of the embedded application.
- the client workstation 520 has stored an embedded application A with the file name 05F3A4, which is also the checksum. Since the embedded application A with filename 05F3A4 has already been launched and is servicing networking device 510 , the application version 05F3A4 need not be launched again. That is, the same embedded application is used to interface with both the networking device 510 and the networking device 512 .
- Embodiments of the present invention a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application are described. While the invention is described in conjunction with the preferred embodiments, it is understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be recognized by one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present invention.
Abstract
Description
- 1. Field of the Invention
- Embodiments of the present invention relate to the field of Java-based embedded device management applications. More particularly, embodiments of the present invention relate generally to accessing and launching a locally stored version of the Java-based embedded device management applications from a client workstation.
- 2. Related Art
- An embedded application (e.g., device management application) is an application which neither needs to be explicitly installed on a client workstation, nor actually installs pieces on a client workstation. The embedded application comes with the device and can be accessed through some network (e.g., the Internet). As soon as there is Internet protocol (IP) connectivity between a client workstation and the device, a user can bring up the embedded application within a browser on the client workstation.
- The advantages of having an embedded application is that a user that is Web-enabled can access the embedded application and interact with the embedded application without having to load or install anything onto the client workstation. As a result, via any workstation that is Web-enabled, a user can access and interact with the embedded application.
- Prior Art
FIG. 1 is a flow diagram of the flow of information through aconventional network 100 that is capable of interfacing with thenetworking device 110 while ensuring that a compatible version of the embedded application is used to interface with thenetworking device 110. In theconventional network 100, an applet (java based technology) allows the client to run the version of the embedded application that is compatible with thenetworking device 110. - More specifically, the
loader 115 and the embedded application that is used to interface with thenetworking device 110 are stored on the networking device. The loader is used to launch the embedded application on aclient workstation 130. - As shown in Prior Art
FIG. 1 , in step 1, theloader 115 is installed into a browser window through a java plug-in (e.g., java virtual machine) located on theclient workstation 130. Insteps loader 115 executes in theclient workstation 130 via thebrowser window 140 in order to pull the embedded application from thenetworking device 110 to theclient workstation 130. That is, theloader 115 extracts the embeddedapplication 125 for use on theclient workstation 130. More specifically,client workstation 130 implements the embedded application as a Java applet, that is running within the Java virtual machine (JVM) of thebrowser 140 on theclient workstation 130. As such, the user can access the application through anotherwindow 140. In this way, throughstep 4, the user can interface with thenetworking device 110 using the java based embedded application, for example to configure thenetworking device 110. - While the use of the java based applet through the
browser window 140 ensures that a compatible version of the embedded application is used to interface with the networking device, the browser interface is slow and inefficient. That is, the embedded application must be downloaded each time the client wants to interface with the networking device, which is an inefficient use of resources. Also, if two networking devices use the same version of an embedded application, two separate but identical copies of the embedded application are downloaded. Additionally, if the client is connecting to thenetworking device 110 through a secure socket layer (SSL) numerous dialog boxes are presented in order to guide the user through the downloading process. However, these dialog interfaces are also slow and cumbersome from the user perspective. Furthermore, since the embedded application is stored on thenetworking device 110, the user is limited in terms of runtime parameters, such as memory allocated to the embedded application, etc. - Accordingly, various embodiments of the present invention disclose a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application. Embodiments of the present invention are capable of automatically upgrading the version of the embedded application that is locally stored to match the version of the embedded application stored on the remote device. In addition, embodiments of the present invention provide for the ability to launch directly from the client workstation, thereby bypassing a browser interface and effectively increasing the speed and efficiency when executing the java based embedded application that interfaces with the remote device.
- Specifically, in one embodiment, a method is disclosed for launching an interface with a remotely located electronic device. That is, the present embodiment is capable of accessing and launching a java based applet as a locally installed application. The present embodiment begins by launching a loader that is locally installed. The loader is associated with an embedded application stored on a remote device. The present embodiment establishes communication with the remote device in order to access a first checksum value of the embedded application. The first checksum value is stored on the remote device along with the embedded application. Thereafter, the first checksum value is compared against a second checksum value of a locally stored version of the embedded application. The locally stored version of the embedded application is launched when the first checksum value matches the second checksum value.
- Prior Art
FIG. 1 is a block diagram of a conventional system that launches and executes a java based embedded application through a browser on a client workstation. -
FIG. 2 is a block diagram of an electronic device that is capable of accessing and launching a java based embedded application of a remote device as a locally installed application, in accordance with one embodiment of the present invention. -
FIG. 3 is a flow chart illustrating steps in a computer implemented method for accessing and launching a java based embedded application as a locally installed application in order to provide a local interface with the remote device, in accordance with one embodiment of the present invention. -
FIG. 4 is a flow diagram illustrating the flow of information when installing the loader and a locally stored version of an embedded application, in accordance with one embodiment of the present invention. -
FIG. 5 is a block diagram illustrating a client workstation that is capable of storing embedded applications on a per application basis, in accordance with one embodiment of the present invention. - Reference will now be made in detail to the preferred embodiments of the present invention, a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application, examples of which are illustrated in the accompanying drawings.
- Accordingly, various embodiments of the present invention disclose a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application. Embodiments of the present invention are capable providing the advantages of both a java based applet model framework and an application model framework to access and launch an embedded application as a locally installed application. For instance, embodiments of the present invention are able to access the launcher through a browser interface, so that no other software is needed to initially load of automatically upgrading the version of the embedded application that is locally stored to match the version of the embedded application stored on the remote device. In addition, embodiments of the present invention provide for the ability to launch directly from the client workstation, thereby bypassing a browser interface and effectively increasing the speed and efficiency when executing the java based embedded application that interfaces with the remote device.
- Notation and Nomenclature
- Referring now to
FIG. 2 , portions of the present invention are comprised of computer-readable and computer-executable instructions which reside, for example, in computer-readable media of an electronic system that are capable of accessing networked devices, such as, a server computer, mainframe, networked computer, workstation, hub, router, switch, firewall, access server, and the like.FIG. 2 is a block diagram of interior components of an exemplaryelectronic system 200, upon which embodiments of the present invention may be implemented. - Exemplary
electronic system 200 includes an address/data bus 220 for communicating information, acentral processor 201 coupled with the bus 220 for processing information and instructions, a volatile memory 202 (e.g., random access memory (RAM), static RAM dynamic RAM, etc.) coupled with the bus 220 for storing information and instructions for thecentral processor 201, and a non-volatile memory 203 (e.g., read only memory (ROM), programmable ROM, flash memory, EPROM, EEPROM, etc.) coupled to the bus 220 for storing static information and instructions for theprocessor 201. - Exemplary
electronic system 200 also includes an optional data storage device 204 (e.g., cache memory, memory card, hard drive, etc.) coupled with the bus 220 for storing information and instructions.Data storage device 204 is removable, in one embodiment. With reference still toFIG. 2 , a network interface 208 (e.g., signal input/output device) is provided which is coupled to bus 220 for providing a communication link betweenelectronic system 200 and a network environment. Assuch network interface 208 enables thecentral processor unit 201 to communicate with or monitor other electronic systems (e.g., networked devices) or coupled to a communication network. - Some portions of the detailed descriptions which follow are presented in terms of procedures, steps, logic blocks, processing, and other symbolic representations of operations on data bits that can be performed on computer memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. A procedure, computer executed step, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
- It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “launching,” “accessing,” “comparing,” “executing,” “storing,” “downloading,” or the like, refer to the action and processes of a computer system, or similar electronic computing device, including an embedded system, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
- Method and System for Interfacing with Networked Devices
- The flow chart of
FIG. 3 and the flow diagrams ofFIGS. 4 and 5 describe the processes used for accessing and launching a java based embedded application as a locally installed application by a client workstation, in accordance with embodiments of the present invention. Accessing the embedded application as a locally installed application allows for a more efficient use of the embedded application since a browser interface is bypassed. In addition, embodiments of the present invention are capable of automatically upgrading the locally stored version of the embedded application to be compatible with the embedded application used to interface with the networking device. - Referring now to
FIG. 3 , aflow chart 300 is disclosed illustrating steps in a computer implemented method for accessing and launching the embedded application that is locally stored on a client workstation, in accordance with one embodiment of the present invention. The method as disclosed in the present embodiment avoids the slow downloading of the application code from the remote device, as in conventional techniques. That is, the user is able to launch the application much quicker, since it is installed locally at the client workstation, without going through a browser interface. - At 310, the present embodiment launches a loader. The loader is used to invoke a java based embedded application with a remote electronic device. In particular, the present embodiment launches a loader that is locally installed, for example on a client workstation. As such, the loader is used to invoke the java based embedded application that is locally installed on the client workstation. Since the loader is installed on the client workstation, the loader can be executed without the use of a browser interface.
- The core embedded application is stored on the remote device and is used to interface with the remote electronic device. That is, the remote device is associated with and is the source of an embedded application. As such, the embedded application stored on the remote device is the default version of the embedded application used to interface with the embedded device. For example, the embedded application can be a device management application that allows a user to interact with and configure the device.
- At 315, the present embodiment selects the remote device for interfacing. More specifically, the launcher is able to launch a particular embedded application of varying versions that are used to interface with one or more remote devices. As such, a remote device is selected by the present embodiment in order to determine which version of the embedded application is compatible with the particular remote device that is selected
- In particular, the present embodiment establishes communication with the remote device. Communication between the client workstation and the remote device is necessary to determine which version of the embedded application is stored on the remote device. That is, the version of the embedded application is the version used to interface with the remote device.
- In one embodiment, a checksum value of the embedded application is used to determine the version of the embedded application stored on the remote device. As such, the present embodiment establishes communication to access a first checksum value of the embedded application that is stored on the remote device at 320.
- In one embodiment, the MD-5 hash algorithm is applied on the embedded application stored on the remote device to determine the checksum value associated with the embedded application used to interface with the remote device. As such, any embedded application having the same checksum value can be used to interface with the remote device, and is effectively running the same version of the embedded application.
- The MD-5 hash algorithm is used to calculate a 16 byte checksum in one embodiment, for example. In another embodiment, a 128 bit value is calculated for the checksum. In still other embodiments other bit values can be used to determine the checksum.
- At 325, the present embodiment accesses the second checksum value of the locally stored version of the embedded application. In this way, the present embodiment can determine if the version of the locally stored embedded application is the same or is compatible with the version of the embedded application stored on the remote device.
- As such, at 330, the present embodiment compares the checksum values. More particularly, the present embodiment compares the first checksum value of the embedded application against the second checksum value of the locally stored version of the embedded application.
- At 335, the present embodiment determines if the first checksum value matches the second checksum value. That is, the present embodiment determines if the first checksum value of the embedded application stored at the remote device matches (e.g., is identical) to the second checksum value of the locally stored version of the embedded application.
- If the checksum values match, then the present embodiment proceeds to 355 to launch the locally stored version of the embedded application. That is, when the first checksum value of the embedded application matches the second checksum value, then the locally stored version of the embedded application is launched. That is, the locally stored version of the embedded application can be used to interface with the remote device since they are of the same version.
- On the other hand, if the checksum values do not match, then the present embodiment proceeds to 340. At 340, the present embodiment determines if there are any other locally stored versions of the embedded application. If there are more locally stored versions of the embedded application, then the present embodiment locates another version and then returns to 325 to do the checksum accessing and comparison.
- More specifically, the present embodiment compares the first checksum value of the embedded application with a plurality of checksum values of a plurality of locally stored versions of the embedded application to determine if one of the plurality of checksum values, as the second checksum value, matches the first checksum value. If there is a match, then the corresponding version of the locally stored embedded application can be used to interface with the remote device.
- However, if there are no other locally stored versions of the embedded application, then the present embodiment proceeds to 345 to automatically upgrade the embedded application on the client workstation. That is, the present embodiment determines that the client workstation does not have a compatible version of the embedded application stored locally on the client workstation.
- As such, the present embodiment continues by retrieving the java based applet from the remote device for implementing the embedded application. That is, in the present case, a Java applet is transferred from the remote device to the client workstation. In one embodiment, the embedded application is included within the Java applet. Moreover, in one embodiment the same software code base can be used for both the applet and the embedded application which makes the software development process much smoother. As a result, the present embodiment is capable of downloading the embedded application using any file transfer protocol (e.g., HTTP, HTTPS, etc.) to pull the embedded application stored on the remote device and install the embedded application locally on the client workstation.
- As such, at 350 the present embodiment stores the downloaded embedded application as the locally stored version of the embedded application. For example, the embedded application is stored in the memory (e.g., hard drive) of a client workstation.
- After the embedded application is downloaded and stored as a locally stored versions of the embedded application, the present embodiment then proceeds to 355 to launch the locally stored version of the embedded application to interface with the remote device.
-
FIG. 4 is a flow diagram 400 illustrating the flow of information between thenetworking device 410 and theclient workstation 430 when accessing and installing the embedded application, in accordance with one embodiment of the present invention. - In one embodiment, the
loader 415 is installed on theclient workstation 430. That is, when the embedded application is executed for the first time, theloader 415 is installed on theclient workstation 430 through abrowser interface 435. In particular, the present embodiment begins by establishing communication with thenetworking device 410, as is shown in path 1. The communication is established through abrowser interface 435 that is Java-enabled on theclient workstation 430. - As such, for example, at the
client workstation 430, a user can interact with and access thenetworking device 410 through thebrowser interface 435 in order to install theloader 415 onto theclient workstation 430. As shown bypath 2, the present embodiment uses theinstallation wizard 450 to prompt the user for installation of theloader 415 from the networking device. - After installation of the
loader 415 by theinstallation wizard 450, the present embodiment uses theinstallation wizard 450 to install the loader into the memory 460 (e.g., hard drive) of theclient workstation 430. Thereafter, theloader 415 can be launched directly on the client workstation without the use of thebrowser interface 435. -
FIG. 4 also illustrates the flow of information when installing the embeddedapplication 420 from thenetworking device 410 onto theclient workstation 430, in accordance with one embodiment of the present invention. For instance, the flow diagram 400 is illustrative of the operations performed at 345 and 350 ofFIG. 3 . - In the present embodiment, the
loader 415 is executed independently of thebrowser interface 435. That is, the loader can be launched directly from the client workstation (e.g., through invoking an icon associated with the loader 415). If the present embodiment determines that the present embodiment does not have the proper version of the embedded application or does not have the embedded application locally stored, then the loader is able to directly communicate with thenetworking device 410 as shown inpath 3 ofFIG. 4 to access the embeddedapplication 420 that is stored on thenetworking device 410. As shown inFIG. 4 , the embedded application is typically compressed to utilize memory resources on the networking device efficiently. - The present embodiment then downloads the embedded
application 420 from thenetworking device 410 to theclient workstation 430. That is, the present embodiment, overpath 4 downloads and extracts the embedded application for storing on theclient workstation 430 inmemory 460. As such, the present embodiment is capable of providing a locally stored version of the embedded application on theclient workstation 430. - Thereafter, the embedded application can be executed through a
window 427 directly and without the use of thebrowser interface 435. As such, the user can execute the application throughwindow 427 to interface with the networking device 410 (e.g., for configuration purposes). -
FIG. 5 is a flow diagram 500 illustrating the per-application function of the loading capability of the client workstation 520, in accordance with one embodiment of the present invention. The advantage of the per-application function of the present embodiment is that one copy of a particular version of the embedded application (e.g., embedded application A) need be stored on the client workstation 520. As such, the single copy of the particular version can be used to interface with all networking devices using that particular version as an interface (e.g., configuration interface). This is a distinct advantage over the per-device function of conventional loading systems where each embedded application must be downloaded for every networking device in a one-to-one relationship. That is, even though two networking devices use the same version of an embedded application as an interface, two separate copies of the same embedded application need to be downloaded to the client workstation 520, which is a waste of resources. - As shown in
FIG. 5 , the client workstation 520 is able to interface with three networking devices,network device 510,networking device 512, andnetworking device 514. Each of thenetworking devices - However, different versions of the embedded application A are used for interfacing. In one embodiment, the checksum value of the embedded application that is stored on the networking device is used to identify the version. For example, the
networking device 510 has a version indicated by the checksum 05F3A4. Thenetworking device 512 has a version indicated by the same checksum 05F3A4. As such, the same version of the embedded application (version 05F3A4) is used to interface with both thenetworking device - On the other hand, the
networking device 514 has a version indicated by a different checksum 638D25. Although the embedded application is the same (e.g., embedded application A), the version is different. As such, only the version 638D25 can be used by the client workstation to interface with thenetworking device 514. - The client workstation 520 includes a
loader 530 that launches the embedded application A for all networking deices that use the embedded application A as an interface. That is, theloader 530 is used only to launch all versions of the embedded application A. A different loader is used to launch a different embedded application (e.g., embedded application B). - In one embodiment, the loader is invoked when the shortcut to that loader is invoked. That is, when the user wants to access the embedded application A to interface with either the
networking device loader 530. As such, theloader 530 is executed to determine if the client workstation has a correct version of the embedded application stored inmemory 580 for a particular networking device. - Once the networking device is selected, the
loader 530 communicates with that networking device to determine which version of the embedded application is proper to interface with that networking device. For example, thecommunications module 540 is used to establishing communication with the selected networking device. In particular, the user provides proper authentication credentials (e.g., IP address, username, and password) to connect to theproper networking device - The
retriever 550 accesses the proper checksum value that identifies the version of the embedded application A for the selected networking device. That is, theretriever 550 accesses the first checksum value of the embedded application A that is stored on selected networking device. More particularly, theretriever 550 connects to the selected networking device and accesses the checksum. For example, the retriever accesses a 128 bit MD5 hash value based on the version of the embedded application stored on the selected networking device. - The
comparator 560 will compare the first checksum of the embedded application A stored on the selected networking device against the second checksum of the locally stored version of the embedded application A. That is, if the same hash value version of the embedded application is installed locally on the client workstation 520, then the present embodiment is able to launch the locally stored version of the embedded application using thelauncher 570. This occurs when the first checksum value matches the second checksum value. - For example, in the case of the
networking device 510 the communication module would establish communication (e.g. via HTTP, HTTPS, or any suitable communication protocol) between the client workstation 520 and thenetworking device 510. Theretriever 550 accesses the checksum of the embedded application A. In this case, the checksum is 05F3A4. In one embodiment, the checksum is in the header of the embedded application A stored on thenetworking device 510. - Thereafter, the
comparator 560 accesses the checksum of the locally stored version of the embedded application A. In one embodiment, the comparator accesses a file name of the locally stored version of the embedded application. That is, the filename is the checksum of the locally stored embedded application. More particularly, when the embedded application is stored locally on the client workstation 520, the locally stored application is stored using a filename that is the checksum of that embedded application. - In this case, the client workstation 520 has stored an embedded application A with the file name 05F3A4, which is also the checksum. Since the checksum of the embedded application A stored on the
network device 510 matches the checksum of the locally stored version of the embedded application, the locally stored version (05F3A4) of the embedded application can be launched by thelauncher 570 to interface with thenetworking device 510. - Correspondingly, in the case of the
networking device 512 thecommunication module 540 establishes communication (e.g. via HTTP, HTTPS, or any suitable communication protocol) between the client workstation 520 and thenetworking device 512. Theretriever 550 accesses the checksum of the embedded application A. In this case, the checksum is also 05F3A4. As stated before, in one embodiment, the checksum is in the header of the embedded application A stored on thenetworking device 512. - Thereafter, the
comparator 560 accesses the checksum of the locally stored version of the embedded application A. In one embodiment, the comparator accesses a file name of the locally stored version of the embedded application. In this case, the client workstation 520 has stored an embedded application A with the file name 05F3A4, which is also the checksum. Since the embedded application A with filename 05F3A4 has already been launched and is servicingnetworking device 510, the application version 05F3A4 need not be launched again. That is, the same embedded application is used to interface with both thenetworking device 510 and thenetworking device 512. - Alternatively, in the case of the
networking device 514 thecommunication module 540 would establish communication (e.g. via HTTP, HTTPS, or any suitable communication protocol) between the client workstation 520 and thenetworking device 514. Theretriever 550 accesses the checksum of the embedded application A. In this case, the checksum is 638D25. In one embodiment, the checksum is in the header of the embedded application A stored on thenetworking device 514. - Thereafter, the
comparator 560 accesses the checksum of the locally stored version of the embedded application A. In one embodiment, the comparator accesses a file name of the locally stored version of the embedded application as previously described. In this case, the client workstation 520 does not have a locally stored version (638D25) of the embedded application. In this case, theloader 530 will download the new application version (638D25) from thenetworking device 514 and copy it into the local memory 580 (e.g., cache memory) as indicated by path 593, as previously described. That is, the embedded application A with filename 638D25, as indicated by the dotted outline, is stored locally inmemory 580 of the client workstation 520. Thereafter, the new version (638D25) is launched so that the user can interface with thenetworking device 514. - Accordingly, various embodiments of the present invention disclose a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application. Embodiments of the present invention are capable of automatically upgrading the version of the embedded application that is locally stored to match the version of the embedded application stored on the remote device. In addition, embodiments of the present invention provide for the ability to launch directly from the client workstation, thereby bypassing a browser interface and effectively increasing the speed and efficiently when executing the embedded application to interface with the remote device.
- While the methods of embodiments illustrated in
flow chart 300 show specific sequences and quantity of steps, the present invention is suitable to alternative embodiments. For example, not all the steps provided for in the method are required for the present invention. Furthermore, additional steps can be added to the steps presented in the present embodiment. Likewise, the sequences of steps can be modified depending upon the application. - Embodiments of the present invention, a method and system for accessing and launching a java based embedded application of a remote device (e.g., applet) as a locally installed application are described. While the invention is described in conjunction with the preferred embodiments, it is understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be recognized by one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present invention.
Claims (19)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/099,395 US7930693B2 (en) | 2005-04-04 | 2005-04-04 | Method and system for accessing and launching a java based applet as a locally installed application |
CN200680006413A CN100583038C (en) | 2005-04-04 | 2006-04-03 | Method, system and apparatus for launching an interface with an electronic device |
PCT/US2006/012307 WO2006107872A2 (en) | 2005-04-04 | 2006-04-03 | Method, system and apparatus for launching an interface with an electronic device |
EP06749161.3A EP1866758B1 (en) | 2005-04-04 | 2006-04-03 | Method, system and apparatus for launching an interface with an electronic device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/099,395 US7930693B2 (en) | 2005-04-04 | 2005-04-04 | Method and system for accessing and launching a java based applet as a locally installed application |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060225058A1 true US20060225058A1 (en) | 2006-10-05 |
US7930693B2 US7930693B2 (en) | 2011-04-19 |
Family
ID=37072141
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/099,395 Active 2026-04-11 US7930693B2 (en) | 2005-04-04 | 2005-04-04 | Method and system for accessing and launching a java based applet as a locally installed application |
Country Status (4)
Country | Link |
---|---|
US (1) | US7930693B2 (en) |
EP (1) | EP1866758B1 (en) |
CN (1) | CN100583038C (en) |
WO (1) | WO2006107872A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101976198A (en) * | 2010-10-27 | 2011-02-16 | 中兴通讯股份有限公司 | Method and device for controlling startup of application program in embedded system |
US20140210968A1 (en) * | 2013-01-31 | 2014-07-31 | iStoc Oy | Mobile test reader apparatus |
US9760113B2 (en) * | 2015-02-20 | 2017-09-12 | Sony Interactive Entertainment America Llc | Backward compatibility through use of spoof clock and fine grain frequency control |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120021835A1 (en) * | 2005-02-11 | 2012-01-26 | Iprd Labs Llc | Systems and methods for server based video gaming |
US7930693B2 (en) | 2005-04-04 | 2011-04-19 | Cisco Technology, Inc. | Method and system for accessing and launching a java based applet as a locally installed application |
CN101510161A (en) * | 2009-03-30 | 2009-08-19 | 北京中星微电子有限公司 | Bootstrap implementing method, apparatus and portable electronic apparatus |
CN101630267B (en) * | 2009-08-24 | 2012-09-05 | 中兴通讯股份有限公司 | Embedded system and control method thereof |
CN101795208B (en) * | 2010-01-21 | 2013-12-04 | 中兴通讯股份有限公司 | Method and system for synchronizing display information on rack diagram |
US9395970B2 (en) * | 2014-09-30 | 2016-07-19 | Sony Interactive Entertainment America Llc | Method and apparatus for providing a time period for starting an application |
Citations (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5155847A (en) * | 1988-08-03 | 1992-10-13 | Minicom Data Corporation | Method and apparatus for updating software at remote locations |
US5732275A (en) * | 1996-01-11 | 1998-03-24 | Apple Computer, Inc. | Method and apparatus for managing and automatically updating software programs |
US5764992A (en) * | 1995-06-06 | 1998-06-09 | Apple Computer, Inc. | Method and apparatus for automatic software replacement |
US5809287A (en) * | 1994-09-08 | 1998-09-15 | Compaq Computer Corporation | Automatic computer upgrading |
US5881236A (en) * | 1996-04-26 | 1999-03-09 | Hewlett-Packard Company | System for installation of software on a remote computer system over a network using checksums and password protection |
US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
US5923885A (en) * | 1996-10-31 | 1999-07-13 | Sun Microsystems, Inc. | Acquisition and operation of remotely loaded software using applet modification of browser software |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6139177A (en) * | 1996-12-03 | 2000-10-31 | Hewlett Packard Company | Device access and control using embedded web access functionality |
US20020002595A1 (en) * | 1998-09-01 | 2002-01-03 | Trevor Blumenau | Collection of images in web use reporting system |
US20020009552A1 (en) * | 1998-09-04 | 2002-01-24 | Dukeplanning & Co., Inc. | Method for repairing the coated surface of a vehicle |
US6381631B1 (en) * | 1999-06-03 | 2002-04-30 | Marimba, Inc. | Method and apparatus for controlling client computer systems |
US20020078262A1 (en) * | 2000-12-14 | 2002-06-20 | Curl Corporation | System and methods for providing compatibility across multiple versions of a software system |
US20020095522A1 (en) * | 2001-01-16 | 2002-07-18 | Hayko James Steven | System and method for automatic provision of an application |
US6430570B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java application manager for embedded device |
US6470494B1 (en) * | 1998-11-30 | 2002-10-22 | International Business Machines Corporation | Class loader |
US20020196460A1 (en) * | 2001-06-22 | 2002-12-26 | Parry Travis J. | Remote access to print job retention |
US20030009694A1 (en) * | 2001-02-25 | 2003-01-09 | Storymail, Inc. | Hardware architecture, operating system and network transport neutral system, method and computer program product for secure communications and messaging |
US6513158B1 (en) * | 1999-11-15 | 2003-01-28 | Espial Group Inc. | Method and apparatus for running multiple java applications simultaneously |
US20030041110A1 (en) * | 2000-07-28 | 2003-02-27 | Storymail, Inc. | System, Method and Structure for generating and using a compressed digital certificate |
US6546554B1 (en) * | 2000-01-21 | 2003-04-08 | Sun Microsystems, Inc. | Browser-independent and automatic apparatus and method for receiving, installing and launching applications from a browser on a client computer |
US20030084440A1 (en) * | 2001-10-26 | 2003-05-01 | George Lownes | Method of providing a code upgrade to a host device having a smart card interface |
US20030093508A1 (en) * | 2001-10-18 | 2003-05-15 | Seiko Epson Corporation | System for installing and launching network applications |
US20030208569A1 (en) * | 2000-04-14 | 2003-11-06 | O'brien Michael D | System and method for upgrading networked devices |
US6654954B1 (en) * | 1998-02-17 | 2003-11-25 | International Business Machines Corporation | Computer system, program product and method utilizing executable file with alternate program code attached as a file attribute |
US20040003034A1 (en) * | 2002-06-27 | 2004-01-01 | Weiyun Sun | Method for notification of varying versions of code between client and server |
US6675201B1 (en) * | 1999-03-03 | 2004-01-06 | Nokia Mobile Phones Ltd. | Method for downloading software from server to terminal |
US6675381B1 (en) * | 2000-01-20 | 2004-01-06 | Mitsubishi Denki Kabushiki Kaisha | Software-module dynamic loader, a software-module dynamic loading method and a medium storing the software-module dynamic loading method |
US20040054800A1 (en) * | 2002-08-28 | 2004-03-18 | Samir Shah | Content synchronization frameworks using dynamic attributes and file bundles for connected devices |
US20040092255A1 (en) * | 2002-11-12 | 2004-05-13 | De Ji | Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade |
US6826750B1 (en) * | 2000-03-23 | 2004-11-30 | International Business Machines Corporation | Method of automatically selecting program and data updates based upon versions |
US20040261069A1 (en) * | 2003-06-20 | 2004-12-23 | Sun Microsystems, Inc. | Dynamic loading of remote classes |
US20050102669A1 (en) * | 2003-10-15 | 2005-05-12 | Siemens Medical Solutions Usa, Inc. | Software installation file verification media and methods for medical equipment |
US20050114852A1 (en) * | 2000-11-17 | 2005-05-26 | Shao-Chun Chen | Tri-phase boot process in electronic devices |
US20050132179A1 (en) * | 2003-12-16 | 2005-06-16 | Microsoft Corporation | Applying custom software image updates to non-volatile storage in a failsafe manner |
US6910066B1 (en) * | 2001-03-05 | 2005-06-21 | Principal Financial Services, Inc. | System, method, and apparatus for applet caching |
US20050138037A1 (en) * | 2003-12-08 | 2005-06-23 | Samsung Electronics Co., Ltd. | Apparatus and method for sharing services on network |
US20050144514A1 (en) * | 2001-01-29 | 2005-06-30 | Ulrich Thomas R. | Dynamic redistribution of parity groups |
US20050240919A1 (en) * | 2004-04-27 | 2005-10-27 | Kim Kyoug I | Firmware update using memory card reader |
US20060004737A1 (en) * | 2004-07-02 | 2006-01-05 | Grzonka Michael T | Computer virus protection for automated pharmaceutical processes |
US20060075004A1 (en) * | 2004-10-04 | 2006-04-06 | Stakutis Christopher J | Method, system, and program for replicating a file |
US20060130041A1 (en) * | 2004-12-09 | 2006-06-15 | Advantest Corporation | Method and system for performing installation and configuration management of tester instrument modules |
US7131122B1 (en) * | 2000-08-24 | 2006-10-31 | International Business Machines Corporation | Apparatus, system and method for detecting old version of an applet in a client brower's JVM |
US7194506B1 (en) * | 2000-12-21 | 2007-03-20 | Vignette Corporation | Method and system for cache management of locale-sensitive content |
US20070067581A1 (en) * | 2003-03-25 | 2007-03-22 | Baek Jo H | Method for storing and running application program in flash-rom |
US7304758B2 (en) * | 2002-03-27 | 2007-12-04 | Sharp Laboratories Of America, Inc. | Dynamically updating a printer driver |
US7363623B2 (en) * | 2004-08-05 | 2008-04-22 | Canon Kabushiki Kaisha | Services of remote software installation, configuration and afterward support, for network connected peripherals |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1200347C (en) | 2002-07-08 | 2005-05-04 | 华为技术有限公司 | Method for implementing dynamic loading of single board chip FIRMWARE program |
US7930693B2 (en) | 2005-04-04 | 2011-04-19 | Cisco Technology, Inc. | Method and system for accessing and launching a java based applet as a locally installed application |
-
2005
- 2005-04-04 US US11/099,395 patent/US7930693B2/en active Active
-
2006
- 2006-04-03 CN CN200680006413A patent/CN100583038C/en active Active
- 2006-04-03 WO PCT/US2006/012307 patent/WO2006107872A2/en active Application Filing
- 2006-04-03 EP EP06749161.3A patent/EP1866758B1/en active Active
Patent Citations (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5155847A (en) * | 1988-08-03 | 1992-10-13 | Minicom Data Corporation | Method and apparatus for updating software at remote locations |
US5809287A (en) * | 1994-09-08 | 1998-09-15 | Compaq Computer Corporation | Automatic computer upgrading |
US5960189A (en) * | 1994-09-08 | 1999-09-28 | Compaq Computer Corporation | Automatic computer upgrading |
US5764992A (en) * | 1995-06-06 | 1998-06-09 | Apple Computer, Inc. | Method and apparatus for automatic software replacement |
US5732275A (en) * | 1996-01-11 | 1998-03-24 | Apple Computer, Inc. | Method and apparatus for managing and automatically updating software programs |
US5881236A (en) * | 1996-04-26 | 1999-03-09 | Hewlett-Packard Company | System for installation of software on a remote computer system over a network using checksums and password protection |
US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US5923885A (en) * | 1996-10-31 | 1999-07-13 | Sun Microsystems, Inc. | Acquisition and operation of remotely loaded software using applet modification of browser software |
US6139177A (en) * | 1996-12-03 | 2000-10-31 | Hewlett Packard Company | Device access and control using embedded web access functionality |
US6654954B1 (en) * | 1998-02-17 | 2003-11-25 | International Business Machines Corporation | Computer system, program product and method utilizing executable file with alternate program code attached as a file attribute |
US20020002595A1 (en) * | 1998-09-01 | 2002-01-03 | Trevor Blumenau | Collection of images in web use reporting system |
US20020009552A1 (en) * | 1998-09-04 | 2002-01-24 | Dukeplanning & Co., Inc. | Method for repairing the coated surface of a vehicle |
US6470494B1 (en) * | 1998-11-30 | 2002-10-22 | International Business Machines Corporation | Class loader |
US6430570B1 (en) * | 1999-03-01 | 2002-08-06 | Hewlett-Packard Company | Java application manager for embedded device |
US6675201B1 (en) * | 1999-03-03 | 2004-01-06 | Nokia Mobile Phones Ltd. | Method for downloading software from server to terminal |
US6381631B1 (en) * | 1999-06-03 | 2002-04-30 | Marimba, Inc. | Method and apparatus for controlling client computer systems |
US6513158B1 (en) * | 1999-11-15 | 2003-01-28 | Espial Group Inc. | Method and apparatus for running multiple java applications simultaneously |
US6675381B1 (en) * | 2000-01-20 | 2004-01-06 | Mitsubishi Denki Kabushiki Kaisha | Software-module dynamic loader, a software-module dynamic loading method and a medium storing the software-module dynamic loading method |
US6546554B1 (en) * | 2000-01-21 | 2003-04-08 | Sun Microsystems, Inc. | Browser-independent and automatic apparatus and method for receiving, installing and launching applications from a browser on a client computer |
US6826750B1 (en) * | 2000-03-23 | 2004-11-30 | International Business Machines Corporation | Method of automatically selecting program and data updates based upon versions |
US20030208569A1 (en) * | 2000-04-14 | 2003-11-06 | O'brien Michael D | System and method for upgrading networked devices |
US6986133B2 (en) * | 2000-04-14 | 2006-01-10 | Goahead Software Inc. | System and method for securely upgrading networked devices |
US20030041110A1 (en) * | 2000-07-28 | 2003-02-27 | Storymail, Inc. | System, Method and Structure for generating and using a compressed digital certificate |
US7131122B1 (en) * | 2000-08-24 | 2006-10-31 | International Business Machines Corporation | Apparatus, system and method for detecting old version of an applet in a client brower's JVM |
US20050114852A1 (en) * | 2000-11-17 | 2005-05-26 | Shao-Chun Chen | Tri-phase boot process in electronic devices |
US20020078262A1 (en) * | 2000-12-14 | 2002-06-20 | Curl Corporation | System and methods for providing compatibility across multiple versions of a software system |
US7194506B1 (en) * | 2000-12-21 | 2007-03-20 | Vignette Corporation | Method and system for cache management of locale-sensitive content |
US20020095522A1 (en) * | 2001-01-16 | 2002-07-18 | Hayko James Steven | System and method for automatic provision of an application |
US20050144514A1 (en) * | 2001-01-29 | 2005-06-30 | Ulrich Thomas R. | Dynamic redistribution of parity groups |
US20030009694A1 (en) * | 2001-02-25 | 2003-01-09 | Storymail, Inc. | Hardware architecture, operating system and network transport neutral system, method and computer program product for secure communications and messaging |
US6910066B1 (en) * | 2001-03-05 | 2005-06-21 | Principal Financial Services, Inc. | System, method, and apparatus for applet caching |
US20020196460A1 (en) * | 2001-06-22 | 2002-12-26 | Parry Travis J. | Remote access to print job retention |
US20030093508A1 (en) * | 2001-10-18 | 2003-05-15 | Seiko Epson Corporation | System for installing and launching network applications |
US20030084440A1 (en) * | 2001-10-26 | 2003-05-01 | George Lownes | Method of providing a code upgrade to a host device having a smart card interface |
US7304758B2 (en) * | 2002-03-27 | 2007-12-04 | Sharp Laboratories Of America, Inc. | Dynamically updating a printer driver |
US20040003034A1 (en) * | 2002-06-27 | 2004-01-01 | Weiyun Sun | Method for notification of varying versions of code between client and server |
US20040054800A1 (en) * | 2002-08-28 | 2004-03-18 | Samir Shah | Content synchronization frameworks using dynamic attributes and file bundles for connected devices |
US6836657B2 (en) * | 2002-11-12 | 2004-12-28 | Innopath Software, Inc. | Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade |
US20040092255A1 (en) * | 2002-11-12 | 2004-05-13 | De Ji | Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade |
US20070067581A1 (en) * | 2003-03-25 | 2007-03-22 | Baek Jo H | Method for storing and running application program in flash-rom |
US20040261069A1 (en) * | 2003-06-20 | 2004-12-23 | Sun Microsystems, Inc. | Dynamic loading of remote classes |
US20050102669A1 (en) * | 2003-10-15 | 2005-05-12 | Siemens Medical Solutions Usa, Inc. | Software installation file verification media and methods for medical equipment |
US20050138037A1 (en) * | 2003-12-08 | 2005-06-23 | Samsung Electronics Co., Ltd. | Apparatus and method for sharing services on network |
US20050132179A1 (en) * | 2003-12-16 | 2005-06-16 | Microsoft Corporation | Applying custom software image updates to non-volatile storage in a failsafe manner |
US20050240919A1 (en) * | 2004-04-27 | 2005-10-27 | Kim Kyoug I | Firmware update using memory card reader |
US20060004737A1 (en) * | 2004-07-02 | 2006-01-05 | Grzonka Michael T | Computer virus protection for automated pharmaceutical processes |
US7363623B2 (en) * | 2004-08-05 | 2008-04-22 | Canon Kabushiki Kaisha | Services of remote software installation, configuration and afterward support, for network connected peripherals |
US20060075004A1 (en) * | 2004-10-04 | 2006-04-06 | Stakutis Christopher J | Method, system, and program for replicating a file |
US20060130041A1 (en) * | 2004-12-09 | 2006-06-15 | Advantest Corporation | Method and system for performing installation and configuration management of tester instrument modules |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101976198A (en) * | 2010-10-27 | 2011-02-16 | 中兴通讯股份有限公司 | Method and device for controlling startup of application program in embedded system |
US20140210968A1 (en) * | 2013-01-31 | 2014-07-31 | iStoc Oy | Mobile test reader apparatus |
US9760113B2 (en) * | 2015-02-20 | 2017-09-12 | Sony Interactive Entertainment America Llc | Backward compatibility through use of spoof clock and fine grain frequency control |
US10534395B2 (en) | 2015-02-20 | 2020-01-14 | Sony Interactive Entertainment LLC | Backward compatibility through use of spoof clock and fine grain frequency control |
US11119528B2 (en) | 2015-02-20 | 2021-09-14 | Sony Interactive Entertainment LLC | Backward compatibility through use of spoof clock and fine grain frequency control |
US11829197B2 (en) | 2015-02-20 | 2023-11-28 | Sony Interactive Entertainment LLC | Backward compatibility through use of spoof clock and fine grain frequency control |
Also Published As
Publication number | Publication date |
---|---|
EP1866758B1 (en) | 2018-09-19 |
EP1866758A4 (en) | 2009-12-30 |
EP1866758A2 (en) | 2007-12-19 |
CN101128800A (en) | 2008-02-20 |
CN100583038C (en) | 2010-01-20 |
US7930693B2 (en) | 2011-04-19 |
WO2006107872A3 (en) | 2007-03-01 |
WO2006107872A2 (en) | 2006-10-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7930693B2 (en) | Method and system for accessing and launching a java based applet as a locally installed application | |
US20210349706A1 (en) | Release lifecycle management system for multi-node application | |
US11599348B2 (en) | Container image building using shared resources | |
US8701104B2 (en) | System and method for user agent code patch management | |
RU2421785C2 (en) | Automated control of device drivers | |
EP2973147B1 (en) | Policy-based secure web boot | |
JP4286798B2 (en) | Method for installing driver file on hard drive, computer and computer-readable storage medium | |
JP5328054B2 (en) | Behavior of add-on components in virtual environments | |
US7886292B2 (en) | Methodology of individualized software deployment for hardware-independent personal computer mass development | |
KR20090007575A (en) | Booting an operating system in discrete stages | |
CN104932919A (en) | Implementation method of Linux unattended setup | |
CA2676331A1 (en) | Method of loading software in mobile and desktop environments | |
CN107463388B (en) | UEFI diskless starting method | |
CN107391193A (en) | A kind of client, the system and method for configuration server | |
CN102707971A (en) | Method for automatically acquiring and installing software in virtual machine | |
EP3785150A1 (en) | Automatic generation of app-specific client certification | |
JP5736335B2 (en) | Application analysis apparatus, application analysis system, and program | |
CN110045998A (en) | Load the method and device of dynamic base | |
CN113821220A (en) | Installation method and device of linux operating system | |
US20020083426A1 (en) | Installation of network components or services | |
Nusairat et al. | Raspberry Pi | |
US8291203B2 (en) | Using a live operating system to set up and configure an active management technology device | |
US9910678B1 (en) | NetBoot for installation of a non-native OS on a target host | |
CN110830550A (en) | Computer cluster and diskless starting method thereof | |
CN116484360B (en) | RASP-based injection method, RASP-based injection device, RASP-based injection medium and RASP-based injection equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:OTTAMALIKA, IQLAS MAHEEN;SPRING, MAXIMILIAN J.;REEL/FRAME:016474/0760 Effective date: 20050404 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |