RU2348065C2 - System of automatic component processing in device - Google Patents

Abstract

FIELD: physics, computer technology.

SUBSTANCE: invention concerns automatic component processing in a device. Method of automatic processing involves acceptance of version identifier associated to action list, defining whether version identifier is not equivalent saved version identifier, action list acceptance, analysis of action list for obtaining component identifier and associated action, and performance of this action in respect of the component identified by component identifier.

EFFECT: increase of processing response time.

36 cl, 5 dwg

Description

This application takes precedence over a pending U.S. patent application entitled "Auto-Install," number 60/435 486, filed on December 20, 2002, the disclosure of which is incorporated herein by reference in its entirety.

This application also has priority over the pending U.S. patent application entitled "Registry-Based Auto Install Component Handling", number 60/435 828 and filed December 20, 2002, the disclosure of which is incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present invention, in General, relates to the processing of components in a device and, more specifically, to a system for automatically installing, updating or removing components in a device.

State of the art

Information networks provide the ability for a large number of users to communicate with each other using multiple network devices. For example, in a wireless communication network, many users can communicate with each other over long distances using portable network telephones. Typically, network devices have many components that control the operation of the device, and ultimately determine the overall health of the network.

In certain circumstances, the network operator needs to update, install, remove or otherwise change the configuration of network devices. For example, when improving system software, the network operator needs to install new components on all network devices to ensure more efficient operation of the network. For example, a network operator may need to install application software, binary executables, or other information on devices to provide enhanced services or to update. In another situation, the network operator may want to install enterprise applications or other applications for updating devices, taking into account the requirements for a particular type of device. In addition, if there is a problem with the installed component of the system, the network operator may also need to install an updated component to fix the problem, regardless of whether the device user is aware of the problem at all. For example, if there is a problem with the current component of the device that allows the user to view multimedia content, the network operator may need to update all the devices on the network to replace this component with a new component that does not have this problem.

One of the techniques used to install, update, remove, or otherwise change components in a device is to wait for the device user to bring the device to a service center. At the service center, service personnel can reprogram the device so that the latest version of the component is installed in the device. Unfortunately, this process is very inefficient, since device users may not contact the device with a service center if they are not aware of the problem, or if the problem does not occur when they use the device. Since not all devices will be updated, some devices will not provide the best performance, which can lead to a decrease in the efficiency of the entire network.

Therefore, a system of automatic processing of components in the device is required, which would allow installing and activating selected versions of components. The system must be flexible enough to process components in a large number of devices in a relatively short time, which ensures fast updating of all devices operating in the network, as a result of which the best performance of the device is ensured and the network efficiency is increased.

Disclosure of invention

In one or more embodiments, a system for automatically processing components in a device is provided. For example, in one embodiment, the system allows the device to install, update, delete, activate, disable, re-call, or otherwise change the state of a component in the device using the installed version action list available on the download server. The components that can be processed can be of any type, for example, an application program, an executable file, configuration information, user interface settings, random data, or any other type of information.

While the system is running, the device checks the version of the list of actions on the boot server, comparing them with the saved versions associated with the last list of actions processed by the device. If the two versions are different, the device downloads a new action list from the server and analyzes each item in the action list to process the components in the device. In one embodiment, each item in the action list contains a component / action pair that associates a component identifier with an action identifier. The component identifier identifies the type of component and its current version. The action identifier identifies the action that must be performed by the device in relation to the identified component.

In one embodiment, the device analyzes each component / action pair in the action list to determine if an action should be performed on the identified component. The device compares the version of the component in the action list with the version of the component stored in the device. If the two versions of the component match, the device does not take any action with respect to this component / action pair. If the versions are different, the device performs the action associated with the component in the action list. For example, if the action is to install the identified component, the device downloads the component and any other necessary information from the download server, and installs this component on the device. Thus, the device sequentially analyzes the list of actions, performing the assigned actions only for new versions of the component.

After processing a specific component / action pair, the component version stored in the device is updated using the new component version presented in the action list. When the entire list of actions has been processed, the device writes the identifier of the version of the list of actions to prevent reprocessing the current list of actions in the future. Thus, the device will not process another action list until the version of the action list available on the download server differs from the version stored in the device.

In one embodiment, the device checks the version of the action list each time the device contacts the download server. For example, a device can communicate with a download server after the device is turned on or at periodic intervals. The system provides a mechanism that allows processing components in a device without user interaction or with limited user interaction. For example, in one embodiment, components can be transferred to the device when it is turned on to effectively provide “installation without notifying the user”. In another embodiment, a user interface is used, due to which the processing of components can be carried out at the choice of the user. Moreover, the system provides the ability to process components forcibly, with notification, on demand or by choice.

The system can be used to process components in a single device or in a large number of devices. For example, in an information network that uses a large number of devices, devices can access an action list server, a separate action list can be transferred to all devices, and each device can determine which components should be processed for this device. In another embodiment, the server may provide multiple action lists that may be used by various types of devices. For example, different types of devices can access various action lists to process the components required for this type of device. Thus, the system provides the ability to conduct global updates of a large number of devices, while updates are performed within a few hours or days, as each device comes into contact with the list server. In addition, communication between the server and the device can be carried out using any reliable communication technology, such as encryption or encoding of any type, which provides authentication of the device, and at the same time, any information is transmitted securely.

In one embodiment, a method for automatically processing components in a device is provided. The method comprises receiving a version identifier associated with the action list, determining that the version identifier is not equivalent to the stored version identifier, receiving an action list, analyzing the action list to obtain a component identifier and an associated action, and performing an action on the component identified by the component identifier.

In yet another embodiment, a device for automatically processing components in a device is provided. The device comprises a logic circuitry for receiving a version identifier associated with the action list and a logic circuitry for comparing the version identifier with the stored version identifier. The device also contains a logic circuit for receiving a list of actions if the version identifier is not equivalent to the stored version identifier, and a logic circuit for analyzing the list of actions in order to obtain a component identifier and associated action. The device also contains a logic circuit designed to perform actions on the component identified by the identifier of the component.

In one embodiment, a device for automatically processing components in a device is provided. The device comprises means for receiving a version identifier associated with the list of actions, and means for determining that the version identifier is not equivalent to the stored version identifier. The device also comprises means for receiving a list of actions and means for analyzing a list of actions for obtaining a component identifier and an associated action. The device also comprises means for performing an action on the component identified by the identifier of the component.

In another embodiment, a computer-readable medium is provided comprising instructions that, when executed using a logic circuit in a device, provide automatic processing of components in the device. A computer-readable medium contains instructions for receiving a version identifier associated with the list of actions, and instructions for determining that the version identifier is not equivalent to the stored version identifier. The computer-readable storage medium also contains instructions for receiving an action list and instructions for analyzing an action list for obtaining a component identifier and an associated action. A computer-readable storage medium also contains instructions for performing an action on a component identified by a component identifier.

Other aspects, advantages, and features of the present invention will become apparent after reading the following brief description of the drawings, detailed description of the invention, and claims.

Brief Description of the Drawings

The above aspects and related advantages of the embodiments described here will be more apparent when reading the following detailed description, in conjunction with an examination of the accompanying drawings, in which:

figure 1 shows one embodiment of a system for automatically processing components in a device;

figure 2 shows a functional diagram of a device that includes one embodiment of a system for automatic processing of components;

figure 3 presents one embodiment of the method of operation of the device to provide a system for automatic processing of components in the device;

figure 4 shows the transactions that occur between the download server and the device during operation of one embodiment of a system for automatically processing components in the device;

figure 5 shows one embodiment of a list of actions for use in a system for automatically processing components in a device.

The implementation of the invention

The following detailed description provides embodiments of a system for automatically processing components in a device. The system is suitable for use in many types of cable or wireless networks, including, without limitation, communication networks, public networks such as the Internet, private networks such as virtual private networks (VPNs), local area networks, wide area networks, telecommunication networks or any other types of information networks. The system is also suitable for use with any type of device that allows you to download and install components. For example, the system is suitable for use with office computers, laptop computers, and handheld devices, such as portable phones, PDAs, or any other type of device that can receive and install components.

In one or more embodiments, the system interacts with a runtime running on a device that is used to simplify the operation of the device, for example, it handles generalized calls to specific resources of the device. One such executable environment is the Binary Runtime Environment for Wireless ™ (BREW ™) software platform, developed by QUALCOMM, Inc, San Diego, California. The following description assumes that the device is running an executable environment, such as the BREW software platform. However, one or more embodiments of the system can be used with other types of executable environments to automatically process components in a variety of cable and wireless devices.

1 shows an embodiment of a system 100 for automatically processing components in a device. The system 100 comprises a server 102, an information network 104, and a device 106. The information network 104 may be any type of cable or wireless network that provides information transfer between the server 102 and the device 106. For example, the network 104 may be a data network, a global computing network. a network, a virtual private network, or a public network such as the Internet.

In one or more embodiments, the system operates to process components in the device 106. For example, the server 102 includes components 112, an action list 110, and an action list version identifier 108. Version identifier 108 identifies the current version of action list 110. The action list 110 contains component / action pairs, where each pair contains a component identifier and an action identifier. A component identifier is a unique item identifier that identifies a particular component. The component identifier portion is used to identify the version of the component. For example, a component identifier is a sequence of bits where a portion of bits is used to identify a version of a component. An action identifier identifies a specific action, such as install, update, remove, recall, disconnect, or any other action that device 106 performs with respect to the identified component.

During operation, the server 102 transmits the identifier 108 of the action list version to the device 106 over the network 104. For example, the device 106 can come into contact with the server 102 during the startup sequence, and the server 102 responds by transmitting the identifier 108 of the action list version to the device 106. The device 106 compares the version identifier 108 with the stored version identifier 114, which represents the version of the last action list, for processing by the device 106. If the downloaded version 108 and the saved version 114 are equivalent us, then the device does not need to perform any installation or modification of existing components in the device 116. However, if the downloaded version 108 is different from the saved version 114, then the device 106 receives an indication that additional component processing is required. For example, server 102 may host new components that need to be installed on device 106.

Once device 106 determines that a new version of the action list exists, it sends a request to server 102 to receive a new action list 110. The server 102 responds by transmitting the action list 110 to the device 106. The device 106 then processes the action list 110 to install updates, deletes, or other processing of components identified in the action list 110.

The device 106 performs processing of the action list 110 by sequentially processing each component / action pair and determining whether or not actions should be taken with respect to each component. For example, if the action list indicates that the component should be installed or updated, the device 106 downloads the component 112 and any other required files from the server 102 and installs them in the device 106. For example, information from the server 102 transmitted to the device 106 is presented, in general, at 120. If the action list 110 indicates that the component should be removed, device 106 removes the component. Thus, each component / action pair in the action list 110 is processed by the device 106 to automatically install, update, remove, etc., the identified component. The action list can be any length, and after processing the action list, device 106 updates the stored identifier 114 of the action list version to save the version of the most recently processed action list (i.e., version 108).

In one embodiment, the device 106 analyzes the component / action pairs in the action list 110 to determine if action is required on a particular component. For example, the latest version of a component can already be installed on device 106, and therefore, the device does not need to reinstall this component. In one embodiment, the component identifier in the action list 110 includes information for determining the version of the component. For example, version information may be attached to the end of a component identifier. The device 106 compares the saved version 118 of the component with the version of the component loaded in the action list 110. If the saved and downloaded versions of the component are the same, then the device does not need to take any action with respect to this component. However, if the saved and downloaded versions of the component are different from each other, then the device 106 performs the action associated with this component from the list of actions. Thus, the system works very efficiently because device 106 only processes new versions of components.

Figure 2 shows a functional diagram of a device 200, which includes one embodiment of an automatic component processing system in a device 200. The device comprises a processing logic 208, a comparison logic 206, a functional logic 214, a version upgrade logic 224, a stored version identifier 204 the action list, identifiers 212 of the component version and installed components 226. The described logic circuits and functions provided by the device 200 can be performed in hardware environments vah, software, or a combination of hardware and software. For example, in one or more embodiments, the processing logic 208 comprises a CPU, a processor, a gate array, hardware logic, memory elements, a virtual machine, software, and / or any combination of hardware and software. Meanwhile, the processing logic 208 generally comprises a logic designed to execute machine-readable instructions for performing the functions described herein. It should be noted that the device 200 represents only one embodiment, and that changes, additions or changes in the arrangement of elements of the device can be made without departing from the scope of the invention.

FIG. 3 shows one embodiment of a method 300 for operating a device, such as a device 200, for automatically processing a system of components in a device 200. For clarity, method 300 will be described with reference to the device 200 shown in FIG. 2. In addition, suppose that the device 200 is connected using a reliable communication channel to a download server via an information network, as shown in FIG.

At block 302, the device receives the version identifier of the action list from the download server. For example, the device communicates with the download server via the information network, and the download server passes the version identifier of the action list to the device, as shown in 202.

At block 304, a check is performed to determine if the downloaded action list version identifier is different from the stored version identifier, which is associated with the last action list processed by the device. For example, the downloaded version identifier 202 and the stored version identifier 204 are input into a comparison logic 206 that compares the two identifiers to determine their equivalence. If both version identifiers are equivalent, the process returns to block 302 to obtain a new version of the action list at another time. If the two version identifiers are different (Diff), the process proceeds to block 306.

At block 306, the device reads a list of actions from the download server. For example, the action list 210 is downloaded from the server to the processing logic 208 via the information network.

At block 308, the device begins to process the action list by analyzing the first component / action pair in the action list. For example, processing logic 208 processes the loaded action list 210 to analyze component / action pairs.

At block 310, a check is performed to determine what action is required, if any, for the component / action pair currently being processed. In one embodiment, the device automatically performs an action by moving to block 312. However, this may lead to reinstalling existing components in the device. In another embodiment, the version of the component is checked to determine if an action is required. For example, if the action is to “install” a component, check the version of the component to make sure that the component of this version is already installed on the device. Thus, the method works to prevent reinstallation of components that are already installed in the device. For example, processing logic 208 reads the stored component version identifier 212 and compares it with the version of the component identified in the action list. In one embodiment, the version of the component is embedded in the component identifier presented in the action list. If the two versions of the components coincide, no additional action is required on this component, and the process proceeds to block 416. If the two versions of the components are different from each other, then the processing logic 208 performs the action associated with the component and the process proceeds to block 312.

At block 312, the action associated with the component in the current component / action pair is performed to change the state of the identified component. For example, the processing logic 208 controls the action logic 214 to perform the steps of installing, updating, removing, activating, disconnecting, recalling, or otherwise changing the state of the identified component. For example, a software call may be made when a component is removed from the device, but the associated data and / or licensing information is not deleted. For example, if the action is to install or update a component, the processing logic 208 downloads (or updates) the component 222 from the download server via the information network. The downloaded component is then installed as the installed component 226. The processing logic 208 can perform any type of installation or update the procedure for installing or updating the downloaded component 222 as the installed component 226. If the action is to remove the component, the processing logic 208 controls the logic 220 removal to remove the identified component from installed components 226. Although not shown in FIG. 2 and 3, practically any type of action can be performed on a component, such as installing, updating, uninstalling, recalling, activating and deactivating, etc.

At block 314, the component version list is updated to reflect that a new version of the component has been installed or updated, or that the component has been removed. For example, processing logic 208 controls version upgrade logic 224 to update stored component version identifiers 212 with new information about the component currently being processed.

At block 316, a check is performed to determine whether all component / action pairs in the action list have been processed. If all pairs have been processed, the process proceeds to block 320. If not all pairs have been processed, the process proceeds to block 318, where it refers to the next pair for processing in block 310. The action list 210 can be of any length, and thus any number of component / action pairs for processing can exist in it.

At block 320, the stored version identifier of the device action list is updated. For example, the processing logic 208 controls the update version logic 224 to update the stored action list version identifier 204 with replacing it with the identifier associated with the last processed action list. Due to this, the system will not process another list of actions until a new version of the list of actions becomes available.

In one embodiment, a system for automatically processing device components comprises program instructions stored on a computer-readable storage medium that, when executed using processing logic 208, provides the functions described herein. For example, instructions may be downloaded to device 200 from a computer readable medium, such as a floppy disk, CD-ROM, memory card, flash memory device, RAM, ROM, or any other type of memory device or computer readable medium, which may be associated with device 200. In another embodiment, instructions may be downloaded to device 200 from a network resource that communicates with device 200 through an information network. Instructions, when executed using processing logic 208, provide one or more embodiments of an automatic component processing system in a device, as described herein.

It should be noted that the method 300 represents only one embodiment, and that changes, additions or changes in the layout of the elements of the method can be made without departing from the scope of the invention.

Figure 4 shows the transactions 400 that occur between the download server and the device during operation of one embodiment of an automatic component processing system in the device. For example, transaction 400 may occur between device 106 and server 102 shown in FIG. 1.

At the beginning of automatic processing, device 106 requests the identifier of the latest version of the action list from server 102, as shown at 402. The action list contains component / action pairs that describe the action that the device should perform with respect to each identified component. The action list may change or may be updated periodically, and the action list version identifier identifies the current version of the action list.

Server 102 responds to a request from device 106 by transmitting the version identifier of the current action list, as shown at 404. After receiving the action list version identifier, the device compares this identifier with the stored action list version identifier. If the two version identifiers are equivalent, then the device does not take any further action. If the two version identifiers are different, then the device 102 requests a new list of actions from the server 102, as shown at 406.

Server 102 responds to a request from device 106 by sending a new action list, as shown at 408. Device 106 processes each component / action pair in the action list to determine whether or not to install, update, or remove a specific component. If device 106 determines that a particular component should be installed or updated, device 106 requests a component (or update) from server 102, as shown at 410.

The server 102 responds to the request by transmitting the requested component to the device 106. The device 106 receives the component and performs installation or update on request. A component may have a component version identifier that the device stores locally. After the device 106 analyzes the entire action list and considers all the necessary components from the server 102, the device 106 updates the locally stored version identifier of the action list, replacing it with the version identifier of the action list that has just been processed. Thus, the device 106 will not process another action list from the server 102 until the identifier of the action list version downloaded from the server differs from the stored identifier.

FIG. 5 shows one embodiment of an action list 500 for use in an automatic component processing system in a device. The list of actions 500 contains the identifier 502 of the version of the list of actions, followed by pairs (504, 506) of the component / action. For example, a component / action pair 504 contains a component identifier and a corresponding action. In one embodiment, the component identifier also includes a component version identifier, which allows you to use the component version to determine whether or not the component currently exists in the device. An action can be one of install, upgrade, or remove, however, any other type of action can also be defined. The information in the action list can be encoded using any appropriate format, and the identifiers of the component and action can be of any type.

Accordingly, although one or more embodiments of a system for automatically processing components in a device have been presented and described herein, it should be understood that various changes can be made with respect to the embodiments without departing from their essence or essential characteristics. Therefore, the disclosures and descriptions provided herein are intended to illustrate and not to limit the scope of the invention, which is presented in the following claims.

Claims (36)

1. A method for automatically processing components in a device, comprising: receiving a version identifier associated with an action list; determining that the version identifier is not equivalent to the stored version identifier; receiving a list of actions; analysis of the list of actions to obtain the identifier of the component and associated action; and performing an action on the component identified by the identifier of the component. 2. The method according to claim 1, which also comprises updating the stored identifier so that it is equivalent to the version identifier. 3. The method according to claim 1, in which the action is an installation, and the execution step comprises installing a component in the device. 4. The method according to claim 1, in which the action is a removal, and the execution step comprises removing a component from the device. 5. The method according to claim 1, wherein the execution step comprises changing a state of a component in a device. 6. The method of claim 1, wherein the analysis step further comprises determining that the version of the component associated with the identifier of the component is not equivalent to the stored version of the component. 7. The method according to claim 6, which also includes updating the saved version of the component so that it is equivalent to the version of the component. 8. The method according to claim 1, which also comprises receiving a version identifier, a list of actions, and a component from the server. 9. The method according to claim 1, in which the device is a wireless device. 10. An apparatus for automatically processing components, comprising a logic circuit for receiving a version identifier associated with an action list; logic for comparing the version identifier with the stored version identifier; logic for receiving a list of actions if the version identifier is not equivalent to the stored version identifier; logic to analyze the list of actions to obtain the identifier of the component and the associated action and
logic to perform an action on a component identified by a component identifier. 11. The device according to claim 10, which also contains a logic circuit for updating the stored identifier, so that it is equivalent to the version identifier. 12. The device according to claim 10, in which the logic circuit for performing an action comprises a logic circuit for installing a component in the device. 13. The device according to claim 10, in which the logic circuit for performing an action comprises a logic circuit for removing a component from the device. 14. The device according to claim 10, in which the logic circuit for performing an action comprises a logic circuit for changing the state of a component in the device. 15. The device according to claim 10, in which the logic diagram is intended to analyze that the list of actions also contains a logic diagram for determining that the version of the component associated with the identifier of the component is not equivalent to the stored version of the component. 16. The device according to clause 15, which also contains a logic diagram for updating a saved version of the component so that it is equivalent to the version of the component. 17. The device according to claim 10, which also contains a logic circuit for receiving a version identifier, a list of actions, and a component from a server. 18. The device of claim 10, in which the device is a wireless device. 19. An apparatus for automatically processing components, comprising: means for receiving a version identifier associated with an action list; means for determining that the version identifier is not equivalent to the stored version identifier; means for receiving a list of actions; means for analyzing the list of actions to obtain a component identifier and an associated action; and means for performing an action on the component identified by the component identifier. 20. The device according to claim 19, which also contains means for updating the stored identifier, so that it is equivalent to the version identifier. 21. The device according to claim 19, in which the means for performing comprises means for installing a component in the device. 22. The device according to claim 19, in which the means for performing comprises means for removing a component from the device. 23. The device according to claim 19, in which the means for performing comprises means for changing the state of a component in the device. 24. The device according to claim 19, in which the means for analysis also contains means for determining that the version of the component associated with the identifier of the component is not equivalent to the stored version of the component. 25. The device according to paragraph 24, which also contains means for updating the saved version of the component, so that it is equivalent to the version of the component. 26. The device according to claim 19, which also contains means for receiving a version identifier, a list of actions and a component from the server. 27. The device according to claim 19, in which the device is a wireless device. 28. A computer-readable storage medium containing instructions that, when the processing logic in the device is executed, operate to automatically process the components, containing instructions for receiving the version identifier associated with the action list; instructions for determining that the version identifier is not equivalent to the stored version identifier; instructions for receiving a list of actions; instructions for analyzing the list of actions to obtain a component identifier and an associated action; and instructions for performing an action on the component identified with the component identifier. 29. The computer-readable storage medium according to claim 28, which also contains instructions for updating the stored identifier so that it is equivalent to the version identifier. 30. The computer-readable storage medium according to claim 28, wherein the instructions for execution comprise instructions for installing the component in the device. 31. A computer-readable storage medium according to claim 28, wherein the instructions for execution comprise instructions for removing a component from the device. 32. The computer-readable storage medium according to claim 28, wherein the instructions for execution comprise instructions for changing the state of a component in the device. 33. The computer-readable medium of claim 28, wherein the instructions for analysis also include instructions for determining that the version of the component associated with the identifier of the component is not equivalent to the stored version of the component. 34. A computer-readable storage medium according to claim 33, which also contains instructions for updating a stored version of a component so that it is equivalent to a version of the component. 35. The computer-readable storage medium according to claim 28, which also contains instructions for receiving from the server a version identifier, a list of actions, and a component. 36. The computer-readable storage medium of claim 28, wherein the device is a wireless device.

Images