TWI329266B - System for registry-based automatic installation and component handling on a device - Google Patents
System for registry-based automatic installation and component handling on a device Download PDFInfo
- Publication number
- TWI329266B TWI329266B TW92136235A TW92136235A TWI329266B TW I329266 B TWI329266 B TW I329266B TW 92136235 A TW92136235 A TW 92136235A TW 92136235 A TW92136235 A TW 92136235A TW I329266 B TWI329266 B TW I329266B
- Authority
- TW
- Taiwan
- Prior art keywords
- component
- processing routine
- action
- type
- logic
- Prior art date
Links
- 238000009434 installation Methods 0.000 title claims description 27
- 230000009471 action Effects 0.000 claims description 185
- 238000012545 processing Methods 0.000 claims description 183
- 238000000034 method Methods 0.000 claims description 120
- 230000008569 process Effects 0.000 claims description 74
- 230000008859 change Effects 0.000 claims description 12
- 230000035939 shock Effects 0.000 claims 1
- 238000012360 testing method Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000000875 corresponding effect Effects 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 206010028980 Neoplasm Diseases 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 235000013405 beer Nutrition 0.000 description 1
- 201000011510 cancer Diseases 0.000 description 1
- 239000006071 cream Substances 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
- Manipulator (AREA)
- Machine Translation (AREA)
- Automatic Assembly (AREA)
Description
1329266 玖、發明說明: 【相關申請案交互參考】 本專利申請案要求於2002件12月20日提出申請之美國臨 時專利申請案第60/435,486號標題為「AUTO-INSTALL」的 優先權利益,基於所有目的,該專利申請案之揭示内容以 引用方式整份併入本文中。 本專利申請案要求於2002件12月20日提出申請之美國臨 時專利申請案第60/435,486號標題為「REGISTRY-BASED AUTO INSTALL COMPONENT HANDLING」的優先權利 益,基於所有目的,該專利申請案之揭示内容以引用方式 整份併入本文中。 【發明所屬之技術領域】 本發明廣泛係關於處理裝置上元件,具體而言,係關於 一種用於基於登錄之自動安裝以及裝置上元件處理之系 統。 【先前技術】 資料網路提供一種供大量使用者使用各種具備網路連接 能力型裝置互相通信的方式。例如,在無線通信網路中, 各種具備網路連接能力的攜帶型裝置允許使用者長距離互 相通信。具備網路連接能力型裝置通常係由各種安裝的元 件所組態而成,這些安裝的元件控制裝置的操作方式,並 且最終控制整個網路執行效能。 在某些情況下,網路操作者希望升級、安裝、刪除或變 更具備網路連接能力型裝置的組態。例如,當系統軟體已 O:\90\90362.DOC -6 - 1329266 經過改進時,網路操作員會希望在網路中的所有裝置上安 裝新的元件,以便提高網路運作效率。例如,網路操作: 會想要在裝置上安裝應用程式軟體、二進位執行檔或其他 貢訊,以提供服務增強功能或升級功能。在其他情況下, 網路操作者會想要根據一特定類型裝置,安裝企 式或其他裝置升級應用程式。另夕卜,如果判定現行=裝= 系統元件有問冑,則網路操作者會想要安裝升級版元件來 解決問題,而不管裝置使用者是否查覺到問題。例如,如 =用於允許使用者檢視多媒體内容的現有裝置元件有問 題,則網路操作者會想要升級網路上的所有袭置,使用沒 有問題的新元件取代有問題的元件。 久 /項用於升級、安裝、醫或變更裝置上元件的技術, 是等待裝置使用者將裝置送回維修中心。送達維修中心 後’維修人員可重新設定裝置,使裝置具有最新的^件版 本。然而,如果裝置使用者未查覺問題,或問題尚不會影 響裝置知作’就不會送回裝置,所以這是無效率的做法。 因此不會將所有裝置升級,所以部份裝置之操作不能提供 最佳效率,並且網路整體運作降級。 因此,需要一種自動處理裝置上元件之系統以允許安 裝及啟動所選用的元件版本。系統應具有足夠的彈性,以 在才田短時間内處理大量裝置上的元件,藉以提供迅速 升’·及在網路上運作的所有裝置進而導致最佳裝置效能及 增加網路效率。 【發明内容】 ^項或多項具體實施例中,本發明提供—種自動 允許—裝^在一項具體實施例中,該系統 作:使用可在-下載伺服器上取得之已列版本的動 置上進仃安裝、更新、刪除、啟動、停用或變更一裝 可月^之狀態。可處理的元件可能屬於任何類型,例如: :疋.』程式、可執行檔 '組態資訊' 使用者介面設 A機資料或任何類型的資訊。 作作期間’裝輯照—與該裝置所處理之最新動 清的儲存版本,檢查該下㈣服器上之該動作 :的版本。如果版本不同’則該裝置從該飼服 的動作清單,並且剖析該動作清單中的每筆項目,以 理,裝置上之元件。在一項具體實施例中,該動作清單中1329266 发明, Invention Description: [Related Application Cross-Reference] This patent application claims the priority interest of "AUTO-INSTALL" in US Provisional Patent Application No. 60/435,486, filed on December 20, 2002. The disclosure of this patent application is hereby incorporated by reference in its entirety in its entirety for all purposes. This patent application claims priority to U.S. Provisional Patent Application Serial No. 60/435,486, entitled "REGISTRY-BASED AUTO INSTALL COMPONENT HANDLING", filed on December 20, 2002, which is based on The disclosure is hereby incorporated by reference in its entirety. BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates generally to components on a processing device, and more particularly to a system for automatic installation based on login and component processing on a device. [Prior Art] The data network provides a way for a large number of users to communicate with each other using various network-connected devices. For example, in a wireless communication network, various portable devices with network connection capabilities allow users to communicate with each other over long distances. Network-connected devices are typically configured from a variety of installed components that control how the device operates and ultimately control overall network performance. In some cases, network operators want to upgrade, install, remove, or change the configuration of a network-connected device. For example, when the system software has been improved by O:\90\90362.DOC -6 - 1329266, the network operator will want to install new components on all devices in the network to improve network operation efficiency. For example, network operations: You will want to install application software, binary executables, or other tribute on your device to provide service enhancements or upgrades. In other cases, the network operator would like to install an application or other device to upgrade the application based on a particular type of device. In addition, if it is determined that the current = installed = system component has a problem, the network operator will want to install the upgraded component to solve the problem, regardless of whether the device user is aware of the problem. For example, if the existing device component used to allow the user to view the multimedia content has problems, the network operator would like to upgrade all the attacks on the network and replace the problematic component with a new component that is not problematic. The technique used to upgrade, install, or modify components on a device is to wait for the device user to return the device to the repair center. After being delivered to the repair center, the maintenance personnel can reset the device to have the latest version of the device. However, if the device user does not detect the problem, or if the problem does not affect the device, it will not be returned to the device, so this is inefficient. Therefore, all devices will not be upgraded, so the operation of some devices does not provide optimum efficiency and the overall operation of the network is degraded. Therefore, there is a need for a system that automatically processes components on a device to allow installation and activation of selected component versions. The system should be flexible enough to handle a large number of components on the device in a short period of time in order to provide a rapid boost to all devices operating on the network, resulting in optimal device performance and increased network efficiency. SUMMARY OF THE INVENTION In one or more specific embodiments, the present invention provides an automatic permissive-installation system in a specific embodiment that uses a version of the available version that can be obtained on a download server. Put in the state of installing, updating, deleting, starting, deactivating, or changing the installation. The components that can be processed may be of any type, for example: :疋.』 Program, executable file 'Configuration information' User interface Set A machine data or any type of information. During the production period, the installation version is checked with the latest version of the action processed by the device, and the version of the action on the next (four) server is checked. If the version is different, then the device takes a list of actions from the feeding suit and parses each item in the action list to determine the components on the device. In a specific embodiment, the action list
的母葦項目都包括—7Γ ^ l^h AM &括7"件/動作對’用於建立一元件識別項 j動作識別項之間的關聯。該元件識別項識別的一種類 ^的π件及其現行版本。該動作識利識職裝置所要執 仃之關於該識別之元件的動作。 _在一項具財施射,該裝置剖析《作清單中的每一 凡件/動作對,以便判定是否需要執行該識別之元件的動 作。該裝置比較該動作清單中的元件版本與該裝置上所儲 存之-元件版本。如果這兩個元件版本相同,則該裝置不 會採取關於該元件/料對的動作。如果這兩個版本不同, 則該裝置執行與該動作清單甲之該元件相關聯的動作,以 便在該裝置上變更元件之狀態。^,如果動作是安裝該 識別之元#,則該裝置從該下載伺i器下載該元件及任 :The mother-in-law items all include -7Γ^l^h AM &7" pieces/action pairs' are used to establish an association between a component identification item j motion recognition item. The component identification item identifies a class of π pieces and their current versions. This action identifies the action of the component to be identified by the device. _ In a rich cast, the device parses each of the parts/action pairs in the list to determine if the identified component needs to be executed. The device compares the component version in the action list with the component version stored on the device. If the two components are the same version, the device will not take action on the component/pair. If the two versions are different, the device performs an action associated with the component of the action list A to change the state of the component on the device. ^, if the action is to install the identification element #, the device downloads the component from the download server and:
0:\90\9〇362.D〇C -8 - 置僅二,並且在該裝置上安裝該元件。因此,該裝 作僅針對新的元件版本來逐步執行該動作清單中指派的動 在處理—特定元件/動作對後,會使用該動作清單中所提 供的新元件版本來取代該裝置上所儲存的元件版本。,已 處理整個動作清單時,該裝置田 ^ 、,# 切作凊早的版本識別 項,以避免未來重複處理現行動作清 /月早。因此,除非可在 。亥下載伺服器上取得之已列版本 ^ ™ L 町動作/月早版本不同於該 j所儲存之版本,否則該裝置不處理其他動作清單。 在=體實施例中,每當該裝置與該下載伺服器通信 二:;檢查該動作清單之版本。例如,在該裝置 二:ί:以週期性時間間隔’該裝置與該下載飼服器通 ==供一種用於允許處理裝置上元件而不需要使 用者互動或有限❹者互動的機制。例如,在—項具 2例中’可在裝置開機時將元件推入該裝置,而得以高效 :提供「無訊息安裝」(silentinstallation)e在另一 實施例中,提供一使用者介面,而得以在使用者選擇時處 ^牛。因此’該系統允許以強制、提示、要求或選項方 式來處理元件。 該系統可用來處理一單一裝置上元件或大量裝置上元 件例如,在大里裝置可存取一動作清單祠服器的資料網 路中可將ϋ作清單傳遞至所有裝置,並且每個裝 =都可判疋該。裝置所要處理的元件。在另一項具體實施例 中’該伺服器可提供滴用 供過用於不冋裝置類型的多個動作清 1329266 單。例如’不同類型裝置可存取不同動作清單,以便處理 適用於該裝置類型的元件。因此,該系統能夠提供全域更 新大里裝置’並且當每個裝置聯繫該動作清單词服器時的 數二、時或數天時段期間執行更新。此外,可使用任何類型 的安全通信技術(例如,加密或任何類型之編竭)來介於該祠 服态與一伺服器之間的通信,而得以鑑認裝置並且以安全 方式完成資訊傳輸。 在-項具體實施例中,該系統提供依據—元件類型以新 增裝置支援多個元件的能力。提供一種元件「處理常式」 (handler),該元件處理常式被指派以處理-具有一特定元 件類型(即,一特定「多用途網際網路郵件延伸標準」 (胸叫叫㈣“咖Mail Extension, MIME)類型)之二 件。s亥處理常式是一種Λ用链—·七 種應用私式或可執行檔,用於儲存及 認可元件的資料。例如,該系 忑系統可運作成下載及安裝一元 件處理常式,該元件處理常式 吊式被:才日派用於處理具有一所選 顧_型的多個元件。在-項具體實施例中,會在該裝置 ::業:統登錄中註冊該元件處理常式。—旦已安裝該元 、, 戰具有該所選類型之元件, 並且會啟動相關聯之處理常式— 中八μ爽理該兀件。因此,不會 將户個元件處理常式内嵌於作 呆系統層中,於是,OEM或 第二方可提供元件處理常式及/或 ^ 一 、汉次了動態下載/升級元件處 理常式《這項做法不僅允許後製作 杜牺剂 交炎作要在裝置上處理的新元 件類!,而且還允許新機制處理新元件類型。 在一項具體實施例中,本發明 ^種自動處理裝置上0:\90\9〇362.D〇C -8 - Set only two and install the component on the unit. Therefore, the installation is only for the new component version to step through the action-specific component/action pair assigned in the action list, and the new component version provided in the action list is used instead of the device. Component version. When the entire action list has been processed, the device field ^,, # is cut into early version identification items to avoid repeated processing of the current action clear/monthly in the future. Therefore, unless it is available. The published version obtained on the download server ^ TM L operation / monthly version is different from the version stored in j, otherwise the device does not process other action lists. In the body embodiment, whenever the device communicates with the download server, the system checks the version of the action list. For example, in the device two: ί: the device is connected to the downloading device at periodic intervals == for a mechanism for allowing processing of components on the device without requiring user interaction or limited interaction. For example, in the case of 2 items, 'the component can be pushed into the device when the device is turned on, and it is efficient: providing "silentinstallation" e. In another embodiment, a user interface is provided, and It is possible to be at the time of user selection. Thus the system allows components to be processed in a mandatory, prompt, demand or option manner. The system can be used to process components on a single device or a large number of devices. For example, in a data network where the Dali device can access an action list server, the list can be transmitted to all devices, and each device It can be judged. The component to be processed by the device. In another embodiment, the server can provide a plurality of actions for the type of device to be used. For example, 'different types of devices can access different action lists to handle the components that are appropriate for the device type. Thus, the system is capable of providing a global update of the Dali device' and performing an update during the number two, hour or day period when each device contacts the action list vocabulary. In addition, any type of secure communication technique (e.g., encryption or any type of compilation) can be used to communicate between the service state and a server to authenticate the device and complete the transmission of information in a secure manner. In a specific embodiment, the system provides the ability to support multiple components with a new device based on the component type. Providing a component "handler" that is assigned to handle - has a specific component type (ie, a specific "multipurpose internet mail extension standard" (chest call (four)" Extension, MIME) type. The shai processing routine is a chain of use—seven applications private or executable files for storing and authenticating component data. For example, the system can operate as Download and install a component processing routine that is used to process a plurality of components having a selected type. In the specific embodiment, the device is: Industry: Register the component processing routine in the system login. Once the element has been installed, it has the component of the selected type, and the associated processing routine will be started - the middle eight μ is the same. Therefore, The component processing routine will not be embedded in the layer of the system, so the OEM or the second party can provide the component processing routine and / or ^, Han times the dynamic download / upgrade component processing routine "This The practice not only allows the post-production SGD for Class to be processed on the device!, But also allows new types of mechanisms to deal with a new element. In a particular embodiment, the present invention ^ the kinds of automatic processing apparatus
O:\90\90362. DOC •10- 1329266 儿件之方法,其中該元件具有一所選元件類型。該方法包 Μ㈣置上安裝—元件處理常式’纟中該元件處理常式 可運作以處理具有該所選元件類型之多個元件。該方法還 包括剖析該動作清單’以便獲得_用於識別該裝置所要處 理之元件的元件/動作對,以及將該元件下載至該裝置。該 方法還包括判定該元件具有該所選元件類型,以及使用且 有⑽選s件類型來啟動該元件處理常式以處理該元件:、 在一項具體實施例中,本發明提供—種自動處理裝置上 元件之設備,纟中該元件具有一所選元件類型。該設備包 括安裝邏輯,用於在該裝置上安裝-元件處理常式,其中 該元件處理常式可運作以處理具有該所選元件類型之多個 元件。該設備還包括:剖析邏輯,用於剖析該動作清單, 以便獲得-用於識別該裝置所要處理之元件的元件/動作 對,以及下載邏輯,用於將該元件下載至該裝置。該設備 還包括:判;t邏輯,用於狀該元件具有該所選元件類型; 以及啟動邏輯1於使用具有該所選元件類型來啟動該元 件處理常式以處理該元件。 —在-項具體實施例中’本發明提供—種自動處理裝置上 疋件之設備’其中該元件具有—所選元件類型。該設備包 括安裝構件,用於在該裝置上安裝—元件處理常式,其中 該元件處理常式可運作以處理具有該所選^件類型之多個 心牛。該設備還包括:剖析構件1於剖析該動作清單, 以便獲得-用於識別該裝置所要處理之元件的元件/動作 對;以及下載構件,用於將該元件下栽至該裝置。該設備 O:\90\9O362.DOC -11 - 1329266 還包括:判定構件,用於判定該元件具有該所選元件類型; 以及啟動構件,用於使用具有該所選元件類型來啟動該元 件處理常式以處理該元件。 在一項具體實施例中,本發明提供一種包含指令之電腦 可讀型媒體,當一裝置中的處理邏輯執行該等指令時,則 會運作以自動處理該裝置上元件,其中該元件具有一所選 元件類型。該電腦可讀型媒體包括安裝指令,用於在該裝 置上安裝一元件處理常式,其中該元件處理常式可運作以 處理具有該所選元件類型之多個元件。該電腦可讀型媒體 還包括:剖析指令,用於刳析該動作清單,以便獲得一用 於識別該裝置所要處理之元件的元件/動作對;以及下载指 令,用於將該元件下載至該裝置。該電腦可讀型媒體還包 括:判定構件,用於判定該元件具有該所選元件類型丨以 及啟動指令,用於使用具有該所S元件類型纟啟動該元件 處理常式以處理該元件。 檢閱下文中提出的【實施方式】、【圖式簡單說明】及【申 請專利範圍】,將可明白本發明的其他觀點、優點及功能。 【實施方式】 接下來的詳細說明描述一種自動處理裝置上元件之系統 之具體實施例。該系統適合運用在任何類型的有線或無線 網路,包括(但不限於)通信網路、如網際網路等公共網路、 如虛擬私人網路(VPN)等私人網路 '區域網路、廣域網路、 長途電信網路或任何類型之資料網路。該系統也適用於配 合能夠下載及安裝元件之任何類型裝置—起使用。例如, 0;\90\90362. DOC -12- 1329266 該系統也適用於配合如下裝置-起使用:辦公室電腦、筆 5己型電腦以及手提布]雷賊^ / ., 于Μ電胳例如,攜帶型電腦、PDA或能 夠接收及安裝元件之任何類型裝置。 在:項或多項具體實施财,在㈣統與—正在該裝置 上執灯之執㈣段(nintime)環境互動,該執行階段環境係 用於(例如)藉由提供裝置特有資源的廣義啤叫來簡化裝置 操作。-種此類執行階段環境是美國加州^以,市 QUALCOMM,Inc.公司所開發的「‘町如此⑽ Environment for WirelessTM」(Brewtm)軟體平台。在接下 來的《尤月内谷中,饭设裝置正在執行如軟體平台等執 行階段環境。但是,該系統的一項或多項具體實施例適用 於配合其他類型執行階段環境一起使用,以便自動處理各 種有線及無線裝置上的元件。 圖1顯示一種自動處理裝置上元件之系統100之具體實施 例。該系統100包括一飼服器1 〇2、一資料網路1 〇4及一裝置 106。該資料網路1 〇4可能是允許在該伺服器i〇2與該裝置 106之間傳達資訊的任何類型有線或無線網路。例如,該資 料網路104可能是通信網路、廣域網路、虛擬私人網路或如 網際網路等公共網路。 在一項或多項具體實施例中,該系統運作以處理該裝置 106上的元件。例如,該伺服器1〇2包含多個元件112、一動 作清單110及一動作清單版本識別項1〇8及多個元件處理常 式120 »該版本識別項108識別該動作清單110的現行版本。 該動作清單110包含多筆元件/動作對,而每一元件/動作對 O:\90\90>62.DOC -13- 1329266 都包括一元件識別項及一動作識別項。該元件識別項是一 =於識別一特定元件的唯一項目ID。該元件識別項之一部 系用於識別該元件之版本。例如,該元件識別項是一連 串位7L,其中該等位元之一部分係用於識別該元件之版 本。該動作識別項識別該裝置106將執行之關於該識別之元 的動作,例如,安裝、更新、刪除、回呼、停用或其他 動作。 該等元件處理常式120被指派用於處理所選MIME類型。 例-4π 如 、 一項具體實施例中,該等元件處理常式被指派用 於處理具有所選ΜΙΜΕ類型之元件。可將該等元件處理常式 女裝在該裝置1〇6中,並且會在該裝置之作業系統登錄中註 冊該等元件處理常式。安裝後’就會啟動該等it件處理常 式以處理具有相對應格式類型之元件。 生在運作期間,該伺服器1〇2經由該資料網路1〇4將該動作 /月早版本識別項108傳輸至該裝置106。例如,該裝置106可 在開機序列期間聯繫該伺服器1〇2,並且該伺服器1〇2將該 動作π單版本識別項1〇8傳輸至該裝置106以作出回應。在 -項具體實施例中,當該伺服器1〇2具有可供下載的新版本 動作清單時,就會聯繫該裝置106。例如,在一項具體實施 例中*可取得—新版動作清單時,該伺服器1〇2就會將一 匕3該動作清單版本識別項1〇8的訊息傳送至該裝置。 該裝置106比較該動作清單版本識別項1〇8與一儲存之動作 月單版本識別項114(表示該裝置1〇6所要處理的最後動作 月單版本)。如果該下載之版本1〇8與該儲存之版本Η*為同O:\90\90362. DOC • 10 - 1329266 A method of a child, wherein the component has a selected component type. The method package (4) is provided with an installation-component processing routine, wherein the component processing routine is operable to process a plurality of components having the selected component type. The method also includes parsing the list of actions' to obtain a component/action pair for identifying the component to be processed by the device, and downloading the component to the device. The method also includes determining that the component has the selected component type, and using (10) selecting a component type to initiate the component processing routine to process the component: In a particular embodiment, the present invention provides an automatic A device that processes a component on a device, the component having a selected component type. The apparatus includes mounting logic for mounting a component processing routine on the device, wherein the component processing routine is operable to process a plurality of components having the selected component type. The apparatus also includes profiling logic for parsing the list of actions to obtain - a component/action pair for identifying the component to be processed by the device, and download logic for downloading the component to the device. The apparatus further includes: a logic to determine that the component has the selected component type; and a startup logic 1 to activate the component processing routine to process the component using the selected component type. - In the specific embodiment, the invention provides an apparatus for processing an apparatus on an automatic processing device, wherein the component has a selected component type. The apparatus includes a mounting member for mounting on the device - a component processing routine, wherein the component processing routine is operable to process a plurality of heartbeats having the selected component type. The apparatus further includes the profiling member 1 parsing the list of actions to obtain a component/action pair for identifying the component to be processed by the device, and a downloading member for downloading the component to the device. The apparatus O:\90\9O362.DOC -11 - 1329266 further comprises: a decision component for determining that the component has the selected component type; and an activation component for initiating the component processing using the selected component type The routine is to process the component. In a specific embodiment, the present invention provides a computer readable medium containing instructions that, when processed by a processing logic in a device, operate to automatically process components on the device, wherein the component has a The selected component type. The computer readable medium includes mounting instructions for mounting a component processing routine on the device, wherein the component processing routine is operable to process a plurality of components having the selected component type. The computer readable medium further includes: a parsing instruction for deciphering the action list to obtain a component/action pair for identifying a component to be processed by the device; and a download instruction for downloading the component to the Device. The computer readable medium further includes a decision component for determining that the component has the selected component type and a start command for activating the component using the S component type to process the component. Other aspects, advantages, and functions of the present invention will become apparent upon review of the <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; [Embodiment] The following detailed description describes a specific embodiment of a system for automatically processing components on a device. The system is suitable for use on any type of wired or wireless network, including but not limited to communication networks, public networks such as the Internet, private networks such as virtual private networks (VPNs), regional networks, WAN, long-distance telecommunications network or any type of data network. The system is also suitable for use with any type of device capable of downloading and installing components. For example, 0;\90\90362. DOC -12- 1329266 This system is also suitable for use with the following devices - use: office computer, pen 5 type computer and hand cloth] thief ^ / ., Μ Μ 例如, for example, A portable computer, PDA, or any type of device capable of receiving and mounting components. In the item: or a number of specific implementations, in (iv) the system is interacting with the nintime environment in which the system is used to provide, for example, a generalized beer called by providing device-specific resources. To simplify the operation of the device. - This type of execution phase environment is the "Bottom (10) Environment for WirelessTM" (Brewtm) software platform developed by QUALCOMM, Inc., California. In the next "Yueyue Valley", the rice-storage installation is performing an implementation phase such as a software platform. However, one or more embodiments of the system are suitable for use with other types of execution phase environments to automate the processing of components on a variety of wired and wireless devices. Figure 1 shows a specific embodiment of a system 100 for automatically processing components on a device. The system 100 includes a feeding device 1, a data network 1 and a device 106. The data network 1 〇 4 may be any type of wired or wireless network that allows information to be communicated between the server i 〇 2 and the device 106. For example, the data network 104 may be a communication network, a wide area network, a virtual private network, or a public network such as the Internet. In one or more specific embodiments, the system operates to process components on the device 106. For example, the server 1〇2 includes a plurality of components 112, an action list 110 and an action list version identification item 1〇8 and a plurality of component processing routines 120. The version identification item 108 identifies the current version of the action list 110. . The action list 110 includes a plurality of component/action pairs, and each component/action pair O:\90\90>62.DOC-13- 1329266 includes a component identification item and a motion recognition item. The component identification item is a unique item ID that identifies a particular component. One of the component identifications is used to identify the version of the component. For example, the component identification item is a series of bits 7L, wherein one of the bits is used to identify the version of the component. The action identification identifies an action that the device 106 will perform regarding the identified element, such as an installation, update, delete, call back, deactivation, or other action. These component processing routines 120 are assigned to process the selected MIME type. Example-4π As in a particular embodiment, the component processing routines are assigned to process components having the selected defect type. The components can be processed in the device 1〇6 and the component processing routines are registered in the operating system login of the device. After installation, these iterative processing routines are initiated to process components of the corresponding format type. During operation, the server 1〇2 transmits the action/monthly version identification item 108 to the device 106 via the data network 1〇4. For example, the device 106 can contact the server 1 〇 2 during the power-on sequence, and the server 〇 2 transmits the action π single-version identification item 〇 8 to the device 106 to respond. In the specific embodiment, the device 106 is contacted when the server 1〇2 has a new version of the action list available for download. For example, in a particular embodiment, when a new version of the action list is available, the server 1〇2 will transmit a message of the action list version identification item 1 to 8 to the device. The device 106 compares the action list version identification item 1 to 8 with a stored action month version identification item 114 (indicating the last action month version to be processed by the device 1〇6). If the downloaded version 1〇8 is the same as the stored versionΗ*
〇:V90\9〇362.D〇C -14 - 1329266 一版本,則裝置不需要執行關於該裝置上現有元件116的任 何安裝或變更動作。然而,如果該下載之版本1〇8與該儲存 之版本114為不同版本,則裝置1〇6知道需要額外的元件處 理動作。例如,該伺服器1〇2上可能有必須安裝在該裝置ι〇6 上的新元件。 一旦該裝置106偵測到有新版本之動作清單存在,則會將 一要求傳輸至該伺服器l02以獲得新版動作清單U〇。該伺 服器102將該動作清單11〇傳輸至該裝置1〇6以回應該要 求。接著,該裝置106處理該動作清單11(),以安裝、刪除 或處理在該動作清單丨丨〇中識別到的元件。 該裝置106處理該動作清單11〇的運作方式為,逐步執行 。亥動作α單11 〇中的每一元件/動作對,並且判定是否需要 執=關於每一元件的動作。例如,如果該動作清單指定需 要安裝或更新—元件,則該裝置lG6從該词服器⑽下載該 凡件112及任何其他必要檔案,並且在該裝置上安裝該 兀件。如果該動作清單11〇指定需要刪除一元件,則該裝置 ’于、該元件。以此方式,該裝置106處理該動作清單i i〇 I的每—元件/動作對’以便安裝 '更新、職該識別之元 ^。㈣作清單可能是任意長度,並且在處理該動作清單 後’該裝置106更新該儲存之動作清單版本識別項114,以 便儲存最近處理的動作清單版本。 f-項具體實施例中,該裝置106剖析該動作清單中 相關的Γ件/動作對’以便判定是否需要執行與—特定元件 作。例如,該裝置106可能已安裝—元件的最新版〇: V90\9〇362.D〇C -14 - 1329266 In version, the device does not need to perform any installation or modification of existing components 116 on the device. However, if the downloaded version 1〇8 is a different version than the stored version 114, then the device 1〇6 knows that additional component processing actions are required. For example, there may be new components on the server 1〇2 that must be mounted on the device 〇6. Once the device 106 detects that a new version of the action list exists, a request is transmitted to the server 102 to obtain a new version of the action list U. The server 102 transmits the action list 11 to the device 1 to respond to the request. Next, the device 106 processes the action list 11() to install, delete, or process the components identified in the action list. The device 106 processes the action list 11〇 in a step-by-step manner. Each element/action pair in the alpha action 11 is determined, and it is determined whether or not the action is required for each component. For example, if the action list specifies that an element needs to be installed or updated, the device lG6 downloads the item 112 and any other necessary files from the word server (10) and installs the element on the device. If the action list 11 specifies that a component needs to be deleted, then the device is '', the component. In this manner, the device 106 processes each component/action pair of the action list i i 〇 I to install the 'update, the identity element'. (d) The list may be of any length, and after processing the list of actions, the device 106 updates the stored action list version identification item 114 to store the most recently processed action list version. In the specific embodiment of the f-item, the device 106 parses the relevant element/action pair in the action list to determine if a specific component needs to be performed. For example, the device 106 may have been installed - the latest version of the component
O:\90\90362. OOC -15- 1329266 本,以至於該裝置不需要重新安裝該元件。在一項呈 施例中,該動作清單⑽中的元件識別項包含用於敎元件 版本的貝讯。例如,可將該版本資訊附加至該元件識別項 时端。該裝置⑽比較-儲存之元件版本118與該動 早no中下載的元件版本。如杲兮沒六 _ 讦版奉如果該儲存之元件版本與該下載 之疋件版本為相同版本’則該裝置不需要採取關於該元件 :任何動作。然而,如果該儲存之元件版本與該下載之元 件版本為不同版本’則該裝置1()6執行與該動作清單中之該 元件相關聯的動作。因此’該系統具高效率,因為該裝置 106僅處理新版本的元件。 在一項具體實施例中,該動作清單包括—元件/動作對, 用於識別要安裝在該裝置1G6上的—特定元件處理常式 120。該元件處理常式120是一種設計成處理具有一特定元 件類型之多個兀件的程式。例如’該元件類型可能是一種 用於識別檔案格式的MIME類型。在—項具體實施例中,該 兀件類型可被提供被加入至元件檀案之檔頭的—字元串。 基本上,該元件類型定義元件資料的處理方式。 為了回應剖析該元件/動作對,該裝置從該伺服器102下 載該π件處理常式12〇 ’ 1且將該元件處理常式12〇安裝為 該裝置中安裝之元件處理常式122的一部分。當將該元件處 理常式12G安裝在該裝置1G6中時,就會在該裝置之作業系 統登錄中註冊並且啟動該元件處理常式12〇,以處理具有該 相對應元件類型之多個元件。例如,該作業系統登錄識別 要用來處理元件類型(如URL、文件、影像或其他資料樓案)O:\90\90362. OOC -15- 1329266, so that the device does not need to reinstall the component. In one embodiment, the component identification item in the action list (10) contains the Beckun for the component version. For example, the version information can be attached to the component identification term. The device (10) compares the stored component version 118 with the component version downloaded in the early no. If there is no six _ 讦 奉 if the stored component version is the same version as the downloaded ’ version, then the device does not need to take the component: any action. However, if the stored component version is a different version than the downloaded component version, then device 1() 6 performs the action associated with the component in the action list. Thus the system is highly efficient because the device 106 only processes new versions of the components. In a specific embodiment, the list of actions includes a component/action pair for identifying a particular component processing routine 120 to be installed on the device 1G6. The component processing routine 120 is a program designed to process a plurality of components having a particular component type. For example, the component type may be a MIME type used to identify the file format. In a particular embodiment, the component type can be provided as a string of characters to be added to the header of the component. Basically, this component type defines how the component data is processed. In response to parsing the component/action pair, the device downloads the π-piece processing routine 12〇' 1 from the server 102 and installs the component processing routine 12〇 as part of the component processing routine 122 installed in the device. . When the component processing routine 12G is installed in the apparatus 1G6, the component processing routine 12 is registered in the operating system registration of the apparatus to process a plurality of components having the corresponding component type. For example, the operating system login identification is used to process component types (such as URLs, files, images, or other data structures).
〇:W\90W2D〇C 16- 1329266 的處理常式。 :4件4理常式12G安裝在 理常式120運作w + T仅,忒兀件處 -項且體^處理具有該所選元件類型之任何元件。在 麥之元件#⑽中’該线運作以安裝1於處理尚未安 =L處理常式。例如,該系統執行以上步驟, 便自動處理—裝置上元件。 1.在該裝置上容驻 一 t丄各 型。 *裝-疋件處理常式,以處理-特定元件類 2. 將-具有該特定元件類型之資料元件下載至該裝置。. 3. 使用該元件處理常式來處理該資料元件。 一以此方式’該系統運作成允許從該飼服器收下載新版本 兀件並且在該裝置106上處理該等元件。該等元件可包含用 於處理所選元件類型的多個元件處理常式。若要在該裝置 上處理-種新元件類型,首先在該作業系統登錄中安裝一 新的元件4理常式’並且之後啟動該元件處理常式以處理 新元件。 圖2顯不一種裝置2〇〇的功能圖,該裝置包含用於自動處 理該裝置200上元件的系統之具體實施例。該裝置包括處理 邏輯208、比較邏輯206、功能邏輯2M、更新版本邏輯224、 一儲存之動作清單版本識別項(ALVI)2〇4、多個元件版本識 別項(CVI)212及多個安裝之元件226。可運用硬體、軟體或 軟體體組合來實施所描述之該2〇〇提供的邏輯及功能。例 如,在一項或多項具體實施例中,圖2所示之功能組件包括 一 CPU、一處理器、閘陣列、硬體邏輯、記憶體元件、虛 O:\9(n90362. DOC -17- 1329266 擬機器、軟體及/或任何軟硬體組合。因此,該處理邏輯2〇8 廣泛包括用於執行機器可讀型指令的邏輯,以便執行本文 中所描述的功能。應注意,該裝置2〇〇僅僅是一具體實施例 之圖例說明’並且可變更、增加或重新配置裝置元件,而 不會脫離本發明的範疇。 圖3顯不一種操作一輸入裝置(例如裝置200)之方法300的 具體實施例,以便提供一種自動處理該裝置2〇〇上元件的系 統。基於簡明清楚之目的’將參考圖2所示之裝置2〇〇來說 明該方法300。進一步假設,該裝置2〇〇正在經由一資料網 路與一下载伺服器進行安全通信,如圖1所示。 在步驟302,該裝置從該下載伺服器獲得一動作清單版本 識別項。例如,該裝置經由一資料網路與該下載伺服器進 行通信,並且該下載伺服器將該動作清單版本識別項傳輸 至該裝置,如圖2中的202所示。 在步驟304,執行一項測試,以便判定該下載之動作清單 版本識別項是否不同於該裝置所要處理之最新動作清單相 關聯的-儲存之版本識別項。例如,將該下載之版本識別 項202與該储存之版本識別項2〇4輸入至該比較邏輯鹰,以 便比較該等兩個識別項搬,以判^是否為相同版本。如果 該等兩個識別項為相同,則該方法返回步驟302,以在其他 時間獲得新版本的動作清單。如果該等兩個識別項不同 (Diff) ’則該方法進行到步驟3〇6。 在/驟3G6 ’該裝置從該下㈣服㈣取該動作清單 如’經由該資料網路從該词服器下載該動作清單21〇至處理〇: The processing routine of W\90W2D〇C 16- 1329266. : 4 pieces of the 4th routine 12G are installed in the routine 120 to operate w + T only, the item - item and the body ^ handles any element having the selected element type. In Mai's component #(10), the line operates to install 1 in the process of not processing the =L processing routine. For example, the system performs the above steps and automatically processes the components on the device. 1. A variety of types are accommodated on the device. *Load-device processing routine to process - specific component classes 2. Download - data components with this particular component type to the device. 3. Use the component processing routine to process the data component. In this manner, the system operates to allow downloading of new versions of the device from the feeder and processing the components on the device 106. The elements can include a plurality of component processing routines for processing the selected component types. To process a new component type on the device, first install a new component in the operating system login and then start the component processing routine to process the new component. Figure 2 shows a functional diagram of a device 2 that includes a specific embodiment of a system for automatically processing components on the device 200. The apparatus includes processing logic 208, comparison logic 206, function logic 2M, update version logic 224, a stored action list version identification item (ALVI) 2〇4, a plurality of component version identification items (CVI) 212, and a plurality of installations. Element 226. The hardware, software, or combination of software can be used to implement the logic and functionality provided by the two described. For example, in one or more specific embodiments, the functional components shown in FIG. 2 include a CPU, a processor, a gate array, hardware logic, a memory component, and a virtual O:\9 (n90362. DOC -17- 1329266 A machine, software, and/or any combination of hardware and software. Therefore, the processing logic 2 8 broadly includes logic for executing machine readable instructions to perform the functions described herein. It should be noted that the device 2 〇〇 is merely illustrative of a particular embodiment and may change, add or reconfigure device components without departing from the scope of the invention. Figure 3 illustrates a method 300 of operating an input device (e.g., device 200). DETAILED DESCRIPTION OF THE INVENTION In order to provide a system for automatically processing components on the device 2, the method 300 will be described with reference to the device 2 shown in Figure 2 for the sake of brevity and clarity. Further assume that the device is A secure communication is being made with a download server via a data network, as shown in Figure 1. At step 302, the device obtains an action list version identification item from the download server. For example, the device Communicating with the download server via a data network, and the download server transmits the action list version identification item to the device, as shown at 202 in Figure 2. At step 304, a test is performed to determine Whether the downloaded action list version identification item is different from the stored version identification item associated with the latest action list to be processed by the device. For example, the downloaded version identification item 202 and the stored version identification item 2〇4 are input. To the comparison logic eagle, in order to compare the two identification items to determine whether it is the same version. If the two identification items are the same, the method returns to step 302 to obtain a new version of the action at other times. If the two identification items are different (Diff)' then the method proceeds to step 3〇6. At /3G6 'the device takes the action list from the next (four) service (four), such as 'via the data network from the The word server downloads the action list 21〇 to the processing
O:\90\90362DOC -18- 1329266 邏輯208。 在步驟308,該裝置剖析該動作清翠中的第一筆元件/動 作對,㈣處㈣動作清m該處理邏輯繼運作以 處理該下載之動作清單21G,以剖析多筆元件/動作對。 在步驟310,執行一項測試,以便判定需對目前處理令的 -件/動作對採取的動作(若有的話)。在一項具體實施例 令,該袭置進行到步驟312以自動執行該動作。然而,這會 導致在該裝置上重新安裝現有的元件β在另一項具體實施 例中,檢查該元件之版本以判定是否需要採取動作。例如, 如果該動作為「安裝」該元件,則會檢本該元件之版本, 以查看該裝置是否具有目前安裝之元件的版本。以此方 式,該方法運作成避免重新安袭該裝置上已安裝的元件。 例如’該處理邏輯20請取一儲存之元件版本識別項212, 並且比較在該動作清單中所識別的元件版本。在—項具體 實細例令,會將該元件版本併入該動作清單中所提供的元 件識別項。如果這兩個元件版本相同,則該裝置不會採取 關_儿件的進—步動作’並且該方法進行到步驟416。如 果k兩個%件版本列,職處理邏輯旗運作成執行關於 該元件的動作’並且該方法進行到步驟312。 在夕驟3 12 ’執行與該目前元件/動作對中之元件相關聯 的動作以變更該識別之元件的狀態。例如,該處理邏輯 2〇8運作成控制該功能邏輯214,以執行安裝、更冑、刪除、 啟動、停用 '回呼或變更該識別之元件的狀態。例如,可 執订軟口令’以便從該裝置刪除該元件,但不會移除相關 1329266 聯的:貝料及/或授權資訊。例如,如果動作是安裝或更新該 兀件’則«置處理邏輯纖運作錢由該㈣網路從訂 載㈣器下載該元件222(或更新版本)。接著,將該下載之 兀件安裝為-安裝之元件226。該處理邏輯2〇8可執行任何 類型的安裝或更新程序,以將該下載之元件如安裝或更新 為該安裝之元件226。如果動作是刪除—元件,則該處理邏 輯208控制刪除邏輯22G,以從該等安裝之元件咖刪除該識 別之元件。雖然圖2及圖3中未料,但是實際上可執行關 於該元件的任何類型動作,例如在該裝置上安裝、更新、 刪除、回呼、啟動、撤銷該元件或變更該元件之狀態。 在步驟314,更新一元件版本清單,以反映已安裝或更新 之元件的新版本’或反映已刪除之元件。例如該處理邏 輯208控制該更新版本邏輯224,以使用關於目前處理之元 件的新資訊,來更新該儲存之元件版本識別項212。 在步驟316’執行一項測試,以便判定是否已處理該動作 清單中的所有元件/動作對。如果已處理所有元件/動作對, 則該方法進行到步驟320。如果尚未處理所有元件/動作 對則該方法進行到步驟318,以便存取要在步驟3 1 〇中處 理的下一元件/動作對。該動作清單21〇可能是任何長度, 並且内含所要處理的任何數量之元件/動作對。 在步驟320’更新該裝置中儲存之動作清單版本識別項。 例如,該處理邏輯208控制該更新版本邏輯2.24,以使用與 最近處理之動作清單相關聯的識別項,來更新該儲存之動 作清單版本識別項204。因此,除非可取得新版本的動作清 O:\90\90362.DOC -20- 1329266 早,否則該系統不會運作以處理另—動作清單。 括=具體實施例中,自動處理該裝置上元件之系統包 ^了 4型媒體上健存的程式指令,當該處理邏輯208 =:指令時,則會提供本文中所說明的功能。例如, “”從如下之電腦可讀型媒體載入至該裝置2〇〇:軟碟 CD_R〇M、記憶卡、快閃記憶體、“Μ、麵或經由 "面連接至裝置200的任何其他 讀型媒體。在另一項且體膏4體裝置或電腦可 , #具體實施例中,會經由-資料網路以 從-由面連接至該裝置2〇〇的網路資源下載指令至 置細。當該處㈣輯執行料指令時,就會提供如本 =明之自動處理裝置上元件之系統的一項或多項具體 霄施例。 應注意,該方法300僅僅是一具體實施例之圖例說明,並 且:變更、增加或重新配置方法元件,而不會脫離本發明 的範嘴。 圖镜示-種操作一輪入裝置之方法的具體實施例, 以便處理用於操控特定元件類型所指派的多個元件處理常 式。基於簡明清楚之目的,將參考圖2所示之裝置2〇〇來說 明該方法400。假設使用該方法3〇〇來下 處理元件,如上文所述。一進一步描述 多個兀件的運作方式’而該等處理之元件都屬於已指派多 個元件處理常式操控的特定元件類型。在一項或多項具= 實施例中,該處理邏輯2〇8於程式指令執行期間執行下列 法步驟。 ’方 O-\90\9O3f52.DOC -21 - 1329266 下載伺服器獲得之一元件/ 步驟306所述來獲得該動作 在步驟402,該系統剖析從— 動作對。例如,已按照圖3中之 清單。 在步驟404,執行一項測 唄則忒,以便判定需對目前處理中的 兀件/動作對採取的動作( ^ 有的話)。例如,如果比較該元 件/動作對中的元件版本盘一 ^ , μ 儲存之元件版本,並且如果該 專兩個版本為不同版本, 對應動作。 關於所朗之元件的相 在步驟406,假設採取某動 乍,執仃一項測試,以便判定 該識別之元件是否是—元件虛 牛處理吊式。元件處理常式是一 種設計成操控—㈣元件類_程式。如㈣定該元件是 兀件處理常式’則該方法進行到步驟彻。 在步驟408,將該識別之分放+ „ 之几件處理常式下載至該裝置。例 如’可從一伺服器(例如,伺 服益102)下載該元件處理常式 228 〇 在步驟川,將該元件處理常式安裝在該裝置上。例如, 在該裝置之作業线登錄中註冊該元件處理常式,以當做 用於操控具有一特定元件類型的多個元件。在一項且體實 施例中’該作業系統登錄屬於該處理邏輯之—部分“主 冊後,該元件處理常式22δ變成該裝置2〇〇上已安裝之元件 處理常式230的一部分。 在步驟412,在位於該裝置上的該儲存之元件版本識別項 清單中更新該安裝之元件處理常式的版本識別[例如, 該更新版本邏輯224使用目前安裝之元件處理常式228的版O:\90\90362DOC -18- 1329266 Logic 208. In step 308, the device parses the first component/action pair in the action clear, and (4) the action logic clears the process logic to process the downloaded action list 21G to parse the plurality of component/action pairs. At step 310, a test is performed to determine the action (if any) that needs to be taken on the item/action pair of the current processing order. In a specific embodiment, the attack proceeds to step 312 to automatically perform the action. However, this can result in reinstalling the existing component on 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" the component, the version of the component will be checked to see if the device has a version of the currently installed component. In this way, the method operates to avoid re-attacking the installed components on the device. For example, the processing logic 20 takes a stored component version identification item 212 and compares the component versions identified in the action list. In the specific case, the component version will be incorporated into the component identification provided in the action list. If the two component versions are the same, then the device does not take the advance action of the device and the method proceeds to step 416. If k two % piece versions are listed, the job processing logic flag operates to perform an action on the element ' and the method proceeds to step 312. The action associated with the component in the current component/action pair is performed at a later step 3' to change the state of the identified component. For example, the processing logic 〇8 operates to control the function logic 214 to perform the installation, switch, delete, start, disable, or disable the status of the identified component. For example, a soft password can be issued to remove the component from the device, but the associated 1329266: beaker and/or authorization information is not removed. For example, if the action is to install or update the component, then the processing logic fiber is operated by the (4) network to download the component 222 (or newer version) from the carrier (four). Next, the downloaded component is mounted as an -mounted component 226. The processing logic 〇8 can execute any type of installation or update program to install or update the downloaded component as the installed component 226. If the action is a delete-element, then the processing logic 208 controls the delete logic 22G to delete the identified component from the installed component coffee. Although not apparent in Figures 2 and 3, virtually any type of action on the component can be performed, such as installing, updating, deleting, calling back, starting, revoking, or changing the state of the component on the device. At step 314, a list of component versions is updated to reflect the new version of the installed or updated component' or to reflect the deleted component. For example, the processing logic 208 controls the updated version logic 224 to update the stored component version identification 212 using new information about the currently processed component. A test is performed at step 316' to determine if all of the component/action pairs in the action list have been processed. If all component/action pairs have been processed, then the method proceeds to step 320. If all component/action pairs have not been processed, then the method proceeds to step 318 to access the next component/action pair to be processed in step 3 1 . The Action List 21 can be of any length and contains any number of component/action pairs to be processed. The action list version identification stored in the device is updated at step 320'. For example, the processing logic 208 controls the updated version logic 2.24 to update the stored action list version identification item 204 using the identification associated with the most recently processed action list. Therefore, unless a new version of the action is cleared O:\90\90362.DOC -20- 1329266, the system will not operate to process the other action list. In the specific embodiment, the system that automatically processes the components on the device includes program instructions that are stored on the type 4 media. When the processing logic 208 =: instructions, the functions described herein are provided. For example, "" is loaded from the following computer readable media to the device 2: floppy CD_R〇M, memory card, flash memory, "Μ, face or via " face to any device 200 Other reading media. In another embodiment, the body cream device or the computer may, in a specific embodiment, download the command from the network resource connected to the device through the data network. When one (4) is executed, a one or more specific embodiments of the system for the components on the automatic processing device of the present invention are provided. It should be noted that the method 300 is only a specific embodiment. The illustration illustrates, and: alters, adds, or reconfigures a method component without departing from the scope of the invention. The figure illustrates a specific embodiment of a method of operating a wheeled device to handle the assignment of a particular component type for manipulation Multiple component processing routines. For purposes of simplicity and clarity, the method 400 will be described with reference to the apparatus 2 shown in Figure 2. It is assumed that the method is used to process the components as described above. Describe multiple defects The operation of the piece 'and the components of the process belong to a specific component type that has been assigned multiple component processing routines. In one or more of the embodiments, the processing logic 2〇8 is executed during execution of the program instructions The following steps are performed: 'Parts O-\90\9O3f52.DOC-21- 1329266 Download the server to obtain one of the components/step 306 to obtain the action. In step 402, the system parses the slave-action pair. For example, The list in Figure 3. At step 404, a test is performed to determine the action (^ if any) to be taken on the currently processed component/action pair. For example, if the component/action pair is compared The component version in the device disk ^, μ stores the component version, and if the two versions are different versions, the corresponding action. About the phase of the component of the device in step 406, assume that a certain action is taken, and a test is performed. In order to determine whether the identified component is a component virtual cattle processing crane. The component processing routine is a design to operate - (4) component class _ program. If (4) the component is a component processing routine 'the method The process proceeds to step 408. At step 408, the processing routines of the identified split + „ are downloaded to the device. For example, the component processing routine can be downloaded from a server (e.g., servo 102). In the step, the component processing routine is installed on the device. For example, the component processing routine is registered in the line registration of the device as if it were used to manipulate a plurality of components having a particular component type. In an embodiment, after the operating system is registered as part of the processing logic, the component processing routine 22δ becomes part of the component processing routine 230 installed on the device 2〇〇. Step 412: Update the version identification of the installed component processing routine in the stored component version identification list located on the device. [For example, the updated version logic 224 uses the currently installed component processing routine 228 version.
0-\90\90362.DOC -22- 1329266 本,來更新該儲存之元件版本識別項212。接著該方法400 進行到步驟402以剖析下一元件/動作對。 接下來的发明内谷假設步驟4〇2和步驟剖析一用於識 別所要處理之該裝置上元件的後續元件/動作對。 在步驟406’執行一項測試,以便判定該識別之元件是否 疋-兀件處理常式。如果該元件不是―元件處理常式,則 該方法進行到步驟414。 在步驟414,將該元件下載至該裝置。例如,該處理邏輯 208從一伺服器下載該元件(如圖2中的222所示)。 在步驟416,判疋該元件的格式類型。例如,該元件可具 有一屬於其他格式的所選MIME類型,用以指示該元件中的 資訊格式及/或應如何處理該資訊。 在步驟418,啟動一與該元件類型相關聯之元件處理常 式,以便處理該元件。例如,使用該作業系統登錄來判定 應使用哪一個元件處理常式來處理該所選元件類型。啟動 藉由該登錄所識別之元件處理常式來處理該元件。例如, 該處理邏輯208啟動該等安裝之元件處理常式23〇之一來處 理該元件》 在步驟420 ’該啟動之元件處理常式處理該元件。例如, 該元件處理常式可運作成安裝、刪除、更新、啟動、合併 資料或在該裝置上變更元件之狀態。 在步驟422’使用新的元件版本來更新該裝置中儲存之元 件版本識別項。例如,該更新版本邏輯224更新該裝置上儲 存的元件版本識別項212。接著該方法繼續進行,以在步驟 O:\90\9O362. DOC -23- 1329266 402處理下—元件/動作對。 ^此’該方法彻運作成下載及安裝—元件處理 :使用該元件處理常式來處理—下載之元件。該^件产接 ㊉式被設計成處理—特定元件類型 处理 :常式時,就會在該裝置之登錄中註冊該=處 -在。亥裝置上處理-具有該特^類型的元件時,就會二 =登錄來啟動該元件處理常式,以執行關於該元件二 處理。接著,更新該裝置上的該元件版本識別項。 在另一項具时施财,使料同的動作清單, 件處理常式228及相關聯之元件下鼓該裝置2⑼。例如^ 使用一第-動作清單來下載及安裝該元件處理常式券 用-第二動作清單來處理該元件,其Μ前安裝的 理常式會處理該元件^ 干處 在另一項具體實施例中,使用任何安裝技術在該裝置咖 上安裝該元件處理常式咖例如,可使用—分離於該 飼服器的傳輪來安裝該元件處理常式,或可從—本機系统 或裝置來安裝該元件處理常式。然而,一旦已安裝該元件 處理常式’就會在作業系統登錄中註冊該元件處理常式以 處理相對應之元件。 圖5顯示-種操作-輸人裝置之方法5⑽的具體實施例, 以便處理所指定操控指定元件類型的多個元件處理常式。 基於簡明清楚之目的’將參考圖2所示之裝置2⑻來說明該 方法500。假設使用該方法綱來下載一動作清單並且處理 元件,如上文所述。該方法500進一步描述該系統處理多個 〇:W〇W〇362.D〇C •24- 1329266 元件處理常式的運作方式,而 ,“一 %該4處理常式已被指派操控 多種特定元件類型。在—項或多 _ 項〇體實施例中,該處理 邏輯2 0 8於程式指令執行期間執 j r別方法步驟。 在步驟502,剖析一動作清單以 _ 種·彳于要在該裝置上處理的 一元件/動作對。在步驟5〇4,執 巩仃一項測試,以便判定需 對所識別之元件採取的任何動作 有的話)。如果所需之動 作疋在該裝置上變更該識別之元 到步驟5。6。 件的狀癌,則該方法進行 在步驟506,判定處理該元件 丨卞听而的7L件處理常式。例 如,在一項具體實施例中,該動作、.主s 士 茨劲作/月早中的元件識別項包 3—用於識別元件類型的「類型」識別項。該處理邏輯· 使用該「類型J識別項來判定處理該元件所需的一 理常式。 在步驟508,執行-項測試,以便判定該袭置上是否已存 在該所需之7G件處理常式。例如,該處理邏輯檢查該等 安裝之S件處理常仏26,以便判定是否已安裝該所需之元 件處理㊉式。如果已安裝該所需之元件處理常式,則該方 法進行到步驟516。如果未安農該所需之元件處理常式°,則 該方法進行到步驟5 1 0。 在步驟別,將該所需之元件處理冑式下載至該裝置。例 如,在一項具體實施例中,該處理邏輯2〇8從—伺服器下載 該το處理常式228。可使用任何技術將該元件處理常式下載 至該裝置。 在步驟512,將該元件處理常式安裝在該裝置上。例如,0-\90\90362.DOC -22- 1329266, to update the stored component version identification item 212. The method 400 then proceeds to step 402 to dissect the next component/action pair. The next invention valley assumes that step 4〇2 and the step parsing a subsequent component/action pair for identifying the component on the device to be processed. A test is performed at step 406' to determine if the identified component is a 疋-兀 processing routine. If the component is not a component processing routine, then the method proceeds to step 414. At step 414, the component is downloaded to the device. For example, the processing logic 208 downloads the component from a server (shown as 222 in Figure 2). At step 416, the format type of the component is determined. For example, the component may have a selected MIME type that belongs to other formats to indicate the format of the information in the component and/or how the information should be processed. At step 418, a component processing routine associated with the component type is initiated to process the component. For example, the operating system is logged in to determine which component processing routine should be used to process the selected component type. The component is processed by the component processing routine identified by the login. For example, the processing logic 208 initiates one of the installed component processing routines 23 to process the component. The component processing routine in step 420' processes the component. For example, the component processing routine can operate to install, delete, update, launch, merge data, or change the state of components on the device. The new component version is used in step 422' to update the component version identification stored in the device. For example, the updated version logic 224 updates the component version identification 212 stored on the device. The method then proceeds to process the component/action pair in step O:\90\9O362.DOC-23-1329266402. ^This method works as a download and install - component processing: processing the routine using this component to process the downloaded component. This type of production is designed to be processed - specific component type processing: In the normal form, it will be registered in the registration of the device - at. Processing on the device - with this type of component, the second = login to start the component processing routine to perform the second processing on the component. The component version identification on the device is then updated. In another time, the same action list, the processing routine 228 and the associated components are used to drum the device 2 (9). For example, using a first-action list to download and install the component processing regular coupon-second action list to process the component, the current installation routine will handle the component ^ in another implementation In an example, the component is installed on the device using any mounting technique. For example, the component can be installed using a transfer wheel that is separate from the feeder, or can be from the local system or device. To install the component processing routine. However, once the component processing routine has been installed, the component processing routine is registered in the operating system login to process the corresponding component. Figure 5 shows a specific embodiment of a method 5 (10) of the operation-input device for processing a plurality of component processing routines for the specified manipulation of the specified component type. The method 500 will be described with reference to the apparatus 2 (8) shown in Fig. 2 for the sake of conciseness. Assume that the method outline is used to download an action list and process components as described above. The method 500 further describes how the system handles multiple 〇:W〇W〇362.D〇C •24-1329266 component processing routines, while "one percent of the four processing routines have been assigned to manipulate a plurality of specific components In the - or more _ 〇 embodiment, the processing logic 208 executes the jr method step during execution of the program instruction. In step 502, parsing an action list to _ 彳A component/action pair processed. In step 5〇4, a test is performed to determine if any action is required to be performed on the identified component. If the desired action is changed on the device The identification element proceeds to step 5. The condition of the piece of cancer, the method proceeds to a step 506 of determining a 7L piece of processing routine for processing the element. For example, in one embodiment, the action , s s sssssssssssssssssssssssssssssssssssssssssssssssssssss The processing logic uses the "type J identification item to determine the rationale required to process the element. In step 508, the - item test is performed to determine if the required 7G piece of processing already exists on the attack. For example, the processing logic checks the S-processing routines 26 of the installations to determine if the required component processing tens have been installed. If the required component processing routines have been installed, the method proceeds to Step 516. If the required component processing routine is not used, the method proceeds to step 5 10 0. In the step, the required component processing is downloaded to the device. For example, in an item In a particular embodiment, the processing logic 2〇8 downloads the το processing routine 228 from the server. The component processing routine can be downloaded to the device using any technique. In step 512, the component processing routine is installed at On the device. For example,
O:\90\90362.DOC -25- 1329266 在登錄中註冊該元件處理常式,以便可啟動該元件處理常 式來處理所選之元件類型。在步驟514,更新所儲存之處理 常式版本。例如’該更新版本邏輯224更新該儲存之元件版 本識別項212。然後,該方法進行到步驟5丨6。 在步驟516,將該識別之元件下載至該裝置。例如,該處 理邏輯208從一下載伺服器下載識別之元件。 在步驟518,啟動最新安裝的元件處理常式來處理該下載 之元件。例如,該處理邏輯2〇8使用該登錄來判定所要啟動 的該等安裝之元件處理常式23〇之一來處理該元件。結果, 將啟動最新安裝的元件處理常式來處理該元件。 在步驟520’該元件處理常式處理該裝置上的元件,以在 該裝置上變更該I件之狀態。例如,該元件處理常式可運 作成安裝、刪除、更新、啟動、合併資料或變更該裝置上 元件之狀態。 在/驟522,更新所儲存之元件版本識別項。例如,該更 新版本邏輯224更新該儲存之元件版本識別項加。接著今 方法進行到步驟502以剖析其他元件/動作對。 人 3叫運作成判定是否 理堂彳*忐 u。— π高弋兀件處 式,:會::一元件。如果該裝置上未安裝該元件處理臂 續使用下載飼服器下載該元件處理,以及安裝且種 續使用該疋件處理常式來處理一下載之 常式被設計成處理一特定元件類型,並且告;:—3 理常式時,就會在該裝置 田女件處 當在該裝置D 冊該元件處理常式。 理-具有該特定類型的元件時,就會使用 〇:\9〇\9〇j62.〇〇c -26- 1329266 =錄來啟動該元件處理常式,以執行關於該㈣的 處理。接著,更新該裝置上的該元件版本識別項。要 :示在自動處理裝置上元件之系統的具體實 作』間’ ;|於—下載伺服器與—裝置之間所發生的 例如’ I所示之該裝置1Q6與該伺服器iG2 生該交易600。 曰發 在自動處理開始時’該裝置1()6向_服器⑽要求 作清單的最新版本朗項,如时的術所心該動作清單 包含多個元件/動作對’用於播述該裝置應執行之關於= 識別之元件的動作。可週期性變更或更新該動作清單,並 且該動作冑單版本識別項識別該動作清單的現行版本。 該飼服器H)2會傳輸現行動作清單的版本識別項,以回應 該裝置1G2之要求’如圖中的6()4所示。接收到該動作清單 版本識別項之後,該裝置比較該識別項與一儲存之動作清 單版本識別項。如果這兩個元件版本相同,則該裝置不會 抓取進一步動作。如果這兩個版本識別項不同,則該裝置 1〇6向該词服器102要求一新版動作清單,如圖中的6〇6所 示。 該伺服器102會傳輸新版動作清單,以回應該裝置1〇6之 要求,如圖中的608所示。該裝置1〇6處理該動作清單中的 母一元件/動作對,以便判定是否要安裝、更新、刪除或變 更一特定元件之狀態。如果該裝置1〇6判定需要處理—特定 元件’則該裝置106向該伺服器1 〇2要求該元件(或更新版 本),如圖中的610所示。 0:\90\9M62.DOC -27- D^266 。玄飼服益102將該要求之元件傳輸至該裝置i〇6以回應今 要求。該裝置1〇6接收該元件並且視需要處理該元件β = 件可具有該裝置本機儲存的1件版本識別項。在該 處理該元件後,就舍爭紅 沈會更新該7C件版本識別項。該裝置1〇6 析:個動作^單並且按需要自該词服器⑽掏取所有必要 的几件之後’該裝置1()6使用_處理的動作清單版本,來 更新本機儲存之動作清單版本朗項^因此,除非自該 飼服器下載的動作清單版本不同於該裝置上所儲存之版 =’否則該裝置⑽不處理來自該伺服器⑽的其他動作产 單〇 圖7顯示運用在一種自動處理裝置上元件的系統中之動 作清皁700之具體實施例。該動作清單7〇〇包含一動作清單 版本識別項702,其後接著多個元件/動作對(7〇4, 7〇6):例 如,7C件/動作對704包含一元件識別項及一相制動作。 在-項具體實施例中,該元件識別項還包含一元件版本識 別項及-「類型」識別項。使用該元件識別㈣,就能夠 使用元件版本來判定裝置上目前是否已有該元件q吏用該 類型識別項來標示元件類型’並且判定處理該元件所需的 元件處理常式。該動作可能是安裝、更新、刪除或任何其 他類型之動作,以在該裝置上變更該元件之狀態。可基於 安全傳輸及/絲認之目的,❹任何適合的格式來編碼該 動作清單中的資訊,並且該元件識別項及該動作識別項可 能屬於任何類型。在一項具體實施例中,該元件/動作對704 識別要在該裝置上安裝的-元件處理常式,並且該元件/動 O:\90\90362.DOC -28- 丄 作對識㈣元件處㈣柄要處判 據此’雖然本文中已圖 , 口鮮及栺述用於說明 上元件之系統的—項或多 '1 行各# # f ifb 、/ 施例,但是應知道可進 :各種變更’而不會脫離其精神或基本特徵。因此,本文 y mm 曰係〜作4本發明料之例證,而 不疋限制本發明範疇,本 中提出。 發月乾可係在隨附申請專利範圍 【圖式簡單說明】 從刖文中參考附圖解說的本發明 出的觀點及本文所描述1 5 ,將可明白提 Τ Γ田述之具體實施例的附帶優點,i中: 圖1顯示一種自動處理裝置上元件之系統之具體實施例; 圖2顯不—種裝置的功能圖,該裝置包含用於自動處理裝 置上元件之系統之具體實施例; 圖3顯不-種操作一輸入裝置之方法的具體實施例,以便 提供一種自動處理裝置上元件之系統; 圖4顯不-種操作一輪入裝置之方法的具體實施例,以便 處理用於操控特定元件類型所指派的多個元件處理常式; 圖5顯不-種操作一輸入裝置之方法的具體實施例,以便 處理用於操控特定元件類型所指派的多個元件處理常式; 圖6顯示在自動處理裝置上元件之系統的具體實施例運 作期間’介於-T載伺月艮器與-裝置之間所#生的交易; 以及 圖7顯示運用在一種自動處理裝置上元件之系統中之動 作清單之具體實施例。O:\90\90362.DOC -25- 1329266 Register the component processing routine in the login so that the component processing routine can be started to process the selected component type. At step 514, the stored version of the process routine is updated. For example, the updated version logic 224 updates the stored component version identification 212. Then, the method proceeds to step 5丨6. At step 516, the identified component is downloaded to the device. For example, the processing logic 208 downloads the identified component from a download server. At step 518, the newly installed component processing routine is initiated to process the downloaded component. For example, the processing logic 2〇8 uses the login to determine one of the installed component processing routines 23 to be initiated to process the component. As a result, the newly installed component processing routine will be started to process the component. The component processing routine processes the components on the device at step 520' to change the state of the I component on the device. For example, the component processing routine can be implemented to install, delete, update, launch, merge data, or change the state of components on the device. At /step 522, the stored component version identification is updated. For example, the updated version logic 224 updates the stored component version identification plus. The method then proceeds to step 502 to dissect the other component/action pairs. The person 3 is called to operate to determine whether or not it is 彳*忐 u. — π 高弋兀件式,:会::一元件。. If the component is not mounted on the device, the processing arm continues to download the component processing using the downloading device, and the routine is installed and used to process a download. The routine is designed to process a particular component type, and告;:—3 When the routine is used, the component processing routine is used in the device's D-book. When there is a component of this particular type, 元件:\9〇\9〇j62.〇〇c -26- 1329266=recording is used to start the component processing routine to perform the processing on (4). The component version identification on the device is then updated. To: show the specific implementation of the system on the component of the automatic processing device; | the download device and the device, for example, the device 1Q6 shown in 'I' and the server iG2 generate the transaction 600. When the automatic processing starts, the device 1 () 6 requests the latest version of the list to the server (10), and the action list contains a plurality of component/action pairs for broadcasting the The action that the device should perform regarding the = identified component. The action list can be changed or updated periodically, and the action version version identification identifies the current version of the action list. The feeder H) 2 transmits the version identification of the current action list in response to the request of the device 1G2 as shown by 6() 4 in the figure. After receiving the action list version identification item, the device compares the identification item with a stored action list version identification item. If the two components are the same version, the device will not grab further actions. If the two version identification items are different, the device 1〇6 requests the word server 102 for a new version of the action list, as shown in Fig. 6-6. The server 102 transmits a new version of the action list to respond to the requirements of the device 1〇6, as shown at 608 in the figure. The device 1〇6 processes the parent-element/action pair in the action list to determine if the state of a particular component is to be installed, updated, deleted, or changed. If the device 106 determines that a process is required - a particular component, then the device 106 requests the component (or updated version) from the server 1 , 2, as shown at 610 in the figure. 0:\90\9M62.DOC -27- D^266. The sacred feed benefit 102 transmits the required components to the device i〇6 in response to today's request. The device 1〇6 receives the component and processes the component β=piece as needed to have one version identification item stored locally by the device. After the component is processed, the 7C piece version identification item is updated. The device analyzes: an action ^ single and selects all necessary pieces from the word processor (10) as needed. 'The device 1 () 6 uses the action list version of the _ process to update the local storage action The list version is long. Therefore, unless the version of the action list downloaded from the feeder is different from the version stored on the device=', the device (10) does not process other actions from the server (10). A specific embodiment of the action soap 700 in a system for automatically processing components on a device. The action list 7A includes an action list version identification item 702 followed by a plurality of component/action pairs (7〇4, 7〇6): for example, the 7C piece/action pair 704 includes a component identification item and a phase System action. In the specific embodiment, the component identification item further includes a component version identification item and a "type" identification item. Using the component identification (4), it is possible to use the component version to determine whether the component is currently present on the device, and to identify the component type using the type identification item and to determine the component processing routine required to process the component. The action may be an installation, update, deletion, or any other type of action to change the state of the component on the device. The information in the action list may be encoded in any suitable format for secure transmission and/or identification purposes, and the component identification and the motion recognition item may be of any type. In a specific embodiment, the component/action pair 704 identifies the component processing routine to be installed on the device, and the component/action O:\90\90362.DOC -28- 对 对 ( (4) component (4) The handle shall be judged according to this. Although it has been illustrated in this paper, it is fresh and detailed to describe the system of the upper component - or more '1 rows each # # f ifb , / the example, but should know: Various changes' without departing from their spiritual or basic characteristics. Therefore, the y mm system is exemplified by the invention, and does not limit the scope of the invention, which is proposed herein. 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 </ RTI> </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> <RTIgt; </ RTI> </ RTI> </ RTI> Figure 1 shows a specific embodiment of a system for automatically processing components on a device; Figure 3 shows a specific embodiment of a method of operating an input device to provide a system for automatically processing components on the device; Figure 4 shows a specific embodiment of a method of operating a wheeled device for processing A plurality of component processing routines assigned by a particular component type; Figure 5 shows a specific embodiment of a method of operating an input device to process a plurality of component processing routines for manipulating a particular component type; During the operation of a particular embodiment of the system of components on the automated processing device, the transaction between the 'T-Temporary device and the device'; and Figure 7 shows the application Listing of the system for particular kinds of automatic processing apparatus of the movable element of the embodiment.
O:\90V90362.DOC -29- 1329266 【圖式代表符號說明】 100 自動處理裝置上元件的系統 102 伺服器 104 資料網路 106, 200 裝置 108, 702 動作清單版本識別項 110, 210, 700 動作清單 112 元件 Π4, 204 儲存之動作清單版本識別項(ALVI) 116 裝置上現有的元件 118 裝置儲存之元件版本 120, 228 元件處理常式 122, 230 安裝之元件處理常式 202 下載之版本識別項 206 比較邏輯 208 處理邏輯 212 元件版本識別項(CVI) 216 安裝元件邏輯 218 更新元件邏輯 214 功能邏輯 222 下載之元件 220 刪除邏輯 224 更新版本邏輯 226 安裝之元件 704, 706 元件/動作對 O:\9O\90362.DOC -30-O:\90V90362.DOC -29- 1329266 [Description of Symbols in the Drawings] 100 System 102 for Automatic Processing of Components on the Device Server 104 Data Network 106, 200 Device 108, 702 Action List Version Identification 110, 210, 700 Action Listing 112 Component Π 4, 204 Stored Action List Version Identification (ALVI) 116 Existing component on device 118 Device stored component version 120, 228 Component processing routine 122, 230 Installed component processing routine 202 Downloaded version identification 206 Comparison Logic 208 Processing Logic 212 Component Version Identification (CVI) 216 Install Component Logic 218 Update Component Logic 214 Function Logic 222 Downloaded Component 220 Delete Logic 224 Update Version Logic 226 Installed Component 704, 706 Component/Action Pair O:\ 9O\90362.DOC -30-
Claims (1)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US43548602P | 2002-12-20 | 2002-12-20 | |
| US43582802P | 2002-12-20 | 2002-12-20 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| TW200422869A TW200422869A (en) | 2004-11-01 |
| TWI329266B true TWI329266B (en) | 2010-08-21 |
Family
ID=36047750
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW92136235A TWI329266B (en) | 2002-12-20 | 2003-12-19 | System for registry-based automatic installation and component handling on a device |
| TW92136239A TW200422870A (en) | 2002-12-20 | 2003-12-19 | System to automatically process components on a device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW92136239A TW200422870A (en) | 2002-12-20 | 2003-12-19 | System to automatically process components on a device |
Country Status (6)
| Country | Link |
|---|---|
| AR (2) | AR042657A1 (en) |
| EG (1) | EG24017A (en) |
| MY (1) | MY138562A (en) |
| PE (2) | PE20040818A1 (en) |
| RU (2) | RU2339995C2 (en) |
| TW (2) | TWI329266B (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5473772A (en) * | 1991-04-02 | 1995-12-05 | International Business Machines Corporation | Automatic update of static and dynamic files at a remote network node in response to calls issued by or for application programs |
| US5761618A (en) * | 1994-12-22 | 1998-06-02 | Bell Atlantic Mobile Systems, Inc. | Updating technique for downloading new system identification (SID) list into a handset |
| US5920821A (en) * | 1995-12-04 | 1999-07-06 | Bell Atlantic Network Services, Inc. | Use of cellular digital packet data (CDPD) communications to convey system identification list data to roaming cellular subscriber stations |
| US6308061B1 (en) * | 1996-08-07 | 2001-10-23 | Telxon Corporation | Wireless software upgrades with version control |
| TW343318B (en) * | 1996-09-23 | 1998-10-21 | Advanced Risc Mach Ltd | Register addressing in a data processing apparatus |
| US6065046A (en) * | 1997-07-29 | 2000-05-16 | Catharon Productions, Inc. | Computerized system and associated method of optimally controlled storage and transfer of computer programs on a computer network |
-
2003
- 2003-12-19 RU RU2005122941/09A patent/RU2339995C2/en not_active IP Right Cessation
- 2003-12-19 RU RU2005122942/09A patent/RU2348065C2/en not_active IP Right Cessation
- 2003-12-19 MY MYPI20034927 patent/MY138562A/en unknown
- 2003-12-19 TW TW92136235A patent/TWI329266B/en active
- 2003-12-19 TW TW92136239A patent/TW200422870A/en unknown
- 2003-12-22 AR ARP030104785 patent/AR042657A1/en unknown
- 2003-12-22 AR ARP030104786 patent/AR045714A1/en unknown
-
2004
- 2004-01-05 PE PE2004000028A patent/PE20040818A1/en not_active Application Discontinuation
- 2004-01-05 PE PE2004000031A patent/PE20040820A1/en not_active Application Discontinuation
-
2005
- 2005-06-19 EG EGNA2005000331 patent/EG24017A/en active
Also Published As
| Publication number | Publication date |
|---|---|
| PE20040820A1 (en) | 2004-12-25 |
| AR042657A1 (en) | 2005-06-29 |
| AR045714A1 (en) | 2005-11-09 |
| RU2339995C2 (en) | 2008-11-27 |
| RU2348065C2 (en) | 2009-02-27 |
| RU2005122941A (en) | 2006-01-27 |
| TW200422869A (en) | 2004-11-01 |
| EG24017A (en) | 2008-03-24 |
| TW200422870A (en) | 2004-11-01 |
| MY138562A (en) | 2009-06-30 |
| RU2005122942A (en) | 2006-01-27 |
| PE20040818A1 (en) | 2004-12-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10348804B2 (en) | System to automatically process components on a device | |
| JP4865835B2 (en) | Method, software, and apparatus for performing actions on a wireless device using action lists and versioning | |
| JP5248657B2 (en) | System for registry-based automated installation and component handling on devices | |
| EP1470697B1 (en) | System and method for updating dataset versions resident on a wireless device | |
| US8645943B2 (en) | Communication system, communication device, and management server device | |
| JP2007511822A (en) | Method, software, and apparatus for performing application upgrades during execution | |
| TW200917732A (en) | Management system for local and remote services | |
| CN108733398B (en) | Software upgrading processing method and device | |
| TWI329266B (en) | System for registry-based automatic installation and component handling on a device | |
| JP2011123570A (en) | Information-processing device, server device, distribution system, receiving method and program module providing method | |
| JP4792744B2 (en) | Image processing device | |
| JP2009187456A (en) | Firmware update system, information processor, and firmware update method and program | |
| CN100474285C (en) | Method and apparatus for automatically processing components on a device | |
| KR100685314B1 (en) | Mobile terminal software automatic upgrade system and method | |
| JP2004046420A (en) | Matching method and its system for latest resources | |
| KR100545095B1 (en) | Wireless terminal software upgrade method | |
| JP2023005619A (en) | Management program, management method, and management system |