KR20120115171A - Software component information retrieving method for scomo and related service system - Google Patents

Abstract

PURPOSE: An SCOMO(Software Component Management Object) and a method for searching for software component information for a related service system are provided to let an SCOMO client know the auailability of software components in an SCOMO server by matching a download low tree with the software components. CONSTITUTION: A first message is received from an SCOMO client(402). The first message includes a warning type. The warning type is used to confirm an available software component in an SCOMO server. If the available software component is detected, a low tree of an SCOMO tree is formed in the SCOMO client(404). The low tree is matched with the available software component and includes information about the available software component. [Reference numerals] (400) Start; (402) A SCOMO client transmits a first generic alert message with a first warning type to a SCOMO server; (404) When a software component available for the SCOMO server is confirmed, one or more download low trees are generated within the SCOMO client; (406) End

Description

How to retrieve software component information for SCCO and related service systems {SOFTWARE COMPONENT INFORMATION RETRIEVING METHOD FOR SCOMO AND RELATED SERVICE SYSTEM}

Cross reference of related application

This application claims the benefit of US Provisional Application No. 61 / 472,641, filed April 7, 2011, entitled "Retrieving Available Software Components Mechanism for Software Component Management Object," the entire contents of which are incorporated herein by reference. .

The present application relates to a method used in a service system, and more particularly, to a method of searching for software components for SCOMO of a service system.

The Open Mobile Alliance (OMA) was established to develop OMA specifications for mobile services that meet the needs of users. The OMA specification also aims to provide interoperable mobile services between geographic regions (eg, countries), operators, service providers, networks, operating systems and mobile devices. In detail, the mobile service based on the OMA standard can be used by the user without restriction on a specific operator and service provider. OMA-compliant mobile services also do not depend on bearers, i.e. bearers carrying mobile services are second generation (2G) mobile systems such as GSM, EDGE or GPRS or third generation (3G) and UMTS, LTE or LTE-. It may be beyond a mobile system such as Advanced. In addition, mobile services can be run on operating systems such as Windows, Android, or Linux that run on various mobile devices. Thus, industries that provide devices or mobile services that support the OMA specification can benefit from the growing market made possible by the interoperability of mobile services. In addition, users of devices or mobile services that support the OMA specification may also have a better experience due to the interoperability of mobile services.

Device management (DM) based on the OMA specification is designed for the management of mobile devices such as cell phones, PDAs and palm top computers. Device management is typical use: configuration of the device to allow changes to the device's settings and parameters, provision of new software (e.g., application and system software) and / or software upgrades to correct bugs loaded on the device, And defect management for error reporting from the device, and / or queries about the status of the device.

A management object is an entity that can be manipulated by management actions delivered through the OMA DM protocol. A managed object can be as small as an integer or as large and complex as a wallpaper, screen saver, or security certificate. The OMA DM protocol is neutral for the content and values of managed objects and treats node values as opaque data.

In the OMA DM working group, a SCOMO (Software Component Management Object) has been proposed to enable remote software component management within a device. This can be used, for example, to update antivirus software or browser plug-ins and the like. Management tasks are defined by SCOMO for the purpose of managing software components for device support delivery, download, installation, update, removal, activation and deactivation. SCOMO is for managing other types of software assets besides firmware. Examples of software components include applications, executables, libraries, UI elements, certificates, licenses, and so on. In addition, retrieval of a list of software components of the device is supported. The list includes software components provided through SCOMO and may include those installed outside of SCOMO, such as at the factory or by an end user.

1, a schematic diagram of a SCOMO tree of the prior art. Managed objects associated with software component management are assembled under an anonymous, internal node x, which is dynamically or statically generated. SCOMO tree has a well-defined structure, with Ext nodes specified to allow nonstandard extension nodes. The general structure of a SCOMO tree is as follows:

1. Download: A subtree containing pre-delivery information and actions used to trigger the deployment and installation of a distribution package using an indirect distribution mechanism.

2. Inventory: A subtree containing post-delivery information and actions.

2.1. Inventory / Delivered: Subtree containing post-deployment (but pre-installation) information for the Delivery Package. This subtree is created by the device after using the indirect deployment mechanism or by the server before using the indirect deployment mechanism. This subtree contains the actions for installation and removal.

2.2. Inventory / Deployed:

Subtree that contains actions for activating, deactivating, and removing, as well as information from the Deployment Component.

SCOMO In the current design, when the SCOMO server wants to download a software component to an SCOMO client, the SCOMO server has a "Download" that contains information of the software component, including the download URI, package type, and other information within the SCOMO client. "Create a subtree. The SCOMO server triggers an Exec command on the SCOMO client to download this software component. However, the SCOMO client does not know how many software components are available in the SCOMO server. Some of these software components may not be available for download yet.

Accordingly, the disclosed invention provides a method for retrieving a software component for a software component management object (SCOMO) of a service system.

A method of retrieving software component information for an SCOMO client of a service system is disclosed. The software component information retrieval method includes sending a message containing an alert type to an SCOMO server, wherein the alert type is used to identify software components available at the SCOMO server.

A software component information retrieval method for an SCOMO server of a service system is disclosed. The software component information retrieval method includes: receiving a message from an SCOMO client, the message comprising an alert type, wherein the alert type is used to identify a software component available at the SCOMO server; And when a available software component is found, generating a subtree of an SCOMO tree in the SCOMO client, the subtree corresponding to the available software component and providing information of the available software component. Include.

A method of retrieving software component information for an SCOMO client of a service system is disclosed. The software component information retrieval method includes sending a message to the SCOMO server, when the SCOMO client wants to download a particular software component, the alert type requesting the specific software component. Used to

A software component information retrieval method for an SCOMO server of a service system is disclosed. The software component information retrieval method includes receiving a message from an SCOMO client, the message comprising an alert type and the alert type being used to request a particular software component; Upon receipt of the message, creating a subtree of an SCOMO tree in the SCOMO client in preparation for a download request of the particular software component to the SCOMO client, the subtree corresponding to the particular software component and Contains information of the particular software; And when the Download subtree is successfully created, sending a second message to an SCOMO client to initiate a software component download process defined in an SCOMO specification run operation under the subtree. It includes.

The service system includes an SCOMO client sending a first message comprising a first alert type; And an SCOMO server that receives the first message from the SCOMO client and creates a subtree of the SCOMO in the SCOMO client, wherein the first alert type is for identifying available software components in the SCOMO server. Used, the subtree corresponds to the available software component and contains information of the available software component.

The service system includes an SCOMO client and an SCOMO server. The SCOMO client is used to send a first message that includes a first alert type when the SCOMO client wants to download a particular software component, and the first alert type is used to request a specific software component. . The SCOMO server is used to receive the first message from the SCOMO client.

After reading the detailed description of the preferred embodiment illustrated in the accompanying drawings, those skilled in the art will clearly understand the objects of the present invention.

These and other objects of the present invention will be apparent to those skilled in the art upon reading the following detailed description of the preferred embodiments, which is illustrated in various accompanying drawings.

1 is a schematic diagram of a SCOMO tree of the prior art.
2 is a schematic diagram of an exemplary service system.
3 is a schematic diagram of an exemplary communication device.
4-6 are flow diagrams of example processes.

2, FIG. 2 is a schematic diagram of a service system 20 according to an example of the present invention. The service system 20 complies with the Open Mobile Alliance (OMA) Device Management (DM) protocol and simply consists of a Software Component Management Object (SCOMO) server, and an SCOMO client. An SCOMO server is a logical entity created for the purpose of issuing SCOMO operations on a device or consuming SCOMO alerts on a device. SCOMO Client Responsible for executing SCOMO tasks. The SCOMO client consumes software components sent to the device

It is expected to relay SCOMO alerts relaying success or failure results to the SCOMO server.

Referring to FIG. 3, FIG. 3 is a schematic diagram of a communication device 30 in accordance with an example of the present invention. The communication device 30 may be the SCOMO server or the SCOMO client shown in FIG. 2, but is not limited thereto. The communication device 30 can include a microprocessor, a processor 300 such as an application specific integrated circuit (ASIC), a storage unit 310, and a communication interfacing unit 320. The storage unit 310 can be any data storage device capable of storing program code 314 accessed by the processor 300. Examples of the storage device 310 include a subscriber identity module (SIM), read-only memory (ROM), flash memory, random-access memory (RAM), CD-ROM / DVD-ROM, magnetic tapes, hard disks, flashlights, and optical data storage devices. The communication interfacing unit 320 is preferably a transceiver and can exchange signals with the server according to the processing result of the processor 300.

4, FIG. 4 is a flow diagram of a process 40 in accordance with an example of the present invention. Process 40 is used by service system 20 to retrieve available software components within the SCOMO server by the SCOMO client. Process 40 may be compiled into program code 314 and includes the following steps.

Step 400: Initiation.

Step 402: The SCOMO client sends a first generic alert message to the SCOMO server that includes the first alert type.

Step 404: Create one or more download subtrees within the SCOMO client when the SCOMO server finds an available software component.

Step 406: End.

According to this process 40, the SCOMO client sends a first Generic Alert message to the SCOMO server to query the SCOMO server whether any available software components that have not yet been downloaded by the SCOMO client exist on the SCOMO server. The first generic alert message includes a first alert type indicating that the first generic alert message is used to identify available software components in the SCOMO server. Software components are applications, executables, libraries, UI elements, certificates, licenses, and so on. The SCOMO server receives a first Generic Alert message that includes a first alert type, and a first Device Management (DM) message if any available software component exists on the SCOMO server that has not yet been downloaded by the SCOMO client. Creates a download subtree within the SCOMO client by sending it to the SCOMO client. Each download subtree corresponds to one software component. Thus, the SCOMO client can find out how many software components in the SCOMO server are available.

After the download subtree is created, if the SCOMO client wants to download a particular software component, the SCOMO client sends a second generic alert message to the SCOMO server. The second generic alert message includes a second alert type indicating that the second generic alert message is used to request a particular software component. The SCOMO server receives the second Generic Alert message with the second alert type and sends a second DM message to the SCOMO client to initiate the software component download process defined in the SCOMO specification.

In one example, a container exists in the SCOMO tree of the SCOMO client. This container is a group of subtrees in the SCOMO tree for storing available software component information, if the subtree can contain only a single node. 5, FIG. 5 is a flowchart of a process 50 according to another example of the present invention. This process 50 is used by the service system 20 to retrieve available software components within the SCOMO server by the SCOMO client. Process 500 may be compiled into program code 314 and includes the following steps.

Step 500: Initiation.

Step 502: The SCOMO client sends a first generic alert message to the SCOMO server that includes the first alert type.

Step 504: When the SCOMO server finds an available software component, it creates one or more download subtrees under the container in the SCOMO client.

Step 506: End.

According to this process 50, the SCOMO client sends a first Generic Alert message to the SCOMO server to query the SCOMO server whether any available software components that have not yet been downloaded by the SCOMO client exist on the SCOMO server. The first generic alert message includes a first alert type indicating that the first generic alert message is used to identify available software components in the SCOMO server. Examples of software components are applications, executables, libraries, UI elements, certificates, licenses, and the like. Unlike process 40, the SCOMO server receives the first Generic Alert message that includes the first alert type and sends the first DM message to create a subtree under the container in the SCOMO client. A container is a group of subtrees of the SCOMO tree for storing available software information if the subtree can contain only one node. Each subtree corresponds to one software component. Thus, the SCOMO client can find out how many software components in the SCOMO server are available.

After the download subtree is created, if the SCOMO client wants to download a particular software component, the SCOMO client sends a second generic alert message to the SCOMO server. The second generic alert message includes a second alert type indicating that the second generic alert message is used to request an available software component. The SCOMO server receives the second Generic Alert message with the second alert type and then generates a subtree that is used to download software components into the SCOMO client. If the subtree is successfully created, the SCOMO server sends a second DM message to the SCOMO client to initiate the software component download process defined in the SCOMO specification.

Referring to FIG. 6, FIG. 6 is a flowchart of a process 60 in accordance with an example of the present invention. This process 60 is used by the SCOMO client in the service system 20 to download certain software components within the SCOMO server. Process 60 may be compiled into program code 314 and includes the following steps.

Step 600: Initiation.

Step 602: The SCOMO client sends a second Generic Alert message to the SCOMO server that includes the second alert type, the second alert type being used to request a particular software component.

Step 604: When the SCOMO server receives the second Generic Alert message, it creates a "Download" subtree that is used to download the requesting software component in the SCOMO client.

Step 606: End.

According to this process 60, the SCOMO client sends a second generic alert message to the SCOMO server that includes the second alert type used to request a particular software component. The SCOMO server receives the second generic alert message and then creates a download subtree in preparation for the download request of a particular software component in the SCOMO client. If the generation of the subtree is successful, the SCOMO server sends a DM message to the SCOMO client to initiate the software component download process defined in the SCOMO specification.

The steps described above for processes including the proposed steps may be implemented by means of hardware, hardware devices and firmware known as a combination of computer instructions and data resident in read-only software on the hardware device, or means that may be an electronic system. Can be. Examples of hardware may include analog circuits, digital circuits and mixed circuits known as microcircuits, microchips, or silicon chips. Examples of electronic systems may include a system on chip (SOC), a system in package (SiP), a computer on module (COM), and a communication device 30.

In short, the SCOMO client sends a Generic Alert message to the SCOMO server to query the SCOMO server if any available software components exist on the SCOMO server that have not yet been downloaded by the SCOMO client. Generic Alert messages contain new alert types that are used to identify available software components within the SCOMO server. When the SCOMO server receives a Generic Alert message containing a new alert type, the SCOMO server sends a DM message to the SCOMO client to create a subtree within the SCOMO client. Subtree

It can be created under an existing "Download" node or container. Containers are groups of subtrees, and subtrees can be single nodes. Each generated subnode corresponds to one software component. Thus, the SCOMO client can find out how many software components are available in the SCOMO server. In another example, the SCOMO client sends a generic alert message to the SCOMO server containing the type of alert used to request a particular software component. Next, a "Download" subtree is created to prepare for a specific software component download request in the SCOMO client. If the subtree is successfully created, the SCOMO server sends a DM message to the SCOMO client to initiate the software component download process defined in the SCOMO specification.

Those skilled in the art will readily appreciate that many modifications and variations can be made to the apparatus and methods while maintaining the spirit of the invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.

Claims (16)

A method of retrieving software component information for a software component management object (SCOMO) client of a service system,
Sending a message containing an alert type to the SCOMO server,
The alert type is used to identify available software components in the SCOMO server. A method of retrieving software component information for a software component management object (SCOMO) server of a service system,
Receiving a first message from an SCOMO client, the first message comprising an alert type, the alert type being used to identify available software components in the SCOMO server; And,
When an available software component is found, creating a subtree of a SCOMO tree in the SCOMO client
Including,
And the subtree corresponds to the available software component and includes information of the available software component. The method of claim 2,
The generating of the subtree of the SCOMO tree in the SCOMO client by the SCOMO server includes generating the subtree of the SCOMO tree in the SCOMO client by sending a second message to the SCOMO client. , How to retrieve software component information. The method of claim 3,
Wherein the subtree is under a Download node of the SCOMO or under a container of the SCOMO. A method of retrieving software component information for a software component management object (SCOMO) client of a service system.
When the SCOMO client wants to download a particular software component, sending a message to the SCOMO server that includes an alert type,
Wherein the alert type is used to request the particular software component. A method of retrieving software component information for a software component management object (SCOMO) server of a service system,
Receiving a first message from an SCOMO client, the first message comprising an alert type, the alert type being used to request a particular software component; And
Upon receipt of the first message, a Download subtree of the SCOMO tree within the SCOMO client to prepare for the download of the particular software component to the SCOMO client in the absence of a Download subtree. Steps to generate
Including,
The Download subtree corresponds to the particular software component and includes information of the particular software. The method of claim 6,
When the Download subtree is successfully created, sending a second message to an SCOMO client to initiate a software component download process defined in the SCOMO specification. The method of claim 6,
The Download subtree is below the Download node of the SCOMO tree. An SCOMO client sending a first message comprising a first alert type; And
An SCOMO server that receives the first message from the SCOMO client and generates a subtree of the SCOMO in the SCOMO client
Including,
The first alert type is used to identify available software components within the SCOMO server,
The subtree corresponds to the available software component and includes information of the available software component. 10. The method of claim 9,
The SCOMO server also sends a second message to create a subtree of the SCOMO tree in the SCOMO client when an available software component is found. The method of claim 10,
The subtree is under a Download node of the SCOMO or under a container of the SCOMO. 10. The method of claim 9,
The service system is compliant with the Open Mobile Alliance (OMA) Device Management (DM) protocol. When the SCOMO client wants to download a particular software component, the SCOMO client sending a first message comprising a first alert type; And
An SCOMO server receiving the first message from the SCOMO client
Including,
The first alert type is used to request a specific software component. The method of claim 13,
The SCOMO server also, upon receipt of the first message, downloads the SCOMO in the SCOMO client to prepare for the download of the particular software component in the SCOMO client in the absence of a Download subtree. Create a Download subtree,
The Download subtree corresponds to the particular software component and includes information of the particular software component and when the Download subtree has been successfully created, the software component download process defined in the SCOMO specification. Send a second message to the SCOMO client to initiate a message. 15. The method of claim 14,
The Download subtree is below a Download node of the SCOMO tree. The method of claim 13,
The service system is compliant with the Open Mobile Alliance (OMA) Device Management (DM) protocol.

Images