Method, system, dm client and dm server for installing software component
15 claims: 9 independent, 6 dependent
- 1ソフトウェアコンポーネントをインストールする方法であって、 端末によって、デバイス管理(Device Management;DM)サーバによって直接に送達されるソフトウェアコンポーネントパッケージ、または 前記DMサーバによって送達される前記ソフトウェアコンポーネントパッケージのダウンロードアドレスおよびダウンロードを指示するコマンドを受信するステップであって、 前記ソフトウェアコンポーネントパッケージが、1つまたは複数のソフトウェアコンポーネントを具備する、ステップと、 前記端末が、前記ダウンロードアドレスおよびダウンロードを指示する前記コマンドを受信する場合に、前記端末によって、前記ダウンロードアドレスに従って前記ソフトウェアコンポーネントパッケージをダウンロードするステップと、 前記端末によって、前記ソフトウェアコンポーネントパッケージをローカルにインストールし、前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードをSoftware Component Management Object(SCOMO)のDeployedサブツリーの下に生成するステップとを具備し、 前記ソフトウェアコンポーネントの各々に対応する前記管理ノードならびに前記管理ノードの前記サブノードを前記SCOMOの前記Deployedサブツリーの下に生成した後に、前記端末によって、インストール応答メッセージを前記DMサーバに報告するステップであって、前記インストール応答メッセージが前記Deployedサブツリーの下の前記管理ノードのUniform Resource Identifier(URI)を含む、ステップをさらに具備 し、 ダウンロードを指示する前記コマンドがDownLoadである場合に、前記端末が前記ダウンロードアドレスに従って前記ソフトウェアコンポーネントパッケージをダウンロードした後、前記ソフトウェアコンポーネントパッケージがローカルにインストールされる前に、あるいは、ダウンロードを指示する前記コマンドがDownLoadInstallまたはDownLoadInstallInactiveである場合に、前記端末が前記ソフトウェアコンポーネントパッケージをダウンロードすることに成功しているが前記ソフトウェアコンポーネントパッケージをインストールするのに失敗する時に、 前記ソフトウェアコンポーネントパッケージに対応する管理ノードおよび前記管理ノードのサブノードをDeliveredサブツリーの下に生成するステップと、 アクセス制御権を前記管理ノードおよび前記管理ノードの前記サブノードに割り当てるように適合された第1権利割当てステップとをさらに具備する ことを特徴とする方法。
- 2前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードを前記SCOMOのDeployedサブツリーの下に生成する前記ステップが、 前記端末によって、1つのソフトウェアコンポーネントのIDを入手し、前記IDを前記SCOMOの前記Deployedサブツリーの下の前記ソフトウェアコンポーネントに対応する前記管理ノードのIDサブノードの値に割り当てるステップであって、前記ソフトウェアコンポーネントの前記IDが、前記ソフトウェアコンポーネントパッケージの一部として前記端末に送達される、ステップを具備することを特徴とする請求項1に記載の方法。
- 3前記ソフトウェアコンポーネントパッケージをインストールした後、前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードを生成する前に、 前記ソフトウェアコンポーネントパッケージ内の1つのソフトウェアコンポーネントが、前記Deployedサブツリーの下に既に存在する管理ノードおよび前記管理ノードのサブノードに対応するソフトウェアコンポーネントと同一であるかどうかを判断し、前記ソフトウェアコンポーネントと同一である場合には、前記Deployedサブツリーの下に既に存在する前記管理ノードおよび前記サブノードの情報を前記ソフトウェアコンポーネントパッケージ内の前記ソフトウェアコンポーネントの情報に変更し、あるいは、前記ソフトウェアコンポーネントと同一でない場合に、前記ソフトウェアコンポーネントパッケージ内の前記ソフトウェアコンポーネントに対応する管理ノードおよび前記管理ノードのサブノードを前記Deployedサブツリーの下に生成するステップをさらに具備することを特徴とする請求項1または2に記載の方法。
- 4前記Deployedサブツリーの下に既に存在する前記管理ノードおよび前記サブノードの情報を前記ソフトウェアコンポーネントパッケージ内の前記ソフトウェアコンポーネントの情報に変更した後に、前記ソフトウェアコンポーネントパッケージ内の1つのソフトウェアコンポーネントが前記Deployedサブツリーの下に既に存在する管理ノードおよび前記管理ノードのサブノードに対応するソフトウェアコンポーネントと同一であると判断される場合に、 DeliveredサブツリーまたはDownloadサブツリーの下の前記ソフトウェアコンポーネントパッケージについて生成される前記管理ノードのアクセス制御権と、前記Deployedサブツリーの下に既に存在する前記管理ノードのアクセス制御権との組合せを、前記Deployedサブツリーの下に生成される前記管理ノードに割り当てるステップをさらに具備することを特徴とする請求項3に記載の方法。
- 5前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードを前記SCOMOのDeployedサブツリーの下に生成した後に、 アクセス制御権を前記管理ノードおよび前記管理ノードの前記サブノードに割り当てるステップをさらに具備することを特徴とする請求項1乃至4のいずれか一項に記載の方法。
- 6アクセス制御権を前記管理ノードに割り当てる前記ステップが、 DeliveredサブツリーまたはDownloadサブツリーの下に生成される前記ソフトウェアコンポーネントパッケージに対応する前記管理ノードのアクセス制御権を、前記Deployedサブツリーの下に生成される前記管理ノードに割り当てるモードと、 前記Deployedサブツリーの下に生成される前記管理ノードがその親ノードのアクセス制御権を継承するように、前記管理ノードのアクセス制御権にヌルを割り当てるモードと、 前記Deployedサブツリーの下に生成される前記管理ノードに特定のアクセス制御権を割り当てるモードと、 前記Deliveredサブツリーまたは前記Downloadサブツリーの下に生成される前記管理ノードのアクセス制御権と前記Deployedサブツリーの下に生成される前記管理ノードの前記親ノードのアクセス制御権とを組み合わせ、前記組み合わされたアクセス制御権を前記Deployedサブツリーの下に生成される前記管理ノードに割り当てるモードとのうちの1つを具備することを特徴とする請求項5に記載の方法。
- 7アクセス制御権を前記管理ノードのサブノードに割り当てる前記ステップが、 前記Deployedサブツリーの下に生成される前記管理ノードの前記サブノードに前記管理ノードのアクセス制御権を継承させ、かつ/またはDeliveredサブツリーまたはDownloadサブツリーの下の実行可能ノードのアクセス制御権を前記Deployedサブツリーの下に生成される前記管理ノードの実行可能ノードに割り当てるステップを具備することを特徴とする請求項5または6に記載の方法。
- 8ダウンロード応答メッセージおよび前記インストール応答メッセージが、同期モードまたは非同期モードで報告されるとともに、 同期報告モードが適用される場合に、前記ダウンロード応答メッセージまたは前記インストール応答メッセージ内の前記URIが、STATUSコマンドのITEM要素内で伝えられることを特徴とする請求項1乃至7のいずれか一項に記載の方法。
- 9ダウンロード応答メッセージが、前記ソフトウェアコンポーネントパッケージの名前および/またはIDをさらに具備し、 前記インストール応答メッセージが、前記ソフトウェアコンポーネントの名前および/またはIDをさらに具備することを特徴とする請求項1乃至8のいずれか一項に記載の方法。
- 10端末であって、 デバイス管理(Device Management;DM)サーバによって送達されるソフトウェアコンポーネントパッケージまたは前記DMサーバによって送達される前記ソフトウェアコンポーネントパッケージのダウンロードアドレスおよびダウンロードを指示するコマンドを受信するように適合された受信ユニットであって、前記ソフトウェアコンポーネントパッケージが、1つまたは複数のソフトウェアコンポーネントを具備する、受信ユニットと、 前記端末が前記ダウンロードアドレスおよびダウンロードを指示する前記コマンドを受信する場合に、前記ダウンロードアドレスに従って前記ソフトウェアコンポーネントパッケージをダウンロードするように適合されたダウンロードユニットと、 前記ソフトウェアコンポーネントパッケージをローカルにインストールし、前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードをSoftware Component Management Object(SCOMO)のDeployedサブツリーの下に生成するように適合されたインストールユニットと、 前記ソフトウェアコンポーネントの各々に対応する前記管理ノードならびに前記管理ノードの前記サブノードを前記SCOMOの前記Deployedサブツリーの下に生成した後に、インストール応答メッセージを前記DMサーバに報告する報告ユニットであって、前記インストール応答メッセージが前記Deployedサブツリーの下の前記管理ノードのUniform Resource Identifier(URI)を含む、報告ユニットとを具備 し、 ダウンロードを指示する前記コマンドがDownLoadである場合に、前記端末が前記ダウンロードアドレスに従って前記ソフトウェアコンポーネントパッケージをダウンロードした後、前記ソフトウェアコンポーネントパッケージがローカルにインストールされる前に、あるいは、ダウンロードを指示する前記コマンドがDownLoadInstallまたはDownLoadInstallInactiveである場合に、前記端末が前記ソフトウェアコンポーネントパッケージをダウンロードすることに成功しているが前記ソフトウェアコンポーネントパッケージをインストールするのに失敗する時に、 前記ソフトウェアコンポーネントパッケージに対応する管理ノードおよび前記管理ノードのサブノードをDeliveredサブツリーの下に生成するように適合された第1生成ユニットと、 アクセス制御権を前記管理ノードおよび前記管理ノードの前記サブノードに割り当てるように適合された第1権利割当てユニットとをさらに具備する ことを特徴とする端末。
- 11前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードを前記SCOMOのDeployedサブツリーの下に生成するために、前記インストールユニットが、1つのソフトウェアコンポーネントのIDを入手し、前記IDを前記SCOMOの前記Deployedサブツリーの下の前記ソフトウェアコンポーネントに対応する前記管理ノードのIDサブノードの値に割り当てるように適合され、前記ソフトウェアコンポーネントの前記IDが、前記ソフトウェアコンポーネントパッケージの一部として前記端末に送達されることを特徴とする請求項10に記載の端末。
- 12前記ソフトウェアコンポーネントに対応する前記管理ノードおよび前記管理ノードの前記サブノードが、前記Deployedサブツリーの下に生成された後に、 アクセス制御権を前記管理ノードおよび前記管理ノードの前記サブノードに割り当てるように適合された第2権利割当てユニットをさらに具備することを特徴とする請求項 10または11 に記載の端末。
- 13ソフトウェアコンポーネントをインストールする方法であって、 端末によって、デバイス管理(Device Management;DM)サーバによって直接に送達されるソフトウェアコンポーネントパッケージ、または 前記DMサーバによって送達される前記ソフトウェアコンポーネントパッケージのダウンロードアドレスおよびダウンロードを指示するコマンドを受信するステップであって、 前記ソフトウェアコンポーネントパッケージが、1つまたは複数のソフトウェアコンポーネントを具備する、ステップと、 前記端末が、前記ダウンロードアドレスおよびダウンロードを指示する前記コマンドを受信する場合に、前記端末によって、前記ダウンロードアドレスに従って前記ソフトウェアコンポーネントパッケージをダウンロードするステップと、 前記端末によって、前記ソフトウェアコンポーネントパッケージをローカルにインストールし、前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードをSoftware Component Management Object(SCOMO)のDeployedサブツリーの下に生成するステップとを具備し、 前記ソフトウェアコンポーネントの各々に対応する前記管理ノードならびに前記管理ノードの前記サブノードを前記SCOMOの前記Deployedサブツリーの下に生成した後に、前記端末によって、インストール応答メッセージを前記DMサーバに報告するステップであって、前記インストール応答メッセージが前記Deployedサブツリーの下の前記管理ノードのUniform Resource Identifier(URI)を含む、ステップをさらに具備し、 前記ソフトウェアコンポーネントに対応する前記管理ノードが前記SCOMOの前記Deployedサブツリーの下に生成された後に、インストール応答メッセージを前記DMサーバに報告するステップであって、前記インストール応答メッセージが、前記Deployedサブツリーの下に生成される前記管理ノードのURIを具備するとともに、 ダウンロードを指示する前記コマンドがDownLoadである場合に、ダウンロードが完了した後、前記ソフトウェアコンポーネントパッケージがインストールされる前に、あるいは、ダウンロードを指示する前記コマンドがDownLoadInstallまたはDownLoadInstallInactiveである場合に、ダウンロードが完了したがインストールが失敗する時に、ダウンロード応答メッセージを前記DMサーバに報告する、ステップをさらに具備し、前記ダウンロード応答メッセージが、Deliveredサブツリーの下に生成される前記管理ノードのURIを具備することを特徴とする方法。
- 14端末であって、 デバイス管理(Device Management;DM)サーバによって送達されるソフトウェアコンポーネントパッケージまたは前記DMサーバによって送達される前記ソフトウェアコンポーネントパッケージのダウンロードアドレスおよびダウンロードを指示するコマンドを受信するように適合された受信ユニットであって、前記ソフトウェアコンポーネントパッケージが、1つまたは複数のソフトウェアコンポーネントを具備する、受信ユニットと、 前記端末が前記ダウンロードアドレスおよびダウンロードを指示する前記コマンドを受信する場合に、前記ダウンロードアドレスに従って前記ソフトウェアコンポーネントパッケージをダウンロードするように適合されたダウンロードユニットと、 前記ソフトウェアコンポーネントパッケージをローカルにインストールし、前記ソフトウェアコンポーネントに対応する管理ノードならびに前記管理ノードのサブノードをSoftware Component Management Object(SCOMO)のDeployedサブツリーの下に生成するように適合されたインストールユニットと、 前記ソフトウェアコンポーネントの各々に対応する前記管理ノードならびに前記管理ノードの前記サブノードを前記SCOMOの前記Deployedサブツリーの下に生成した後に、インストール応答メッセージを前記DMサーバに報告する報告ユニットであって、前記インストール応答メッセージが前記Deployedサブツリーの下の前記管理ノードのUniform Resource Identifier(URI)を含む、報告ユニットとを具備し、 前記ソフトウェアコンポーネントに対応する前記管理ノードが前記SCOMOの前記Deployedサブツリーの下に生成された後に、インストール応答メッセージを前記DMサーバに報告するように適合された報告ユニットであって、前記インストール応答メッセージが、前記Deployedサブツリーの下に生成される前記管理ノードのURIを具備するとともに、 ダウンロードを指示する前記コマンドがDownLoadである場合に、ダウンロードが完了した後、前記ソフトウェアコンポーネントパッケージがインストールされる前に、あるいは、ダウンロードを指示する前記コマンドがDownLoadInstallまたはDownLoadInstallInactiveである場合に、ダウンロードが完了したがインストールが失敗する時に、ダウンロード応答メッセージを前記DMサーバに報告するように適合された、報告ユニットをさらに具備し、前記ダウンロード応答メッセージが、Deliveredサブツリーの下に生成される前記管理ノードのURIを具備することを特徴とする端末。
- 15請求項1乃至9 および13 のいずれか一項に記載のソフトウェアコンポーネントのインストールを実行させるためのプログラム。
Independent claims15
193 paragraphs, as filed
The present invention relates to data transport technology in the field of communications, specifically to methods for installing software components, systems, terminals, and device management servers.
Mobile terminals are an important part of the overall mobile network system. With Device Management (DM), data is downloaded from the network to the terminal device via the Over The Air (OTA) mechanism, which reads the downloaded data and further installs and installs software components. Complete the configuration. In the meantime, the service information and the function information of the terminal device required by the user are automatically transferred from the terminal device to the DM server. Therefore, the device management system (DMS) sets the initial configuration information of the terminal device, installs and updates permanent information on the terminal device, extracts management information from the terminal device, and of different types generated by the terminal device. It provides a cost-effective solution for maintaining and managing data within terminal devices, including processing event and alarm information.
You can now download, install, and remove software components for your device. The following describes how software components are downloaded and installed to show the technical solutions of the prior art.
In the prior art, the Software Component Management Object (SCOMO) is stored in the terminal device management tree. The DM server administers software components by delivering Exec commands to executable nodes within SCOMO.
Figure 1 shows the partial structure of SCOMO in the prior art. The download and installation process involves the DM server downloading software components by manipulating the Download and Delivered subtrees of SCOMO, and the DM server delivering Exec commands to SCOMO's executable nodes after the terminal downloads the components. Includes doing and the terminal device executing commands to install software components. The node that receives the Exec command is the Install node or Install Inactive node in the Delivered subtree. After the installation is complete, the terminal reports the installation result to the DM server. When the reporting mode is asynchronous, the terminal reports the installation result by sending a Generic Alert. The information reported is the Uniform Resource Identifier of the installed software component. Includes (URI). When the reporting mode is synchronous, the terminal reports the execution result code of the Exec command via the Status command corresponding to the Exec command.
<p num="0006"> However, traditional DM solutions for downloading and installing software components are vulnerable to the following flaws: 1. The process of installing and managing software components may not support parameters, resulting in failure. For example, the installation of a software component may require information such as serial numbers, or personalized management is not supported to meet different user requirements. 2. After the installation is complete, the security level may be degraded due to the lack of access control allocation methods for the installed component objects.</p>
<p num="0007"> The configurations of the present invention can provide methods, systems, terminals, and device management servers for installing software components.</p><p num="0008"> According to some configurations, the terminal receives the download address of the software component package delivered directly by the DM server or the software component package delivered by the DM server and a command to instruct the download of the component. Obtained by the terminal, the step of the package comprising one or more components, and the step of downloading the component package from the download address by the terminal when the terminal receives the download address and the command to instruct the download. A method is provided for installing a software component that includes a step to install the component package locally and generate a management node corresponding to the component as well as a subnode of the management node under the Deployed subtree of SCOMO.</p><p num="0009"> According to some configurations, the component package is a DM server adapted to deliver the software component package directly to the terminal, or to deliver the component package download address and command to download to the terminal. A DM server with multiple components and a component package delivered by the DM server or a command to instruct the download address and download of the component package delivered by the DM server are received, and the download address and the command to instruct the download are received. If so, the terminal adapted to download the component package from the download address, install the obtained component package locally, and generate the management node corresponding to the component and the subnodes of the management node under the Deployed subtree. A system for installing software components with and is also provided.</p><p num="0010"> According to some configurations, the terminal is a receiving unit adapted to receive the download address of the software component package delivered by the DM server or the download address of the component package delivered by the DM server and the command to instruct the download. And the component package is a receiving unit with multiple components and a download unit adapted to download the component package from the download address when the terminal receives a download address and a command to instruct the download. A terminal is also provided that installs the obtained component package locally and has a management node corresponding to the component and an installation unit adapted to generate a subnode of the management node under the Deployed subtree of SCOMO.</p><p num="0011"> According to some configurations, it is a DM server that delivers a software component package directly to a terminal via a DM command, or a download address for the component package and a command to direct the download to the terminal. A adapted delivery unit whose component package is a delivery unit with one or more components and a receiving unit adapted to receive the message reported by the terminal, and the message is Delivered. Receive with one or more of the management node URI generated under the subtree, the management node URI generated under the Deployed subtree, the component package name and ID, and the component name and ID items. A DM server with a unit is also provided.</p><p num="0012"> The methods, systems, terminals, and DM servers provided in the configurations of the present invention make the process of installing software components more reasonable.</p>
<figref num="1">It is a figure which shows the partial structure of SCOMO of the prior art.</figref><figref num="2">It is a figure which shows the structure of the system provided in embodiment of this invention.</figref><figref num="3">It is a figure which shows the state transition of the software component package in the terminal of embodiment of this invention.</figref><figref num="4A">It is a figure which shows the state transition of the software component in the terminal of embodiment of this invention.</figref><figref num="4B">It is a figure which shows the state transition of the software component in the terminal of another embodiment of this invention.</figref><figref num="5">It is a flow chart which shows the method of 1st Embodiment of this invention.</figref><figref num="6">It is a figure which shows the structure of SCOMO which downloads and installs a software component when the download is indirect in the 1st Embodiment of this invention.</figref><figref num="7">It is a figure which shows the structure of SCOMO which downloads and installs a software component when the download is direct in 1st Embodiment of this invention.</figref><figref num="8">It is a flow chart which shows three download modes in 1st Embodiment of this invention.</figref><figref num="9">It is a figure which shows the structure of SCOMO when the Pkg1 management node generated under the Download subtree contains the information of a software component.</figref><figref num="10">It is a figure which shows the structure of the terminal in embodiment of this invention.</figref><figref num="11">It is a figure which shows the workflow of the terminal in embodiment of this invention.</figref><figref num="12">It is a figure which shows the structure of the DM server in embodiment of this invention.</figref><figref num="13">It is a figure which shows the workflow of the DM server in embodiment of this invention.</figref><figref num="14">It is a flow chart which shows the method in 2nd Embodiment of this invention.</figref><figref num="15">It is a figure which shows the structure of SCOMO when the Pkg2 management node is generated under the Download subtree.</figref><figref num="16">It is a figure which shows the structure of SCOMO when the Pkg2 management node is generated under the Delivered subtree.</figref><figref num="17">It is a flow chart which shows the method in 3rd Embodiment of this invention.</figref><figref num="18">It is a figure which shows the structure of SCOMO when the Pkg3 management node is generated under the Delivered subtree.</figref><figref num="19">It is a figure which shows the structure of SCOMO when the Component1 management node is generated under the Deployed subtree.</figref>
As shown in FIG. 2, the system of one embodiment of the present invention includes a DM server 1 and a terminal 2, and the DM server 1 directly transfers a software component package containing a plurality of software components to the terminal 2. Adapted to deliver directly via DM commands, or adapted to deliver software component package download addresses and commands to direct downloads to Terminal 2, Terminal 2 served by DM Server 1. If the software component package or the download address of the software component package and the command to instruct the download are adapted to receive the download address of the software component package and the command to instruct the download, the terminal 2 follows the download address. Download the software component package, install the obtained software component package locally, and generate the management node corresponding to the component and the subnodes of that management node under the Deployed subtree.
When the command to instruct download is DownLoad, after terminal 2 downloads the component package according to the download address, before the component package is installed locally, or when the command to instruct download is DownLoadInstall or DownLoadInstallInactive. After terminal 2 downloads the software component package according to the download address but fails to install the software component package, terminal 2 generates a management node corresponding to the software component package and a subnode of that management node under the Delivered subtree. It is further adapted to assign access control rights to its management and subnodes.
Before Terminal 2 generates the management node corresponding to the software component package under the Delivered subtree, the ID of the downloaded software component package is the management node that already exists under the Delivered subtree and the component corresponding to that subnode. Terminal 2 can be adapted to determine if it is the same as the ID of the package, and if so, terminal 2 will download information about the management and subnodes that already exist under the Delivered subtree. If the information is changed to the information of the package, or otherwise, the terminal 2 generates a management node corresponding to the downloaded package and a subnode of the management node under the Delivered subtree.
DM Server 1 is further adapted to instruct Terminal 2 to generate a management node for the component package under the Download subtree before delivering the download instructions, and Terminal 2 is under the Download subtree. It is further adapted to set the access control rights of the generated management node as the access control rights of the management node generated under the Delivered subtree, or Terminal 2 allows the management node to set the access control rights of its parent node. Set the access control of the management node generated under the Delivered subtree to null for inheritance, or set a specific access control of the management node generated under the Delivered subtree. Or, by combining the access control rights of the management node generated under the Download subtree and the access control rights of the parent node of the management node generated under the Delivered subtree, the combined access control rights are combined in the Delivered subtree. It is adapted to be set as the access control right of the management node generated under.
DM Server 1 can be adapted to instruct Terminal 2 to generate a management node for the software component package under the Download subtree before delivering the command to download, and Terminal 2 will be downloaded. If the terminal 2 determines that the software component package is the same as the software component package corresponding to the management node that already exists under the Delivered subtree, the terminal 2 has the access control right of the management node generated under the Download subtree. It is further adapted to set the sum of the access control rights of the management nodes that already exist under the Delivered subtree as the access control rights of the management nodes generated under the Delivered subtree.
Terminal 2 causes the management node subnode generated under the Delivered subtree to inherit the access control right of the management node, or generates the access control right of the executable node under the Download subtree under the Delivered subtree. It is further adapted to be set as the access control right of the executable node of the management node to be executed.
Whether Terminal 2 receives the DM command delivered by DM Server 1 for the Delivered subtree node and DM Server 1 has the right to execute the DM command on that node according to the access control rights assigned to the node. And if DM Server 1 has that right, it may be adapted to execute its DM command on that node.
The DM server 1 is further adapted to send parameters to terminal 2, and terminal 2 either downloads the software component package, installs the software component package, or removes the software component package according to the parameter. It is further adapted to activate the software component, deactivate the software component, or remove the software component.
The DM server 1 is further adapted to instruct terminal 2 to add a subnode to SCOMO of terminal 2 before sending the parameters to terminal 2.
The DM server 1 directs terminal 2 to download, install, or remove the software component package, or activates, deactivates, or removes the software component. It may be adapted to send to terminal 2 via a DM command.
After installing the software component package, terminal 2 creates the management node and its subnodes for which the software component package already exists under the Deployed subtree before generating the management node and its subnodes corresponding to that component under the Deployed subtree. Further adapted to determine if it contains the same software component as the corresponding software component. If so, terminal 2 is adapted to change the information of the management node under the Deployed subtree and its subnodes to the information of the components in the software component package, otherwise terminal 2 will Adapted to generate management nodes and their subnodes corresponding to software components in a software component package under the Deployed subtree.
Terminal 2 is further adapted to determine that the two software components are the same if it determines that the IDs or names of the software components are the same, otherwise terminal 2 has the two software components Judge different.
When a software component in a software component package is determined to be the same as a software component corresponding to a management node that already exists under the Deployed subtree, Terminal 2 uses the information of the management node under the Deployed subtree as the software component. Change the information of the software components in the package and add the access control rights of the management node generated for the software component package under the Delivered or Download subtree to the access control rights of the management nodes that already exist under the Deployed subtree. Is further adapted to be set as the access control right for the management node generated under the Deployed subtree.
Prior to delivering the software component package to terminal 2, DM server 1 is further adapted to instruct terminal 2 to generate a management node corresponding to that software component package under the Delivered subtree, and that management node. Contains software component information, and terminal 2 is further adapted to store the software component information contained in the management node under the Delivered subtree in the Deployed subtree.
Terminal 2 is further adapted to set the access control rights for the management node and its management node subnodes after creating the management node corresponding to the software component under the Deployed subtree.
Terminal 2 sets or manages the access control right of the management node corresponding to the software component package generated under the Delivered subtree or Download subtree as the access control right of the management node generated under the Deployed subtree. A management node created under the Deployed subtree to set the access control rights of the management node generated under the Deployed subtree to null so that the node inherits the access control rights of its parent node. To set specific access control rights for, or to combine and combine the access control rights of the management node under the Delivered or Download subtree with the access control rights of the parent node of the management node generated under the Deployed subtree. It is also adapted to set the access control right given as the access control right of the management node generated under the Deployed subtree.
Terminal 2 causes the management node subnode generated under the Deployed subtree to inherit the access control right of the management node, or generates the access control right of the executable node under the Delivered subtree or Download subtree under the Deployed subtree. It is also adapted to be set as the access control right of the executable node of the management node to be set.
After terminal 2 creates a management node for the software component under the Deployed subtree, terminal 2 receives the DM command delivered by DM Server 1 for the Deployed subtree node and the access control assigned to that node. According to the rights, determine if DM Server 1 has the right to execute DM commands on that node, and if DM Server 1 has that right, execute the DM commands on that node. Further adapted.
After Terminal 2 generates the management node corresponding to the component under the Deployed subtree, Terminal 2 is further adapted to report the installation response message to DM Server 1, and the installation response message is under the Deployed subtree. Contains the URI of the generated management node.
When the command instructing the download conveys DownLoad as an indirect download instruction, after the download is completed, before the software component package is installed, or when the command instructing the download conveys DownLoadInstall or DownLoadInstallInactive as an indirect download instruction. When the download is complete but the installation fails, Terminal 2 reports a download response message to DM Server 1, which contains the management node URI generated under the Delivered subtree.
Download and install response messages are reported in synchronous or asynchronous mode.
When the reporting mode is synchronous, terminal 2 is further adapted to convey the URI in a download or install response message via the Item element of the Status command.
The download response message further includes the name and / or ID of the software component package, and the installation response message further includes the name and / or ID of the software component.
When the DownLoad instruction is used for direct or indirect downloads, after generating the management node corresponding to the software component under the Deployed subtree, terminal 2 further sets Installed to the package state. It is adapted.
Hereinafter, embodiments of the present invention will be described in detail.
FIG. 3 shows the state transition of the delivered software component package in the terminal according to the embodiment of the present invention. As shown in Figure 3, the delivered software component package can be in one of four states: Not Download means that the software component package is not downloaded by the terminal and is in the terminal. Delivered indicates that the software component package has been downloaded by the terminal but has not yet been installed, Installed indicates that the software component package is installed, and Removed indicates that the software is not present. Indicates that the component package has been removed. Software component packages can move from one state between these four states to another. For example, after the software component package is downloaded, the software component package state is Not The software component package state changes from Downloaded to Delivered, and then the software component package state changes from Delivered to Installed when the software components in the software component package need to be activated or not after the software component package is installed. When the software component package changes and is removed without being installed, the software component package state changes from Delivered to Removed, and when the software component package is removed after it is installed, the software component package state is from Installed. If it changes to Removed and the installation fails and the software component package is not removed from the terminal, the software component package state changes from Not Downloaded to Delivered and the installation fails and the software component package is removed. The software component package status is Not If the software component package changes from Downloaded to Removed and the software component package is downloaded and installed directly, the software component package state is when the software component in the software component package may or may not be activated. , Not Downloaded changes to Installed. It is clear that the software component packages are in the Download and Delivered subtrees. The Not Downloaded and Removed states can be combined into a single Idle state, which means that the software component package does not exist in the device, indicating that the software component package has not been downloaded or has already been removed.
Software components reside in the Deployed subtree. Figure 4A shows the state transitions of the software components in the terminal. Inactive indicates that the software component is installed but not activated because it is not activated, Active indicates that the component is installed, activated, and the software component is currently available. Removed indicates that the software component has been removed. Software components can move from one of these three states to another. If the software component state changes from Inactive to Active when the component is activated, and conversely, the software component state changes from Active to Inactive and the software component is removed without being activated. The software component state changes from Inactive to Removed, and if the software component is removed when it is activated, the software component state changes from Active to Removed. You can change the Removed state to Idle, which means that the software component is not present in the device, indicating that the software component is not installed or has been removed. When a software component package is in the Installed state, the state of the software components contained in that software component package changes from Idle to Active or Inactive. When a software component is removed, the software component state changes from Active or Inactive to Idle.
In embodiments of the invention, a software component package can be a means of encapsulating and delivering one or more software components unmanaged. In this embodiment of the invention, the software component package may have no state transitions, and only the software components have state transitions. In this case, the state transition of the software component is shown in FIG. 4B. Idle indicates that the software component has not been downloaded, installed, or has already been removed, Delivered indicates that the software component has been downloaded but not installed, and Inactive indicates that the software component has been installed. Indicates that the software component has been installed, is not activated, and is therefore not available, and Active indicates that the software component is installed, activated, and therefore available. In FIG. 4B, the dashed line means that the state does not change after the operation fails, and the solid line indicates the normal operation process. Software components can move from one state to another in four states. The software component state changes from Idle to Delivered when the software component is only downloaded or when the software component is downloaded but the installation fails (when the download fails, the state remains unchanged). When a software component is installed, the component state changes from Idle or Delivered to Active or Inactive (when the installation fails, the state remains unchanged) and when the software component is activated. , The software component state changes from Inactive to Active (when activation fails, the state remains unchanged
A software component package can contain one or more software components. A software component can represent an application program, an antivirus patch, or a library file for an application program. Before a software component is installed, it must be placed within the software component package. After the software component package is downloaded and successfully installed, the software component becomes the deployed component.
FIG. 5 shows a flow chart of the first method embodiment of the present invention. In this embodiment, the name of the software component package is ascendo, the software component package ID is PkgID_1, and the software component package contains three software components, the names of which are ascendo_1, ascendo_2, and ascendo_3, respectively. Yes, the IDs are ComID_1, ComID_2, and ComID_3, respectively. This flow diagram includes the following steps.
Step 501: The DM server delivers the software component package directly to the terminal via a DM command, or delivers the package download address and a command to download to the terminal. A software component package contains multiple software components.
The DM server first determines the download mode of the terminal. If the download mode is direct, the DM server will deliver the software component package directly to the terminal via the DM command, and if the download mode is indirect, the DM server will deliver the software component package download address and The download instruction command is delivered to the terminal, and the download address of the software component package and the download instruction command may be delivered in one DM session or multiple different DM sessions. The DM server can repeatedly deliver a download instruction command to the terminal for one download address.
For easy management, the DM server sends instruction-related parameters to the terminal before delivering an action instruction that can be an instruction to download, install, remove, or activate / deactivate software components. Can be sent. The terminal executes the instruction according to the parameters. Parameters can be delivered in two ways. One is to add a node to the terminal's software component management tree, through which the server delivers parameters. The other method is to convey the parameters directly within the Data element of the delivered Exec command. Next, a parameter delivery method will be described by explaining how the parameters related to the instruction to install the software component should be delivered. Other instruction-related parameters are delivered in the same way. Before the terminal installs the software component package, the DM server delivers the parameters to the terminal when needed. This means that the DM server can deliver parameters when delivering software component packages via DM commands or when delivering commands or installation commands that direct download. The parameter can instruct the terminal to install only certain software components within the software component package, such as Java® or C ++ related components. The parameter can also indicate the processing policy for the terminal to generate the Deployed subtree after installation. Alternatively, the DM server can deliver the parameters at other times as needed. In the subsequent installation process, the terminal can install the downloaded software component package locally according to the parameters. There are multiple parameter delivery modes. For example, the DM server is a sub of SCOMO Create a management node for the software component package under the tree, instruct the terminal to add a subnode for that management node, deliver the parameters directly to that subnode, or the DM server via a DM command. The parameters can be delivered directly to the terminal. The latter mode will be described in step 503. In this step, the former mode is described as follows.
The DM server creates a management node for the software component package under the SCOMO subtree and instructs the terminal to add the management node subtree. The subtree in which the management node is generated changes with the download mode. The download mode can be direct or indirect, where the indirect download further includes a download via the DownLoad instruction and a download via the DownLoadInstall or DownLoadInstallInactive instruction.
If the download is indirect, the DM server tells the terminal to create a management node for the software component package under the Download subtree. As shown in Figure 6, the terminal creates a management node named Pkg1 under the Download subtree and adds a subnode for that management node to store the parameters delivered by the DM server. You can name this subnode InstallPara. In this download mode, the DM server can deliver the parameters to the Download / Pkg1 / InstallPara subnode, where Pkg1 is the name of the management node generated.
If the download is direct, the DM server tells the terminal to create a management node for the software component package under the Delivered subtree. As shown in Figure 7, the terminal creates a management node named Pkg1 under the Delivered subtree and adds a subnode for that management node to store the parameters delivered by the DM server. Similarly, this subnode can be named InstallPara. In this download mode, the DM server can deliver the parameters to the Delivered / Pkg1 / InstallPara subnode.
Despite the download mode, it may be necessary to add the storage space in the terminal as a subnode. The existence of subnodes depends on the needs of the server. If parameters (such as serial numbers) are required for the installation, if a personalized installation is required (for example, to install only Java® related components or only C ++ related components), or the behavior of software components If it is necessary to give the server information about the environment (for example, whether the software component or software component package requires a Java® environment or a C ++ environment), the terminal adds an InstallPara subnode. If you can, then you don't need to add the InstallPara subnode.
Table 1 lists the node information of InstallPara. InstallPara is placed in DownLoad / <X> / InstallPara in any format with optional status. In this embodiment of the invention, the InstallPara subnode is in character (Chr) format. You can add at most one InstallPara subnode, and the minimum access type is Get. These settings are applicable to all download modes.
<tables num="1"><img id="000002" he="24" wi="157" file="JP5954635B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>
Table 2 lists the information for the Name subnode. The location of the Name is DownLoad / <X> / Name, Inventory / Delivered / <X> / Name, or Inventory / Deployed / <X> / Name. These settings are applicable to all download modes. This subnode is required in Chr format. The number of executable nodes that can be added is 1. The minimum access type is Get.
<tables num="2"><img id="000003" he="24" wi="157" file="JP5954635B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>
In addition, the Pkg1 node contains a State subnode. The position of State is Inventory / Delivered / <X> / State. State information is listed in Table 3. The State subnode records state information for the current software component package or software component. As shown in Table 4, the Delivered state can be indicated by "10" and the Installed state can be indicated by "20".
<tables num="3"><img id="000004" he="25" wi="157" file="JP5954635B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>
<tables num="4"><img id="000005" he="40" wi="157" file="JP5954635B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>
Obviously, the DM server can deliver the parameters after the DM server delivers the command to direct the download and before the terminal installs the software component package.
When the download mode is indirect, the DM server stores the download address of the software component package in the PkgURL subnode of the management node named Pkg1 and delivers a command to instruct the download. The terminal can download software component packages locally in preset download mode according to the download address.
Step 502: When the terminal receives the download address and the command to instruct the download, the terminal downloads the package according to the download address and stores the software component package locally.
As explained above, the download mode can be direct or indirect. In direct download mode, the DM server creates a management node for the software component package to be downloaded under the Delivered subtree of SCOMO and replace command to the Data node of the Delivered subtree to deliver the software component package to the terminal. Instruct the terminal to do. In indirect mode, the DM server creates a management node for the downloaded software component package under the Download subnode and sets the download information, including the software component package name, version, and download address, within the management node subnode. , Instruct the terminal to add applicable operating rights, and then the DM server delivers a command to the terminal instructing the download. Figure 8 shows a flow diagram of the three download modes, including:
Step 801: The DM server determines the download mode and delivers a command instructing the download.
Step 802: The terminal selects the process according to the download instruction. The following describes each of the three download modes.
1. Indirect download via DownLoad instruction
Step 803: The terminal downloads the software component package locally from the software component package download address provided by the DM server.
Step 804: Before installing the software component package, the terminal creates a management node under the Delivered subtree that corresponds to the successfully downloaded software component package. This means that the terminal will generate a management node for the software component package under the Delivered subtree. Before creating a management node, the terminal needs to determine if there is a management node under the Delivered subtree whose PkgID corresponding to this management node is the same as the ID of the downloaded software component package. The PkgID may be provided by a software publisher or package publisher. If such a management node exists, the terminal changes the information of the management node and its subnodes that already exist under the Delivered subtree to the information of the currently downloaded software component package and gives access control. Reassign to management node. If no such management node exists, the terminal creates the management node and its subnodes for the downloaded software component package under the Delivered subtree and reassigns access control to the new management node. In an embodiment of the invention, assigning an access control right to a node means generating an access control list (ACL) attribute for the node and assigning a value to that attribute. The ACL value can be null (because it inherits the ACL value of the parent node by default) or non-null (the ACL value of the node itself).
In this embodiment, the ID of the downloaded software component package is PkgID_1. Before the terminal generates the management node corresponding to the software component package, the terminal determines if a PkgID subnode identified as PkgID_1 exists for the management node under the current Delivered subtree. If such a subnode exists, the terminal changes the information on the existing management node and its subnodes to the information in the software component package to be downloaded and reassigns access control to that management node and subnodes. .. Otherwise, the terminal will generate a new management node under the Delivered subtree for the software component package to be downloaded, where the value of the PkgID subnode of the new management node is PkgID_1 and the terminal will be the new management. Assign access control to a node and its subnodes. As shown in Figure 6, the terminal sets a value for each subnode of the management node that corresponds to the software component package generated under the Delivered subtree. This value can be the same as the value of the corresponding subnode of the management node corresponding to the software component package generated under the Download subtree. The value of the State subnode is Delivered. In addition, the terminal assigns access control rights and other attribute values to the management node generated under the Delivered subtree and the subnodes of that management node.
In this embodiment, access control rights can be assigned in multiple ways, which are described by way of example:
The method of assigning access control rights to the management node under the Delivered subtree is as follows. As described in step 501, when the DownLoad instruction is used, the terminal creates a management node under the Download subtree that corresponds to the software component package before the DM server delivers the command to download. Already done, therefore, the terminal assigns access control of the management node under the Download subtree to the management node generated under the Delivered subtree, or its parent node (Delivered node) to the management node under the Delivered subtree. Inherit the access control right of, or assign a specific access control right (such as Get = *) to the Delivered subtree.
The method of assigning the access control right to the subnode of the management node is as follows. The subnode of the management node under the Delivered subtree inherits the access control of the management node, or the terminal has the access control of the corresponding subnode of the management node corresponding to the software component package under the Download subtree. Assign to a subnode of the management node below. Alternatively, some of the admin node subnodes under the Delivered subtree inherit access control of the admin node, and other subnodes of the admin node under the Delivered subtree correspond to software component packages under the Download subtree. The above two methods can be combined to allow access control of the management node's counterpart.
For the executable subnodes of the management node (Install, InstallInactive, and Remove under Operations), the terminal sets the access control of the corresponding executable node under the Download subtree as its access control. This is because the terminal has access control rights for the three executable nodes Install, InstallInactive, and Remove under Operations, and access controls for the executable node under Operations for the management node under the Download subtree, preferably. , Download means to set the access control right of the executable node that executes the download operation under the Download subtree. For example, the command that instructs download is DownLoad, the executable node that executes this command is DownLoad / Pkg1 / Operations / DownLoad, and the access control right is Get = * & Exec = ServerA. The terminal then assigns Get = * & Exec = ServerA to all executable nodes under Delivered / Pkg1 / Operations.
In addition, if the terminal determines that the software component package to be downloaded is the same as the software component package corresponding to the management node that already exists under the Delivered subtree, the terminal will be in the software component package under the Download subtree. Set the sum of the access control rights of the management node and the access control rights of the management node of the software component package that already exists under the Delivered subtree as the new access control rights of the management node of the software component package under the Delivered subtree. Can be done. Access control rights can be assigned to subnodes of the management node in the same way as above.
Step 805: The terminal reports a download response message to the DM server. This message conveys the URI of the software component package in the Delivered subtree (the URI of the Delivered subnode). This message can also convey other information that includes, but is not limited to, one or more of the items named Software Component Package ID (PkgID Subnode) and Software Component Package Name (Name Subnode).
In this embodiment, the response message can be reported in multiple modes, such as synchronous and asynchronous reporting. Synchronous reporting means that the terminal reports execution results and other information in response to the operation instructions delivered by the server, and asynchronous reporting means that the terminal responds to the operation instructions delivered by the server. Means to report execution results independently in the same or different management sessions. Synchronous reporting allows the server to know the current execution result of the terminal in real time, while asynchronous reporting keeps waiting for a session between the terminal and the server with less resource waste and higher efficiency. Help save time. The user can select the correct reporting mode based on the actual needs. The two reporting modes are described as follows:
Asynchronous reporting implements data reporting by using the Generic Alert command. The information reported includes Result Code, Source, Target, AlertType, and Correlator, which is communicated in the Item / Data element of the Generic Alert command. The Source element conveys the URI of the node that executes the download instruction. The Target element conveys the URI of the management node generated for the software component package under the Delivered subtree. In addition to the above information, the software component package includes name information that is the Name subnode of the management node generated under the Delivered subtree and / or ID information that is the PkgID subnode of the management node generated under the Delivered subtree. Information is also reported. There are at least three unique ways to report component package information.
1. Report the name of the package to the DM server via MetaInf's extensible element EMI in Alert. This can be done using the following program, where Pkg1 is the name assigned to a management node when it is created by a terminal. <Alert> <CmdID> 2 </ CmdID> <Data> 1226 </ Data> <!-Generic Alert-> <Correlator> abcl23 </ Correlator> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg1/Operations/Download </ LocURI> </ Source> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkgl </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> text / plain </ Format> <Mark xmlns = "syncml: metainf"> critical </ Mark> <EMI xmlns = "syncml: metainf"> _Name </ EMI> <!-Package information to be reported-> </ Meta> <Data> <!-Result Code-> </ Data> </ Item> </ Alert>
In the above program, the value of EMI can be the information in Delivered / Pkg1 / Name, the information in Delivered / Pkg1 / PkgID, or both.
2. Add the Item element to Alert and report the software component package information to the DM server via the Data element of the added Item. This can be done via the following program: <Alert> <CmdID> 2 </ CmdID> <Data> 1226 </ Data> <!-Generic Alert-> <Correlator> abc123 </ Correlator> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg1/Operations/Download </ LocURI> </ Source> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1 </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> text / plain </ Format> <Mark xmlns = "syncml: metainf"> critical </ Mark> </ Meta> <Data> <!-Result Code-> </ Data> </ Item> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg1/Operations/Download </ LocURI> <Source> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1/Name </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> chr </ Format> </ Meta> <Data> _Name </ Data> <!-Package information to be reported-> </ Item> </ Alert>
In the above program, the value of Data can be the information in Delivered / Pkg1 / Name, the information in Delivered / Pkg1 / PkgID, or both.
3. Report the Result Code in the Alert's Item / Data element, along with the ID and / or Name. You need to define the data format of the Item / Data element to help the server correctly resolve the Result Code, ID, and / or Name within the Item / Data element. This format can be "Result Code (separator) ID" or Extendable Markup Language (XML) format. One section of a particular reporting program (in XML format) is as follows, where Pkg1 is the name assigned to a management node when it is created by a terminal. <Alert> <CmdID> 2 </ CmdID> <Data> 1226 </ Data> <!-Generic Alert-> <Correlator> abc123 </ Correlator> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg1/Operations/Download </ LocURI> </ Source> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1 </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> text / plain </ Format> <Mark xmlns = "syncml: metainf"> critical </ Mark> </ Meta> <Data> <! [CDATA [ <ResultCode> 200 </ ResultCode> <Identifier> 1123sdf312 </ Identifier> ]]> </ Data> </ Item> </ Alert>
In the synchronous report, the operation result is reported via the Status command corresponding to the Exec command. The Data element of the Status command conveys the DM status code of the operation. The Status command also reports the URI of the Pkg1 management node under the Delivered subtree. The Status command can also report the Name or PkgID of the software component package. The reporting method is as follows. The Status command conveys the Item, the Target element of the Item conveys the URI of the Pkg1 management node under the Delivered subtree, and the Source element conveys the URI of the node that executes the Exec operation. Reporting can be done through the following programs: <Status> <MsgRef> 1 </ MsgRef> <CmdRef> 2 </ CmdRef> <Cmd> Exec </ Cmd> <Data> 200 </ Data> <!-Successful-> <Item> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1 </ LocURI> </ Target> </ Item> </ Status>
In addition to the execution status, Delivered / Pkg1 / NAME or Delivered / Pkg1 / PkgID and package operation status code can be reported at the same time. The software component package operation code can be conveyed in the Item / Data element, and the Delivered / Pkg1 / NAME or Delivered / Pkg1 / PkgID can be combined in the EMI element, in the parallel Item, or in the Item / Data element ( If the software component operation code is also reported, the status code is also combined). For combined reporting, you need to define the data format of the Item / Data element to help the server correctly resolve the different data in the Item / Data element. This format can be "result code (separator) ID" or XML format. The specific reporting program segments (in XML format) are: <Status> <MsgRef> 1 </ MsgRef> <CmdRef> 2 </ CmdRef> <Cmd> Exec </ Cmd> <Data> 200 </ Data> <!-Successful-> <Item> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1 </ LocURI> </ Target> <Meta> <Format xmlns = "syncml: metainf"> text / plain </ Format> </ Meta> <Data> <! [CDATA [ <ResultCode> 200 </ ResultCode> <!-Status Code-> <Identifier> 1123 sdf3 12 </ Identifier> ]]> <Data> </ Item> </ Status>
The DM server determines the downloaded software component package and the corresponding management node according to the information reported by the terminal. Based on this information, the terminal can perform subsequent actions on the software component package.
2. Indirect download via the DownLoadInstall or DownLoadInstallInactive instruction.
In this download mode, the DM server also tells the terminal to create a management node for the software component package under the Download subtree. Step 806 is then followed by the terminal downloading the software component package locally from the download address provided by the DM server. The download address is stored in the PkgURL subnode of the management node under the Download subtree. Then, step 807 continues, and if the download is successful, the terminal automatically performs an Install or Install Inactive action after the download is complete.
3. Download directly.
Step 808: The DM server tells the terminal to generate a management node for the software component package under the Delivered subtree and issues a Replace command targeting the Data subnode of the management node generated under the Delivered subtree. To deliver to. The terminal receives the software component package data delivered by the server via the Replace command, stores the data in the Data subnode of the management node under the Delivered subtree, and returns the download response message to the DM server.
Step 503: The terminal installs the downloaded software component package locally and creates a management node corresponding to the software component in the package and a subnode of that management node under SCOMO's Deployed subtree.
When the download is complete, the terminal installs the obtained software component package locally. Obviously, if the download is direct, the software component package obtained is delivered directly by the DM server, and if the download is indirect, the software component package is obtained from the download address delivered by the DM server. Will be done.
The installation mode changes with the download mode. The following describes each installation process for direct downloads, indirect downloads via DownLoad, and indirect downloads via DownLoadInstall and DownLoadInstallInactive.
1. Indirect download via DownLoadInstall or DownLoadInstallInactive.
When the DM server delivers the DownLoadInstall or DownLoadInstallInactive instruction, the terminal installs the software component package directly after the software component package is successfully downloaded. Step 502 describes the process by which the terminal downloads the software component package via the DownLoadInstall or DownLoadInstallInactive instruction. In this case, the terminal can generate a management node for the downloaded software component package under the Delivered subtree as shown in FIG. 6 and assign access control rights to the management node and its subnodes. Here, the access control right can be assigned in the same manner as described in step 502 for assigning the access control right to the management node generated under the Delivered subtree when the Download instruction is delivered. Instead, the terminal may not generate the corresponding management node under the Delivered subtree.
The terminal installs the downloaded software component package locally and parameters may be required during the installation process. One parameter delivery method is described in step 501. In embodiments of the invention, other methods can be used by the terminal to obtain the parameters. For example, if the DM server sets download mode to download directly or indirect download via the DownLoad command, when the DM server receives a download response message from the terminal, the DM server will allow the terminal to successfully package the software components. The DM server delivers the parameters to the terminal via an Install or InstallInactive command, which is considered to have been downloaded. When the DM server sets the download mode to indirect download via the DownLoadInstall command or the DownLoadInstallInactive command, the DM server delivers the parameters to the terminal via the DownLoadInstall or DownLoadInstallInactive command. This actually means that the parameters are delivered via DM commands, including the Install command. For example, when the Inventory / Delivered / <Pkg1> / Operations / Install subnode performs an operation, the DM server specifies the Inventory / Delivered / <Pkg1> / Operations / Install executable node to perform the installation operation. , Deliver the Install command. In this case, the parameters are delivered via the following program. <Exec> <CmdID> 3 </ CmdID> <Item> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1/Operations/Install </ LocURI> </ Target> <Data> -1-t </ Data> <!-Parameter-> </ Item> </ Exec>
In the program above, the parameters are communicated in the Data element of the Exec command. During the installation process, the terminal can perform the installation according to this parameter.
When the installation is performed via DownLoadInstall or DownLoadInstallInactive, the installation fails, but the software component package is not removed and the terminal generates a management node under the Delivered subtree that corresponds to the software component package before installation. Otherwise, the terminal will generate a management node for the downloaded software component package under the Delivered subtree. Before generating this management node, the terminal needs to determine if a management node corresponding to the same software component package as the downloaded software component package already exists under the current Delivered subtree. If such a management node exists, the terminal changes the information of the management node under the current Delivered subtree and that subnode to the information of the downloaded software component package, and the access control right is updated management. Assign to nodes and subnodes. Otherwise, the terminal creates a new management node and its subnodes for the downloaded software component package under the Delivered subtree and assigns access control to the new management node and subnodes. Here, access control rights can be assigned in the same manner as described in step 502 when the terminal downloads the software component package via the DownLoad instruction. However, the allocation method is not limited to this. After that, the terminal reports an installation response message to the DM server, which conveys the failure information.
If the installation is successful, the terminal should generate a management node under the Deployed subtree for each software component in the software component package. As shown in Figure 6, when a terminal creates a management node for a software component in a software component package, the terminal obtains the ID of the software component and uses that ID for the software component ID subnode of the management node. Set as a value (ie, as the value of the ID node under the Deployed subtree). The software component ID can be provided by the network, for example by a software publisher or a software component package publisher. The component ID can be delivered to the terminal together with the software component package as metadata for the software component package, or can be delivered to the terminal independently of the software component package. The software component ID can uniquely identify the software component. The server (DM server, software publisher, or package publisher) can recognize the software component according to this ID. Before creating the management node, the terminal has one or more software components corresponding to the management nodes that already exist under the Deployed subtree that are the same as one or more of the installed software components. You need to decide. This decision can be made in this way: Compare the software component ID (ID node under the Deployed subtree) or software component name (Name node under the Deployed subtree). When the ID is adopted as a criterion for judgment, when the IDs of the two software components are the same, the two software components are considered to be the same. Otherwise, their software components will be different. The same is true when the name is adopted as a criterion for judgment. When the terminal changes the information of the management node and its subnode of the existing software component when the two software components are the same, the terminal does not change the value of the existing PkgIDRef subnode (that is, the software component whose value is old). Keep the relationship between the old software component corresponding to the management node and the old software component package, which is the PkgID of the package) and add a new association (ie, the installed software component package and the software corresponding to the management node) Add a PkgIDRef node under the Deployed subtree to store the associations with the software components in the component package). Therefore, multiple PkgIDRef nodes may coexist under the Deployed subtree. To achieve this functionality, the tree occurrence of the PkgIDRef node that stores the association information must be changed to "one or more" as shown in Table 5. Do not change the value of the existing PkgIDRef subnode (that is, keep the relationship between the old software component corresponding to the management node and the old software component package whose value is the PkgID of the old software component package) and create a new association. Add (ie, add a PkgIDRef node under the Deployed subtree to store the association between the installed software component package and the software component in the software component package that corresponds to the management node). Therefore, multiple PkgIDRef nodes may coexist under the Deployed subtree. To achieve this functionality, the tree occurrence of the PkgIDRef node that stores the association information must be changed to "one or more" as shown in Table 5. Do not change the value of the existing PkgIDRef subnode (that is, keep the relationship between the old software component corresponding to the management node and the old software component package whose value is the PkgID of the old software component package) and create a new association. Add (ie, add a PkgIDRef node under the Deployed subtree to store the association between the installed software component package and the software component in the software component package that corresponds to the management node). Therefore, multiple PkgIDRef nodes may coexist under the Deployed subtree. To achieve this functionality, the tree occurrence of the PkgIDRef node that stores the association information must be changed to "one or more" as shown in Table 5.
<tables num="5"><img id="000006" he="24" wi="157" file="JP5954635B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>
The next judgment process adopts the name as the judgment criterion.
For example, consider a software component named ascendo_1. If the value of the Name subnode of the management node under the Deployed subtree is ascendo_1, the terminal changes the management node information to the information of the ascendo_1 software component that was downloaded and successfully installed, and the updated management node. Assign access control to and its subnodes. If the value of the Name subnode of any management node under the Deployed subtree is not ascendo_1, the terminal creates a management node named software component 1 under the Deployed subtree and the Name subnode value of this management node is ascendo_1. The terminal assigns access control rights to this management node and its subnodes. software component A management node named 1 can be created under the Deployed subtree in multiple modes. For example, as shown in Figure 9, if the management node generated under the Download subtree contains software component information, the terminal sends the software component information to the corresponding management node under the Deployed subtree. Store.
Here, it is necessary to assign access control rights to the updated or generated management node and its subnodes, regardless of whether the terminal determines that the same software component already exists. Access control rights can be assigned in multiple ways, including the method described in step 502. Furthermore, if the terminal determines that a management node with the same name exists, other allocation methods can be applied. For example, combine the set access control right with the access control right of the existing management node, and use the combined access control right as the new access control right. Here, the set access control right can be the set access control right of the software component package under the Download subtree. An example of assigning access control to a specific executable node is as follows: The Download / Pkg1 / Operations / DownloadInstall node executes the installation operation, the access control right for Download / Pkg1 is Get = ServerA & Race = ServerA, and the access control right for Download / Pkg1 / Operations / DownloadInstall is Get = ServerA & Exec = Server A. Currently, the control node access control generated for the same software component under the Deployed subtree is Get = ServerB & Release = ServerB. Access control rights for all executable nodes under Operations, Get = ServerB & Exec = ServerB. After the terminal updates the management node information for the same component under the Deployed subtree, the terminal can set ServerA as a new server with access and management rights, or the terminal can control access to the new management node. You can set Get = ServerA + ServerB & Release = ServerA + ServerB as the right, or the terminal sets the access control right in the null ACL so that the management node inherits the access control right of its parent node. Alternatively, the terminal can set specific access control rights such as Get = *.
The method of assigning access control rights to the subnodes of the management node is as follows. The subnode inherits the access control rights of the management node, or the terminal transfers the access control rights of the management node corresponding to the software component package under the Download subtree to the subnode of the management node under the Deployed subtree. The allocation or the terminal sets the access control right of the Download subtree as the access control right of the executable subnode of the management node under the Deployed subtree, that is, the three executable subnodes of Operations under the Deployed subtree, Activated, Access control rights for Deactivated and Remove, access control rights for executable subnodes (Download, DownLoadInstall, and DownLoadInstallInactive) under Operations on the management node under the Download subtree, and preferably installation operations under the Download subtree. Set the access control right of the executable subnode that executes. For example, if the installation command is DownLoadInstall, the executable node that executes the command is Download / Pkg1 / Operations / DownloadInstall, and the access control right is Get = * & Exec = ServerA. The terminal then assigns Get = * & Exec = ServerA to all executable nodes under Delivered / Pkg1 / Operations.
This combination of access controls allows Server B to operate the management node after the management node has been updated, but can weaken security. The user can choose the correct method for assigning access control rights based on actual needs.
Regardless of whether the installation is successful, the terminal must report an installation response message to the DM server. The difference is that the terminal also needs to report a failure message to the DM server if the installation fails. The reporting mode can be synchronous or asynchronous. In the asynchronous case, the terminal sends a Generic Alert. The information reported via asynchronous reporting includes Result Code, Source, AlertType, and Correlator, where the Result Code is communicated within the Item / Data element of the Generic Alert. The Source element conveys the URI of the node that executes the installation instruction. If the installation is successful, the Target element must convey the URI of the corresponding management node under the Deployed subtree, and the download will succeed but the installation will fail (Result Code: 60) If the corresponding management node is created under the Delivered subtree, the Target element must also convey the URI of the management node generated under the Delivered subtree. In addition, the reported information can also convey the name or ID of the software component. The name or ID is reported in the same way as described in step 502, where the terminal reports a download response message when the download is performed via the DownLoad instruction.
When the report is synchronous, the terminal reports the execution result via the Status command corresponding to the Exec command. The Data element of the Status command conveys the DM status code of the operation. If the installation is successful, the Status command must give the URI of the management node generated under the Deployed subtree, and can also give the Name and / or PkgID of the software component package. Specifically, the Status command conveys an Item, and the Target element of this Item conveys the URI of the management node generated under the Inventory / Deployed subtree. The Status command can convey software component information (Name or ID) and / or software component operating status code along with the execution result. Name or ID information under the Inventory / Deployed subtree can be communicated within an EMI or parallel Item or combined with data in an Item / Data element (status code must report software component operating status code). Also combined in some cases). The software component operating status code is communicated within the Data element. The synchronous report is similar to the synchronous report in step 502. See the synchronization reporting code in step 502 for an example of specific code.
Obviously, if the DM server does not deliver the parameters, the other steps of this embodiment can still be performed successfully. After the DM server receives the reported information, the terminal can proceed with subsequent actions on the software components according to that information.
2. Direct download or indirect download via DownLoad.
After the software component package is downloaded in direct download mode or indirect mode via Download, the terminal sends a download response message to the server. Upon receiving the download response message, the DM server delivers an install instruction or Install or Install Inactive to the terminal. The executable node that performs the install operation is Inventory / Delivered / <Pkg1> / Operations / Install or Inventory / Delivered / <Pkg1> / Operations / InstallInactive. In fact, installation instructions can be sent via the operating interface to an executable node that performs the installation operation. Before performing the installation, the terminal needs to determine if the DM server delivering the installation instructions has the right to act on the software component package. This allows the terminal to determine if the DM server has the right to access and manage the Inventory / Delivered / <Pkg1> / Operations / Install or Inventory / Delivered / <Pkg1> / Operations / InstallInactive executable node. Means that. When the package is downloaded directly, the access control of the Inventory / Delivered / <Pkg1> / Operations / Install or Inventory / Delivered / <Pkg1> / Operations / InstallInactive executable node is given by the DM server that delivers the download instruction. Assigned. Inventory / Delivered / <Pkg1> when the download command is Download
If the DM server meets the rights requirements (meaning that the DM server has the right to access and manage the executable node), after the installation is complete, the terminal is shown in Figure 6 or 7. Create management nodes under the Deployed subtree that correspond to the software components named ascendo_1, ascendo_2, and ascendo_3. When the terminal generates a management node for a software component in a software component package, the terminal obtains the ID of the software component and uses that ID as the value of the software component ID subnode of the management node (the ID node under the Deployed subtree). Value). The software component ID can be provided by the network, for example by a software publisher or a software component package publisher. The software component ID can be delivered to the terminal together with the software component package as metadata for the software component package, or can be delivered to the terminal independently of the software component package. The software component ID can uniquely identify the software component. The server (DM server, software publisher, or software component package publisher) can recognize the software component according to this ID. If the terminal determines that there are no management nodes under the Deployed subtree that correspond to the three identical software components before the terminal creates the management nodes for the three software components, the terminal will have ascendo_1, ascendo_2. , And the management node corresponding to the ascendo_3 software component is generated under the Deployed subtree. If such a management node exists, the terminal , Change the information of the management node and its subnodes to the information of software components. When the terminal changes the information of the management node of the software component and its subnodes, the terminal retains the value of the existing PkgIDRef subnode (the old software component corresponding to the management node whose value is the PkgID of the old software component package). To keep the association between the old software component package and the old software component package, and add a new association (to store the association between the installed software component package and the software component in the software component package that corresponds to the management node. Add a PkgIDRef node under the Deployed subtree). Therefore, multiple PkgIDRef nodes may exist under the Deployed subtree. Whatever the judgment result, the terminal assigns access control rights to the updated or newly generated management node and the subnodes of the management node. The allocation method here can be the same as the method used in the indirect download mode via DownLoadInstall or DownLoadInstallInactive described above. Add a PkgIDRef node under the tree). Therefore, multiple PkgIDRef nodes may exist under the Deployed subtree. Whatever the judgment result, the terminal assigns access control rights to the updated or newly generated management node and the subnodes of the management node. The allocation method here can be the same as the method used in the indirect download mode via DownLoadInstall or DownLoadInstallInactive described above. Add a PkgIDRef node under the tree). Therefore, multiple PkgIDRef nodes may exist under the Deployed subtree. Whatever the judgment result, the terminal assigns access control rights to the updated or newly generated management node and the subnodes of the management node. The allocation method here can be the same as the method used in the indirect download mode via DownLoadInstall or DownLoadInstallInactive described above.
Therefore, when the terminal reports the installation response message to the DM server, the reporting mode can also be synchronous or asynchronous. In the case of asynchronous reporting, the response message is sent via Generic Alert and the reported information includes Result Code, Source, Target, AlertType, and Name, where Result Code is Generic. Communicated within the Alert's Item / Data element. The Source element conveys the URI of the node that executes the installation instruction. The Target element conveys the URI of the Deployed subtree after the software component has been installed. In addition to the above information, the response message should also convey the name or ID of the software component. The form in which the name or ID is reported is the same as in step 502 when the download response message is reported in the case of a download via DownLoad. The DM server determines the installed software components and the corresponding management tree according to the information reported by the terminal. Based on this information, the terminal can perform subsequent management actions on the software components.
When the report is synchronous, the terminal reports the execution result via the Status command corresponding to the Exec command. The Data element of the Status command conveys the DM status code of the operation. The terminal is a management node under the Deployed subtree that contains the management node's URI for the software component, the software component ID (the ID node under the Deployed subtree) and / or the software component name (the Name node under the Deployed subtree). Also report information. The reporting method is as follows. The Status command tells the Item, and the Target element of that Item tells the URI of the management node for the installed software component, or when the status is reported, the software component information (Name or ID) and / or software. Can convey the component operating status code. The name or ID information of the management node under the Deployed subtree can be communicated within the EMI element or parallel Item, or combined with the data in the Item / Data element (the status code is the software component operating status code). Also combined if you need to report). The software component operating status code is communicated within the Data element. The synchronous report is similar to the synchronous report in step 502. See the synchronization reporting code in step 502 for an example of specific code.
Regardless of whether the reporting mode is synchronous or asynchronous, after the terminal performs a DownLoadInstall or DownLoadInstallInactive operation and generates a software component management node and its subnodes under the Deployed subtree, the terminal goes into the software component package. If the corresponding management node is also generated under the Delivered subtree of SCOMO, the installation response message will include the management node URI generated under the Deployed subtree and the management node URI generated under the Delivered subtree. Including. The server determines whether the URI indicates the address of a software component package in the SCOMO tree or the address of an installed software component in the SCOMO tree, according to the URI conveyed in the Item / Data element of the reported message. .. The specific judgment method is as follows. The server checks if the URI contains a Delivered or Deployed string, and if it does, the URI indicates the address of the package in the SCOMO tree, otherwise the URI is SCOMO. Indicates the address of the installed software component in the tree. The following is an example of a message that is reported asynchronously. <Alert> <CmdID> 2 </ CmdID> <Data> 1226 </ Data> <!-Generic Alert-> <Correlator> abc123 </ Correlator> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg1/Operations/DownloadInstall </ LocURI> </ Source> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg1 </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> text / plain </ Format> </ Meta> <Data> ... </ Data> </ Item> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg1/Operations/DownloadInstall </ LocURI> <Source> <Target> <LocURI> ./SCOMO/Inventory/Deployed/Com1 </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org. openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> chr </ Format> </ Meta> <Data> ... </ Data> </ Item> </ Alert>
In this embodiment of the invention, this process can be a parameter-based installation process. Other installation steps are unaffected, regardless of the presence of the parameter. After the installation is complete, you can call the Remove executable node to remove the installed components.
The terminal provided in the embodiment of the present invention shown in FIG. 10 includes a receiving unit 11, a download unit 12, and an installation unit 13. The receiving unit 11 is adapted to receive the software component package delivered by the DM server or the download address of the software component package and the command to instruct the download, where the software component package comprises a plurality of software components. The download unit 12 is adapted to download the software component package according to the download address when the receiving unit 11 receives the download address and the command to instruct the download. Installation unit 13 is adapted to install the obtained software component package locally and generate the management node and its subnodes corresponding to the software component under the Deployed subtree.
Successful download if the command to instruct the download is DownLoad, after the software component package has been downloaded, before the software component package has been installed, or if the command to instruct the download is DownLoadInstall or DownLoadInstallInactive. However, if the installation fails, the terminal further includes a first generation unit 14 and a first rights allocation unit 15. The first generation unit 14 is adapted to generate the management node corresponding to the software component package under the Delivered subtree, and the first rights allocation unit 15 assigns access control rights to the management node and the management node subnodes. Is adapted to.
Before the management node corresponding to the software component package is generated under the Delivered subtree, the terminal further contains the first decision unit 16, which has the ID of the downloaded software component package Delivered. Determines if it is the same as the ID of the software component package that corresponds to the management node that already exists under the subtree, and if so, the software component package that downloaded the information for the management node under the Delivered subtree. If not, it will be adapted to generate a management node under the Delivered subtree that corresponds to the downloaded software component package.
Before receiving the information, the receiving unit 11 is further adapted to generate a management node for the software component package under the Download subtree, and the first allocation unit 15 is the management generated under the Download subtree. Set the access control of the node as the access control of the management node generated under the Delivered subtree, or make the management node generated under the Delivered subtree inherit the access control of its parent node. To set the access control rights of the management node to null, or set the specific access control rights of the management node generated under the Delivered subtree, or set the management node generated under the Download subtree. The access control right of is combined with the access control right of the parent node of the management node generated under the Delivered subtree, and the combined access control right is set as the access control right of the management node generated under the Delivered subtree. Further adapted as.
Before receiving the information, the receiving unit 11 is further adapted to generate a management node for the software component package under the Download subtree, and the first decision unit 16 is the downloaded software component package in the Delivered subtree. When determining that it is the same as the software component package corresponding to the management node that already exists under it, the first rights allocation unit 15 is under the management node's access control and Delivered subtree generated under the Download subtree. It is further adapted to set the sum of the existing management node access control rights as the management node access control rights under the Delivered subtree.
The first rights allocation unit 15 causes the subnode of the management node generated under the Delivered subtree to inherit the access control right of the management node, or gives the access control right of the executable node under the Download subtree to the Delivered subtree. It is also adapted to be set as the access control right of the executable node of the management node generated below.
After the download unit 12 downloads the software component package, the receiving unit 11 receives the DM command delivered by the DM server for the Delivered subtree node, and the DM server receives the DM commands assigned to that node. It determines if it has the right to execute DM commands on that node, and if the DM server has that right, it is further adapted to execute that DM command on that node, and the terminal further The second decision unit 17 determines whether the DM server has the right to access and control the nodes generated under the Delivered subtree operated by the DM command. , If so, is adapted to execute DM commands on that node.
The receiving unit 11 is further adapted to receive the parameters delivered by the DM server, and the installation unit 13 is further adapted to install the downloaded software component package locally according to the parameters.
After the installation unit 13 performs the installation, before the management node corresponding to the software component is generated under the Deployed subtree, the terminal further contains a third decision unit 18, which is the third decision unit 18. Determines if one software component in a software component package is the same as the software component that corresponds to a management node that already exists under the Deployed subtree, and if so, manages under the Deployed subtree. It changes the node information to the software component information in the software component package, otherwise it is adapted to generate the management node corresponding to the software component in the software component package under the Deployed subtree.
Before receiving the software component package delivered directly by the DM server via the DM command, the receiving unit 11 should generate the management node corresponding to the software component package under the Delivered subtree according to the instruction of the DM server. Where the management node further contains software component information, the terminal further contains a second generation unit 19, and the second generation unit 19 contains software component information contained in the management node under the Delivered subtree. Is adapted to be stored in the Deployed subtree.
After the management node corresponding to the software component is generated under the Deployed subtree, the terminal further includes a second rights assignment unit 20 adapted to assign access control rights to the management node and its subnodes.
The second right allocation unit 20 sets the access control right of the management node corresponding to the software component package generated under the Delivered subtree or Download subtree as the access control right of the management node generated under the Deployed subtree. Alternatively, set the access control of the management node to null so that the management node generated under the Deployed subtree inherits the access control of its parent node, or generate it under the Deployed subtree. Set the specific access control right of the management node to be created, or set the access control right of the management node under the Delivered subtree or Download subtree and the access control right of the parent node of the management node generated under the Deployed subtree. It is also adapted to combine and set the combined access control rights as the access control rights of the management node generated under the Deployed subtree.
The second right allocation unit 20 causes the subnode of the management node generated under the Deployed subtree to inherit the access control right of the management node, or gives the access control right of the executable node under the Delivered subtree or Download subtree. It is also adapted to be set as the access control right of the executable node of the management node generated under the Deployed subtree.
After the management node corresponding to the software component is generated under the Deployed subtree, receiving unit 11 receives the DM command delivered by the DM server for the Deployed subtree node and the access control assigned to that node. According to the rights, determine if the DM server has the right to execute the DM command on the node, and if the DM server has the right, execute the DM command on the node. Further adapted to, the terminal further includes a 4th judgment unit 21, which accesses and manages the nodes generated under the Deployed subtree operated by the DM server by the DM server. Determines if you have the right and, if so, is adapted to execute the DM command on that node.
If the command instructing the download conveys DownLoad as an indirect download command, the terminal further includes a reporting unit 22 after the download is successful and before the software component package is installed, and the reporting unit 22 downloads. Adapted to report the response message to the DM server, where the download response message contains the management node URI generated under the Delivered subtree. After the management node corresponding to the software component is generated under SCOMO's Deployed subtree, reporting unit 22 is further adapted to report the installation response message to the DM server, where the installation response message is the Deployed subtree. Contains the URI of the management node generated under.
Download and install response messages are reported in synchronous or asynchronous mode.
When the reporting mode is synchronous, reporting unit 22 is further adapted to convey the URI in the download or install response message via the Target subelement of the Item element of the Status command.
The download response message further includes the name and / or ID of the software component package, and the installation response message further includes the name and / or ID of the software component.
When DownLoad is used to indicate a direct or indirect download, the terminal should set Installed to the state of the software component package after generating the management node corresponding to the software component under the Deployed subtree. Also includes a adapted setting unit 23.
The workflow of the terminal provided in the embodiment of the present invention is shown in FIG. This workflow includes:
Step 1101: The terminal receives a software component package or a command to download the software component package delivered by the DM server, where the software component package comprises multiple software components.
Step 1102: When the terminal receives the download address and the command to instruct the download, the terminal downloads the software component package according to the download address.
Step 1103: The terminal installs the obtained software component package locally and creates a management node corresponding to the software component and a subnode of that management node.
In order to increase the security of the terminal, it is necessary to assign access control rights to the management nodes and subnodes generated by the terminal. In the download process, the specific action steps are: Successful download if the command to instruct download is DownLoad, after the software component package is downloaded, before the software component package is installed, or if the command to instruct download is DownLoadInstall or DownLoadInstallInactive. However, if the installation fails, the terminal creates a management node corresponding to the software component package under the Delivered subtree of SCOMO and assigns access control rights to that management node and each subnode of that management node.
Before the management node corresponding to the software component package is generated under the Delivered subtree, in order to avoid data redundancy and realize the software component upgrade, the terminal has the ID of the downloaded software component package, Delivered. You need to determine if it is the same as the ID of the software component package that corresponds to the management node that already exists under the subtree, and if so, the terminal will display information about the management node under the Delivered subtree. Change the information to the downloaded software component package, otherwise the terminal will generate a management node under the Delivered subtree that corresponds to the downloaded software component package.
If the management node has already been generated for the software component package under the Download subtree before the terminal receives the information delivered by the DM server, one way to assign access control is: Is. The terminal sets the access control right of the management node generated under the Download subtree as the access control right of the management node generated under the Delivered subtree. If the terminal determines that the downloaded software component package is the same as the software component package that corresponds to the management node that already exists under the Delivered subtree, another way to assign access control is: Is. The terminal adds the access control rights of the management node corresponding to the software component package generated under the Download subtree to the access control rights of the management node that already exists under the Delivered subtree of the management node under the Delivered subtree. Set as access control right.
In addition to assigning access control rights to the management node, the terminal also needs to assign access control rights to the management node subnodes. The specific method is as follows. The terminal manages the access control right of the management node to be inherited by the subnode of the management node generated under the Delivered subtree, or the access control right of the executable node generated under the Download subtree is generated under the Delivered subtree. Execution of node Set as access control right of node.
After the terminal downloads the software component package, the terminal receives the DM command delivered by the DM server for the Delivered subtree node, and the DM server issues the DM command to that node according to the access controls assigned to that node. Determines if it has the right to execute on, and if the DM server has that right, executes the DM command on that node.
If the installation process requires parameters, the terminal also receives the parameters delivered by the DM server and installs the downloaded software component package locally according to the parameters.
After the terminal performs the installation, before the management node corresponding to the software component is generated under the Deployed subtree, the terminal also has one software component in the software component package already under the Deployed subtree. Determine if it is the same as the software component that corresponds to the management node you want to play, and if so, change the management node information under the Deployed subtree to that software component information in the software component package. If not, the terminal creates a management node for that software component in the software component package under the Deployed subtree.
The terminal can generate management nodes corresponding to the software components in the software component package under the Deployed subtree in multiple ways. For example, before receiving a software component package delivered directly by the DM server via a DM command, the terminal creates (manages) a management node for the software component package under the Delivered subtree according to the DM server's instructions. The node stores the software component information contained in the management node under the Delivered subtree (including software component information) in the Deployed subtree.
After the terminal generates the management node corresponding to the software component in the software component package under the Deployed subtree, the terminal needs to assign access control rights to the management node and its subnodes.
Methods for assigning access control rights include, but are not limited to: Set the access control of the management node corresponding to the software component package under the Delivered subtree or Download subtree as the access control of the management node generated under the Deployed subtree, and the management node generated under the Deployed subtree. To let the subnode of the management node inherit the access control right of the management node, or to give the access control right of the executable node under the Delivered subtree or Download subtree the access control right of the executable node of the management node generated under the Deployed subtree. To set as.
After the terminal generates the management node corresponding to the software component under the Deployed subtree, the terminal receives the DM command delivered by the DM server for the Deployed subtree node and according to the access control assigned to that node. Determine if the DM server has the right to execute the DM command on the node, and if the DM server has that right, execute the DM command on the node.
If the command instructing the download conveys DownLoad as an indirect download command, the terminal reports a download response message to the DM server after the download is successful and before the software component package is installed, where the download is made. The response message contains the management node URI generated under the Delivered subtree. After the management node corresponding to the software component is generated under the Deployed subtree of SCOMO, the terminal reports the installation response message to the DM server, where the installation response message is generated under the Deployed subtree. Contains the management node URI.
Download and install response messages are reported in synchronous or asynchronous mode.
When the reporting mode is synchronous, the terminal conveys the URI in the download or install response message via the Target subelement of the Item element of the Status command.
The download response message further includes the name and / or ID of the software component package, and the installation response message further includes the name and / or ID of the software component.
When DownLoad is used to indicate a direct or indirect download, the terminal sets Installed to the state of the software component package after generating the management node corresponding to the software component under the Deployed subtree.
An embodiment of the present invention provides a DM server. As shown in FIG. 12, the DM server includes a delivery unit 31, which delivers the software component package directly to the terminal via a DM command, or the software component package download address and Adapted to deliver a download instruction command to the terminal, where the software component package comprises a plurality of software components.
The DM server further includes a receive unit 32 adapted to receive the message reported by the terminal, where the message is generated under the Managed node's URI, Deployed subtree, which is generated under the Delivered subtree. Contains the URI of the management node to be created, the name and ID of the software component package, and one or more of the items named software component name and ID.
The delivery unit 31 is further adapted to deliver parameters to the terminal before the terminal installs the software component package.
The delivery unit 31 includes the first instruction unit 33 and the transmission unit 34, and the first instruction unit 33 generates a management node for the software component package under the Download subtree when the download is indirect, and the management node of the management node Instruct the terminal to add a subnode, generate a management node for the software component package under the Delivered subtree if the download is direct, and instruct the terminal to add a subnode of the management node. And the transmit unit 34 is adapted to send parameters to the subnodes added under the Download or Delivered subtree.
The delivery unit 31 is further adapted to deliver the parameters to the terminal via a DM command, which directs the terminal to perform an installation.
The DM server further includes a second instruction unit 35, which manages the software component package corresponding to the software component package before the delivery unit 31 delivers the software component package directly to the terminal via the DM command. Adapted to instruct the terminal to generate a node under the Delivered subtree, where the management node contains software component information.
The workflow of the DM server provided in the embodiment of the present invention is shown in FIG. This workflow includes:
Step 1301: The DM server delivers the software component package directly to the terminal via the DM command, or delivers the download address of the software component package and a command to the terminal, where the software component package is Includes multiple software components.
Step 1302: The DM server receives the message reported by the terminal, and the message is the management node URI generated under the Delivered subtree, the management node URI generated under the Deployed subtree, and the software component package. Contains the name and ID, as well as one or more of the items named Name and ID of the software component.
Step 1303: The DM server delivers the parameters to the terminal before the terminal installs the software component package. Delivery methods can include:
1. If the download is indirect, the DM server will generate a management node for the software component package under the Download subtree and instruct the terminal to add a subnode for that management node, or the download will be direct. If, the DM server creates a management node for the software component package under the Delivered subtree and tells the terminal to add a subnode for that management node, after which the DM server will either create a Download subtree or Delivered. Deliver parameters to subnodes added below the subtree.
2. The DM server delivers parameters to the terminal via a DM command, which instructes the terminal to perform the installation.
Before the DM server delivers the software component package directly to the terminal via the DM command, the DM server tells the terminal to create a management node for that software component package under the Delivered subtree. The management node contains software component information.
The features recorded in the first embodiment can be parallel. For example, the technical characteristics of receiving delivered parameters by a terminal in different download processes, the technical characteristics of assigning access control to management nodes and subnodes generated by the terminal, the name or ID of the management node, and Technical features of reporting the target management node's URI to the DM server synchronously or asynchronously, techniques for determining if there is a management node that corresponds to the same software component or the same software component package. Parallel or combine features, technical features for handling successful downloads and unsuccessful installations, and technical features for including software component information in the management node that corresponds to the software component package. be able to. There are multiple possible combinations. The next two embodiments are described to show that the features can be combined in any way.
In the second method embodiment of the present invention, the download and installation are performed via the DownLoadInstall instruction in the case of indirect download. In this embodiment, the DM server is ServerA, the software component package name is ascendo, and the software component package ID is PkgID_2. The software component package contains three software components named ascendo_1, ascendo_2, and ascendo_3. The software component IDs are ComID_1, ComID_2, and ComID_3, respectively. The download is successful, but the installation fails. A flow chart including the following is shown in FIG.
Step 1401: The terminal downloads and installs the software component package.
ServerA creates a management node for the software component package under the DCOMO Download subtree on the terminal and populates it with a value that includes the software component package name, version, download address, and parameters, as shown in Figure 15. Instruct the terminal to assign it to the management node. The parameter delivery process can be the same as that described in the first embodiment, or it can be a separate process.
After the management node corresponding to the software component package is generated under the Download subtree, ServerA assigns access control to the management node and subnodes. For example, Get = * & Add = ServerA & Replace = ServerA is set for the access control right of the Download / Pkg2 management node. The access control right for the Download / Pkg2 / Operations / DownloadInstall subnode is Get = * & Exec = ServerA. Other subnodes inherit the access control rights of their parent node.
Next, ServerA sends an Exec command to the terminal, where the Target element indicates that the executable node that performs the download operation is Download / Pkg2 / Operations / DownloadInstall. Specific actions can be performed via the following programs. <Exec> <CmdID> 4 </ CmdID> <Correlator> abc123 </ Correlator> <Item> <Target> <LocURI> ./SCOMO/Download/Pkg2/Operations/DownloadInstall </ LocURI> </ Target> </ Item> </ Exec>
After downloading the software component package, the terminal installs the software component package directly. Suppose the installation fails for some reason and the software component package is retained in the terminal.
Step 1402: The terminal creates a management node corresponding to the software component package under the Delivered subtree and assigns access control to the management node and its subnodes.
Before generating the management node corresponding to the software component package under the Delivered subtree, the terminal has the same management node corresponding to the software component package as the downloaded software component package that already exists under the Delivered subtree. It is necessary to determine whether or not. In the absence of such a management node, the terminal will generate a Delivered / Pkg2 management node with Delivered / Pkg2 unique information, including name, version, and parameter information, as shown in Figure 16. Store in the new Delivered / Pkg2 management node, otherwise the terminal will change the existing Delivered / Pkg2 information to the information in the current software component package. Similarly, regardless of whether the same management node exists, the terminal assigns access control rights to the Delivered / Pkg2 management node and its subnodes in the same process as in the first embodiment.
Step 1403: The terminal reports Delivered / Pkg2 management node information to Server A.
After the Delivered / Pkg2 management node is created, the terminal reports the management node URI and Delivered / Pkg2 / NAME information to ServerA via the Alert command, as included in the following program. <Alert> <CmdID> 2 </ CmdID> <Data> 1226 </ Data> <!-Generic Alert-> <Correlator> abc123 </ Correlator> <Item> <Source> <LocURI> ./SCOMO/Download/Pkg2/Operations/DownloadInstall </ LocURI> </ Source> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg2 </ LocURI> </ Target> <Meta> <Type xmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> </ Meta> </ Item> </ Alert>
After ServerA receives the operation result reported by the terminal as well as the URI information transmitted, ServerA can initiate the Install operation directly on the Delivered subtree. This eliminates the re-download process and thus reduces network and terminal load.
Similar to the terminals described above, terminals and DM servers can be provided according to the second embodiment. The terminal and the DM server can utilize the technical method described in the second embodiment to carry out the steps of the second embodiment.
In the third embodiment, Server A uses the direct download mode. In this embodiment, the name of the software component package is ascendo and the ID of the software component package is PkgID_3. The software components in this software component package are named ascendo_1, ascendo_2, and ascendo_3 and are identified as ComID_1, ComID_2, and ComID_3. After the download is complete, the Install executable node will perform the installation, as shown in Figure 17.
Step 1701: Server A delivers the software component package directly to the Delivered / Pkg3 / Data node.
ServerA creates a Pkg3 management node for the software component package under the Delivered subtree and assigns the management node a value that includes the software component name, version, and parameter information, as shown in Figure 18. ServerA assigns access control rights to the management node. For example, Get = * & Add = * & Replace = ServerA is set for the access control right of Delivered / Pkg3. The access control right of the executable subnode of Delivered / Pkg3 / Operations is Get = * & Exec = ServerA.
Step 1702: ServerA instructs the terminal to perform the installation through the Inventory / Delivered / Pkg3 / Operations / Install executable node. Specifically, this can be done via the following program: <Exec> <CmndID> 5 </ CmdID> <Correlator> abc123 </ Correlator> <Item> <Target> <LocURI> ./SCOMO/Inventory/Delivered/Pkg3/Operations/Install </ LocURI> </ Target> </ Item> </ Exec>
After receiving the installation instruction, the terminal determines the rights of Server A. If the judgment results indicate that Server A has access to Inventory / Delivered / Pkg3 / Operations / Install and has the right to control it (meaning that the DM server has Exec rights), the terminal is a software component. Instructs the package's Install program to install the software component package and returns the Exec command Status Code 202 to Server A. Status Code 202 indicates that the terminal has successfully received the data and is currently processing the data. If the installation process requires parameters, the terminal can obtain the parameters from Inventory / Delivered / Pkg3 / Install Para.
Step 1703: The terminal determines if the same software component management node as the software component in the software component package exists under the Deployed subtree.
This embodiment employs, for example, a software component named ascendo_1. Assume that there is no management node under the Deployed subtree that has the software component name (Name node) as ascendo_1. The terminal then creates a management node for ascendo_1 and a subnode for that management node under the Deployed subtree and assigns values and access control rights to that management node and subnodes, as shown in FIG. The process of assigning access control rights can also be the same as in the first embodiment. For example, the terminal has access control rights for the ./SCOMO/Inventory/Deployed/Component1 node and access control rights for the ./SCOMO/Inventory/Delivered/Pkg3 node, that is, the same access control rights as Get = * & Add = ServerA & Replace = ServerA. To set. The access control right of the executable subnode of ./SCOMO/Inventory/Deployed/Component1/Operations is the same as the access control right of ./SCOMO/Inventory/Delivered/Pkg3/Operations/Install node, that is, Get = * & Exec = ServerA. Access control right is set.
Step 1704: The terminal reports to Server A the installation result, that is, the information in Deployed / Component1 including the URI and name and / or ID of Deployed / Component1.
The installation response message can be reported via the Generic Alert command, where the reported Result Code is communicated within the Generic Alert Data element and the URI to execute the installation instruction is communicated within the Source element. And the Deployed subtree path information after the component is installed is communicated within the Target element. Software component name and / or ID information is communicated within Alert's MetaInf extensible element EMI. This operation is carried out via the following program. <Alert> <CmdID> 6 </ CmdID> <Data> 1226 </ Data> <!-Generic Alert-> <Correlator> abc123 </ Correlator> <Item> <Source> <LocURI> ./SCOMO/Inventory/Delivered/Pkg3/Operations/Install </ Source> <Target> <LocURI> ./SCOMO/Inventory/Deployed/Component1 </ LocURI> </ Target> <Meta> <Typexmlns = "syncml: metainf"> org.openmobilealliance.softwarecomponent.OperationComplete </ Type> <Format xmlns = "syncml: metainf"> text / plain </ Format> <Mark xmlns = "syncml: metainf"> critical </ Mark> <EMI xmlns = "syncml: metainf"> ComID_1 </ EMI> <!-ID of a component under the Deployed subtree-> </ Meta> <Data> 200 </ Data> <!-Result Code -> </ Item> </ Alert>
The information reported by EMI can be a name and / or an ID.
Similar to the terminals described above, terminals and DM servers can also be provided according to the third embodiment. The terminal and the DM server can utilize the technical methods described in the third embodiment to carry out the steps of the third embodiment.
It will be appreciated by those skilled in the art that all or part of the steps of the aforementioned embodiments can be performed by hardware that follows the instructions of the program. The program can be stored on a computer-readable storage medium. When the program is executed, the steps of the above embodiment are performed and the storage medium can be any read-only memory (ROM), random access memory (RAM), magnetic disk, and compact disk that can store the program code. It can be a medium.
The following benefits can be obtained using the first, second, and third embodiments described above as well as the systems and terminals described above.
1. Parameters are supported in software component package installations, so users can utilize the device to generate more flexible software component packages without having to generate a specific software component package for each installation. Can be done. This reduces the load on the server and allows for a personalized installation of the same software component package, thus giving a better user experience.
2. In the prior art, the DM server assigns access control rights to the management node created by itself, but cannot or is reasonable to set access control rights for the management node generated later by the terminal. Access control right cannot be set. As a result, security is weakened. By setting access control rights for the management node and its subnodes generated by the terminal, the specified device can manage the data and is therefore more reliable.
3. The terminal reports the software component package name, software component name, and URI information to the DM server, so that the DM server can recognize the software component more accurately, and therefore the DM server operates subsequently. Will be easier to do.
4. When the terminal creates a management node, the terminal determines if the same management node already exists under the subtree. This reduces the redundancy of software components in the terminal, allows updates and upgrades of software components in the terminal, and thus ensures that the software components in the terminal are up to date.
5. Software component packages that are successfully downloaded but fail to install are processed so that the software component package can be installed again later. This eliminates the hassle of re-downloading for reinstallation and reduces the load on the network and servers.
6. When the management node corresponding to the software component package is generated, the management node contains the information of the software component, and as a result, later, the management node corresponding to the software component is generated after the installation is successful. Becomes convenient.
Although the present invention has been described through some exemplary embodiments, the invention is not limited to such embodiments. It will be apparent that one of ordinary skill in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. The present invention is intended to include these modifications and variations, provided they are within the scope of protection defined by the appended claims or their equivalents. There is.
1 DM server 2 terminals 11 Receiving unit 12 download unit 13 Installation unit 14 1st generation unit 15 1st rights allocation unit 16 1st judgment unit 17 Second judgment unit 18 Third Judgment Unit 19 Second generation unit 20 Second rights allocation unit 21 4th judgment unit 22 Reporting unit 23 Setting unit 31 Delivery unit 32 receiving unit 33 1st instruction unit 34 Transmission unit 35 2nd instruction unit
25 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25
Every citation, both waysCites: the store holds 3 of 4
| Document | Relation | Office |
|---|---|---|
| US20060190608A1 | Cites | United States of America |
| US20060236325A1 | Cites | United States of America |
| JP2005085281A | Cites | Japan |
| Software Component Management Object,Open Mobile Alliance,2007年 5月25日,Draft Version 1.0,URL,http://member.openmobilealliance.org/ftp/Public_documents/DM/SCOMO/Permanent_documents/OMA-TS-SCOMO-V1_0-20070525-D.zip | Non-patent | – |
32 members in 7 offices
Priority claims18
| Document | Office | Kind | Date |
|---|---|---|---|
| 200710111788 | China | A | |
| 200710111788 | China | A | |
| 2007101117883 | China | – | |
| 200710123436 | China | A | |
| 200710123436 | China | A | |
| 200710123436X | China | – | |
| 200710130148 | China | A | |
| 200710130148 | China | A | |
| 2007101301487 | China | – | |
| 2007101117883 | – | – | – |
| 200710123436X | – | – | – |
| 2007101301487 | – | – | – |
| CN200710111788 | – | – | – |
| CN200710123436 | – | – | – |
| CN200710130148 | – | – | – |
| CN20071111788 | – | – | – |
| CN20071123436 | – | – | – |
| CN20071130148 | – | – | – |
Members32
| Document | Office | Kind | |
|---|---|---|---|
| CN101325509A | China | A | |
| WO2008151571A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP2104274A1 | European Patent Office (EPO) | A1 | |
| KR20090106537A | Republic of Korea | A | |
| US2009271781A1 | United States of America | A1 | |
| JP2010518497A | Japan | A | |
| CN101325509B | China | B | |
| CN102006333A | China | A | |
| CN102006334A | China | A | |
| US2011179410A1 | United States of America | A1 | |
| US2011252417A1 | United States of America | A1 | |
| KR101074886B1 | Republic of Korea | B1 | |
| US8082352B2 | United States of America | B2 | |
| US2012042308A1 | United States of America | A1 | |
| US8239859B2 | United States of America | B2 | |
| US8245225B2 | United States of America | B2 | |
| US8261262B2 | United States of America | B2 | |
| EP2104274A4 | European Patent Office (EPO) | A4 | |
| US2012284706A1 | United States of America | A1 | |
| CN102006333B | China | B | |
| CN102006334B | China | B | |
| JP2013069327A | Japan | A | |
| JP5231455B2 | Japan | B2 | |
| US2014137103A1 | United States of America | A1 | |
| JP2014179128A | Japan | A | |
| US8910151B2 | United States of America | B2 | |
| US9141366B2 | United States of America | B2 | |
| EP2104274B1 | European Patent Office (EPO) | B1 | |
| EP3002930A1 | European Patent Office (EPO) | A1 | |
| JP5954635B2This record | Japan | B2 | |
| EP3002930B1 | European Patent Office (EPO) | B1 | |
| ES2768703T3 | Spain | T3 |
17 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 5954635
- Publication, DOCDB
- 5954635
- Publication, EPODOC
- JP5954635B
- Application
- 110103
- Application, DOCDB
- 2014110103
- Application, EPODOC
- JP20140110103
Titles2
- Japanese
- ソフトウェアコンポーネントをインストールする方法、システム、端末、およびデバイス管理サーバ
- English
- How to install software components, systems, terminals, and device management servers
Classification
- CPC, 9
- G06F8/61
- G06F21/12
- H04L67/125
- H04L67/34
- H04W4/50
- H04L65/00
- G06F11/1433
- G06F8/65
- G06F8/60
- IPC, 2
- G06F9 445
- H04W4 50
