CN101996074B - Method and device for managing software by using software component management object - Google Patents
Method and device for managing software by using software component management object Download PDFInfo
- Publication number
- CN101996074B CN101996074B CN200910168281.0A CN200910168281A CN101996074B CN 101996074 B CN101996074 B CN 101996074B CN 200910168281 A CN200910168281 A CN 200910168281A CN 101996074 B CN101996074 B CN 101996074B
- Authority
- CN
- China
- Prior art keywords
- software
- management object
- component management
- information
- software component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a method and a device for managing software by using a software component management object (SCOMO). The method comprises the following steps of: acquiring software information on user equipment; acquiring information of software operated in a non software component management object mode on the user equipment according to the software information; creating and allocating corresponding nodes for the software operated in the non software component management object mode under corresponding nodes of the software component management object according to the information of the ware operated in the non software component management object mode; and reporting the information of the nodes to a software component management object server. By acquiring the information of the software operated in the non SCOMO mode, creating corresponding nodes for the software operated in the non SCOMO mode under the SCOMO according to the acquired information, and reporting the corresponding node information to the SCOMO server, a problem that the software installed on terminal equipment in the non SCOMO mode by a user cannot be managed by the conventional SCOMO mode.
Description
Technical field
The present invention relates to wireless communication technology field, particularly relate to a kind of method and the device that use software component management Object Management group software.
Background technology
Open mobile alliance device management (OMA DM) system that open mobile alliance device management specification 1.2 (OMA DM V1.2) provides, the environment managed for third party and arrange in wireless network terminal equipment and configuration information, solve the problem that these wireless network terminal equipment in use run into, by wireless network (Over The Air, OTA) mode carries out the operation such as installation, upgrading of software and firmware, and hommization more and personalized service are provided, improve Consumer's Experience.Wherein, third party can be mobile operator, the information management department of service provider or partner.Wireless network terminal equipment can be the functional object in mobile phone terminal and terminal.
As shown in Figure 1, the DM client (DM Client) on terminal device is for explaining and perform the administration order that DM server issues for OMA DM system.The management tree that terminal device stores can be considered to the interface that a DM server (DM Server) is managed terminal device by DM agreement.Management tree comprises some basic management objects (Management Object, MO), and DM server crosses the object operation of management object being reached to control terminal management object.Operational order has acquisition (Get), replaces (Replace), performs (Exec), copies (Copy), deletes (Delete) etc.
Software component management object (SCOMO) in management object is used for needing the software installed or installed to manage to equipment, as shown in Figure 2.The software of SCOMO management object management can comprise program, executable file, software security certificate, registration (license) etc.Having the bookkeeping of software of SCOMO agreement support: download, distribute (delivery), install (installation), upgrade (update), remove (removal), activation/deactivation (activation/de-activation), SCOMO management object is also supported to carry out stock-taking to all softwares in terminal device in addition.
Realizing in process of the present invention, inventor finds that prior art at least exists following defect: existing SCOMO mode cannot be installed to software on terminal device by leading subscriber by non-SCOMO mode, such as user oneself downloads or has copied in installation file to terminal device and installs, and the manager of operator or these terminal devices just cannot adopt the mode of effective management tree to inquire about these softwares or manage.
summary of the invention
The embodiment of the present invention proposes a kind of method and device using software component management Object Management group software, cannot to be installed to the problem of the software on terminal device by leading subscriber to solve existing SCOMO mode by non-SCOMO mode.
Embodiments provide a kind of method using software component management Object Management group software, comprising:
Obtain the software information on subscriber equipment;
The information of the software that described subscriber equipment operates in non-software Component Management Object mode is obtained according to described software information;
The software creation that the information of the software operated according to described non-software Component Management Object mode operates for described non-software Component Management Object mode under the respective nodes of software component management object also configures corresponding node;
By the software creation operated for described non-software Component Management Object mode and the information reporting configuring corresponding node to software component management object server.
The embodiment of the present invention additionally provides a kind of method using software component management Object Management group software, comprising:
Receive the information of the node using software component management object client to report; Described node is described software component management object client is software creation in software component management object and the node of configuration; Described software is with the software that non-software Component Management Object mode operates on subscriber equipment.
The embodiment of the present invention additionally provides a kind of software component management target customer end device, comprising:
First acquisition module, for obtaining the software information on subscriber equipment;
Second acquisition module, for obtaining the information of the software that described subscriber equipment operates in non-software Component Management Object mode according to described software information;
Creation module, the software creation that the information for the software operated according to described non-software Component Management Object mode operates for described non-software Component Management Object mode under the respective nodes of software component management object also configures corresponding node;
Reporting module, for by the software creation operated for described non-software Component Management Object mode and the information reporting configuring corresponding node to software component management object server.
The embodiment of the present invention additionally provides a kind of software component management object server, comprising:
Receiver module, for receiving the information of the node using software component management object client to report; Described node is described software component management object client is software creation in software component management object and the node of configuration; Described software is with the software that non-software Component Management Object mode operates on subscriber equipment.
The information of the software that above-described embodiment is operated in non-SCOMO mode by acquisition, and be that the software operated in non-SCOMO mode creates respective nodes under SCOMO according to the information obtained, corresponding nodal information is reported as SCOMO server, solves existing SCOMO mode and cannot be installed to the problem of the software on terminal device by non-SCOMO mode by leading subscriber.
Below by drawings and Examples, technical scheme of the present invention is described in further detail.
accompanying drawing explanation
Fig. 1 is the one-piece construction schematic diagram of OMA DM system of the prior art;
Fig. 2 is the schematic diagram of SCOMO management tree in prior art;
A kind of process flow diagram using the method for software component management Object Management group software that Fig. 3 provides for the embodiment of the present invention;
The process flow diagram of the method for the another kind use software component management Object Management group software that Fig. 4 provides for the embodiment of the present invention;
The process flow diagram of management is unloaded in the method for the use software component management Object Management group software that Fig. 5 provides for the embodiment of the present invention;
The process flow diagram of the method for another the use software component management Object Management group software that Fig. 6 provides for the embodiment of the present invention;
The structural representation of a kind of software component management target customer end device that Fig. 7 provides for the embodiment of the present invention;
The structural representation of a kind of software component management object server that Fig. 8 provides for the embodiment of the present invention.
Embodiment
A kind of process flow diagram using the method for software component management Object Management group software that Fig. 3 provides for the embodiment of the present invention.The method comprises:
Step 31, the software information obtained on subscriber equipment.
This action can by the SCOMO client executing on terminal device and subscriber equipment.SCOMO client can obtain the mount message, Download Info, point photos and sending messages etc. of software from subscriber equipment.SCOMO client is carried out installation, the download of monitoring acquisition software to software or is divided photos and sending messages, or after the instruction receiving the transmission of SCOMO server end, collects installation, the download of acquisition software or divide photos and sending messages.
Step 32, obtain the information of the software that described subscriber equipment operates in non-SCOMO mode according to described software information.
This action can by the SCOMO client executing on terminal device and subscriber equipment.SCOMO client can judge whether according to the information obtained in step 31 that software carries out installing in non-SCOMO mode, download or the operation such as distribution.The information of described software is any one or combination in following information: the descriptor of dbase, software version, software.
The software creation that step 33, the information of software operated according to described non-SCOMO mode operate for described non-SCOMO mode under the respective nodes of SCOMO also configures corresponding node.
This action can by the SCOMO client executing on terminal device and subscriber equipment.SCOMO client is described software creation and configures corresponding node under the respective nodes of SCOMO.When described software is installed in non-SCOMO mode, under deployment (Deployed) node of SCOMO, be described software creation and configure corresponding node.When described software is downloaded in non-SCOMO mode, under download (Download) node of SCOMO, be described software creation and configure corresponding node.When described software is distributed in non-SCOMO mode, under distribution (Delivered) node of SCOMO, be described software creation and configure corresponding node.
, specifically comprise when configuring corresponding node when the software creation for installing in non-SCOMO mode: be described software creation bag identification reference node under the deployment node of SCOMO; For the value that described bag identification reference Joint Enterprise is installed with non-SCOMO for identifying described software.During for identifying described software with non-SCOMO installation, also can create under the deployment node of SCOMO and configure new node; Described new node is be the node installed with non-SCOMO for identifying described software.
, specifically comprise when configuring corresponding node when the software creation for downloading in non-SCOMO mode: be described software creation bag identification nodes under the deployment node of SCOMO; For described bag identification nodes is configured for the value identifying described software and download with non-SCOMO.During for identifying described software with non-SCOMO download, also can create under the download node of SCOMO and configure new node; Described new node is be the node downloaded with non-SCOMO for identifying described software.
, specifically to comprise when configuring corresponding node when the software creation for distributing in non-SCOMO mode: be described software creation bag identification nodes under the distribution node of SCOMO; For described bag identification nodes is configured for the value identifying described software and distribute with non-SCOMO.During for identifying described software with non-SCOMO distribution, also can create under the distribution node of SCOMO and configure new node; Described new node is be the node distributed with non-SCOMO for identifying described software.
Step 34, by the information reporting of described node to SCOMO server.
This action can by the SCOMO client executing on terminal device and subscriber equipment.The management subtree of described software can be identified at least one in the information of the node that described software operates in non-SCOMO mode or combination sends to described SCOMO server at the positional information of described SCOMO, described software current state information or be used for by SCOMO client.The query statement that this action also can send according to described SCOMO server performs the operation reporting the information of described node.
In the present embodiment, SCOMO client is by monitoring the software operated in non-SCOMO mode, and in SCOMO, be this software creation and configure corresponding node, SCOMO achieves the management to non-SCOMO mode function software, makes operator or other manager can by the inquiry that the basis of SCOMO extensively approved realizes to software all on subscriber equipment and management.
When the software operated in non-SCOMO mode in above-described embodiment is unloaded, the method for the use software component management Object Management group software that the embodiment of the present invention provides also can comprise:
Obtain the unloading information of the software that described non-SCOMO mode operates.This action can by the SCOMO client executing on terminal device and subscriber equipment.SCOMO client carries out software monitoring the unloading information obtaining software, or after the instruction receiving the transmission of SCOMO server end, collect the unloading information obtaining software.
When described software unloads in non-SCOMO mode, delete the node for described software creation in described SCOMO according to described unloading information.This action can by the SCOMO client executing on terminal device and subscriber equipment.
Report described software unloaded to described SCOMO server.This action can by the SCOMO client executing on terminal device and subscriber equipment.
The method of the use software component management Object Management group software that the embodiment of the present invention provides also can comprise: receive the delete instruction that described SCOMO server sends; This action can by the SCOMO client executing on terminal device and subscriber equipment.
The node of the software creation operated for described non-SCOMO mode is deleted according to described delete instruction.This action can by the SCOMO client executing on terminal device and subscriber equipment.SCOMO client deletes the node for the software creation operated in non-SCOMO mode after the delete instruction receiving the transmission of SCOMO server.
Suppose that SCOMO client deletes the nodal information of a certain software according to the delete instruction of SCOMO server, when this software is mounted, the method for the use software component management Object Management group software that the present embodiment provides also can comprise the described software of unloading.When this software is not mounted, the method for the use software component management Object Management group software that the present embodiment provides also can comprise the software physical file on a user device deleted described non-SCOMO mode and operate.
With accordingly embodiment illustrated in fig. 3, the another kind that the embodiment of the present invention provides uses the method for software component management Object Management group software to comprise:
Receive the information of the node using SCOMO client to report; Described node is described SCOMO client is software creation in SCOMO and the node of configuration; Described software is with the software that non-SCOMO mode operates on subscriber equipment.
This action can be performed by the SCOMO server end on DM server.SCOMO client is the software creation that operates in non-SCOMO mode and after configuration node, corresponding information is reported SCOMO server end, specifically refers to above-mentioned steps 34.After SCOMO received server-side to above-mentioned information, just can realize the inquiry to software all on subscriber equipment and management.
The method of the use software component management Object Management group software that the embodiment of the present invention provides also can comprise:
Send the identifier that comprises for identifying the software operated in non-SCOMO mode as the query statement of " UserPrivate ", described query statement is used for the nodal information of the software operated in non-SCOMO mode according to described identifier query.This action can be performed by the SCOMO server end on DM server.SCOMO server end just can know all information of the software that subscriber equipment operates in non-SCOMO mode by sending query statement.
The method of the use software component management Object Management group software that the embodiment of the present invention provides also can comprise:
Send delete instruction, for deleting on described subscriber equipment with the software that non-software Component Management Object mode operates.This action can be performed by the SCOMO server end on DM server.SCOMO server end just can manage the software that subscriber equipment operates in non-SCOMO mode by sending delete instruction.
The process flow diagram of the method for the another kind use software component management Object Management group software that Fig. 4 provides for the embodiment of the present invention.The method comprises:
Step 41, the software installation information obtained on subscriber equipment.
This action can by SCOMO client executing.The process that on SCOMO client monitors subscriber equipment, software is installed and information.SCOMO client can software installation information on Real-Time Monitoring subscriber equipment; Also the mode of regularly timing can be adopted to monitor the software installation information in collection during this period of time on subscriber equipment; The software installation information of collecting on subscriber equipment can also be started after the instruction receiving SCOMO server.
SCOMO client monitors collects the software installation information on subscriber equipment, the call function that can be provided by invoke user device operating system is realized, as the mobile phone of Windows Mobile system called " msi " function to obtain the list of mounting software on mobile phone; Also the mobile phone of Symbian or linux system can be realized by the journal file of the software peace loading, unloading analyzing user facility operation system, as can be obtained software installation information by reading analytic system file " installed-software.log " or " Appinist.ini ".
Step 42, obtain the information of the software that described subscriber equipment is installed in non-SCOMO mode according to described software installation information.
This action can by SCOMO client executing.SCOMO client judges that the software that subscriber equipment is installed be that SCOMO mode installs is also that non-SCOMO mode is installed.
After SCOMO client knows the information of mounting software on equipment, judge whether software is by performing SCOMO instruction " Inventory/Delivered/<X>/Opera tions/Install "
Or " Inventory/Delivered/<X>/Opera tions/InstallInactive "
Or " Download/<X>/Operations/Downl oadInstall "
Or " Download/<X>/Operations/Downl oadInstallInactive " installs, if not, then judge that this software thinks that non-SCOMO mode is installed.
To the software that SCOMO mode is installed, SCOMO client creates according to existing SCOMO agreement and configures corresponding node under deployment (Deployed) node.
Step 43, in SCOMO, configure corresponding node for described software creation according to the information of described software.
This action can by SCOMO client executing.To the software that non-SCOMO mode is installed, SCOMO client knows the information such as title, version, installation path of institute's mounting software by operational monitoring program, be this software creation node under " Deployed " node, and software information is configured in corresponding node goes.
After SCOMO client gets the information of the software installed in non-SCOMO mode, be the corresponding node of this software creation under " Inventory/Deployed/ ": " <X> ", " ID ", " PkgIDRef ", " Name ", " Version ", " Status " and " State ".
Wherein, the title of " <X> " node can by the self-defined generation of SCOMO client." ID " node is generated by SCOMO client, and the value of this node is not reproducible, is the unique identifier of this software on SCOMO." PkgIDRef " nodal value is the numbering generated according to certain algorithm by SP numbering, dbase in SCOMO agreement.In the present embodiment, the value of this node is set to the particular value distinguishing the numbering that above-mentioned algorithm generates, as distinguished the software installed in non-SCOMO mode in SCOMO with " UserPrivate ", SCOMO server can be " PkgIDRef " node of " UserPrivate " by Query Value, obtains on SCOMO all with the information of non-SCOMO mode mounting software." Name " nodal value can be the installation title of the software obtained in step 41." Version " nodal value can be the version number of the software obtained in step 41, as 1.2." Status " nodal value can be set to 10, represents that this software not yet starts to delete.If software is current in running status, " State " nodal value is 20; If the current non-operating state of software, " State " nodal value is 10.
If SCOMO client has also got the descriptor of software from step 41, also can create " Description " node here, and descriptor has been write this nodal value.
SCOMO client also can create executable node " Operations/Remove ", and like this to the software that non-SCOMO mode is installed, the execution " Operations/Remove " that also can send instructions down of SCOMO server unloads.
SCOMO server can issue the node under " Get " instruction fetch " Inventory/Deployed ", obtain the nodal information under whole " Deployed ", or just equaled " PkgIDRef " node of " UserPrivate " by read value, obtain the nodal information of the software that non-SCOMO mode is installed.
Step 44, by the information reporting of described node to SCOMO server.
This action can by SCOMO client executing.The information of the software that SCOMO client reports non-SCOMO mode to install to SCOMO server.
SCOMO client reports the state of software to be " installation " to SCOMO server, and report the positional information of this software on management tree as URL: " Inventory/Deployed/<X> ", and the value of " PkgIDRef " is reported to SCOMO server, mounted is the software installed in non-SCOMO mode to allow server know.
Correspondingly, the method for use software component management Object Management group software that the embodiment of the present invention provides can comprise:
Receive the information of the node using SCOMO client to report; Described node is described SCOMO client is software creation in SCOMO and the node of configuration; Described software is with the software that non-SCOMO mode is installed on subscriber equipment.This action can be performed by SCOMO server.The information of the node received refers to the explanation of above-mentioned steps 44.
The method of the use software component management Object Management group software that the embodiment of the present invention provides also can comprise: send query statement, for inquiring about the nodal information of the described software installed in non-SCOMO mode.This action can be performed by SCOMO server.SCOMO server is by software informations installed in non-SCOMO mode all on query statement inquiring user equipment.
The method of the use software component management Object Management group software that the embodiment of the present invention provides also can comprise: send delete instruction, for deleting the software that described subscriber equipment is installed in non-SCOMO mode.This action can be performed by SCOMO server.SCOMO server deletes all software installed in non-SCOMO mode on subscriber equipment by delete instruction.
In the present embodiment, SCOMO client is by monitoring the software installed in non-SCOMO mode, and in SCOMO, be this software creation and configure corresponding node, SCOMO achieves the management to non-SCOMO mode mounting software, makes operator or other manager the basis of SCOMO extensively approved can realized the searching and managing of the software to installations all on subscriber equipment.
The method of the use software component management Object Management group software that the embodiment of the present invention provides also can comprise carries out unloading management to software.As shown in Figure 5, specifically can comprise:
Step 51, obtain the unloading information of described software.
This action can by SCOMO client executing.SCOMO client is by whether monitoring facilities monitor user ' equipment has software unloaded.When there being software unloaded, SCOMO client executing step 52.
SCOMO client can software unloading situation on Real-Time Monitoring subscriber equipment; Also the mode of regularly timing can be adopted to monitor the software unloading situation in collection during this period of time on subscriber equipment; The software unloading situation of collecting on subscriber equipment can also be started after the instruction receiving SCOMO server.
SCOMO client monitors collects the software unloading situation on subscriber equipment, the call function that can be provided by the operating system of invoke user equipment is realized, also can by analyzing the journal file of the software unloading of user facility operation system, as the mobile phone of Symbian or linux system can obtain software unloading information by reading analytic system file " uninstalled-software.log ".
Step 52, when described software unloads in non-SCOMO mode, deleting in described SCOMO according to described unloading information is the node of described software creation.
This action can by SCOMO client executing.SCOMO client judges whether the software unloaded unloads in SCOMO mode.SCOMO client knows the information of the software that subscriber equipment unloads by step 51 after, can judge whether software unloads by performing SCOMO instruction " Inventory/Deployed/<X>/Operat ions/Remove ".If so, illustrate that the software of unloading unloads in SCOMO mode, then delete the respective nodes under " Deployed " node according to existing SCOMO agreement; If not, illustrate that the software of unloading unloads in non-SCOMO mode, then from monitoring information, obtain the information such as the title of unloaded software, delete the respective nodes under " Deployed " node, perform step 53.
Step 53, report described software unloaded to described SCOMO server.
This action can by SCOMO client executing.SCOMO client has reported software to unload in non-SCOMO mode to SCOMO server.
SCOMO client reports the state of software to be " unloading " to SCOMO server, and report the URL of this software on management tree: " Inventory/Deployed/<X> ", and the value of " PkgIDRef " is reported to SCOMO server, unloaded is the software that non-SCOMO mode is installed or unloaded to allow server know.
For the mobile phone of a Windows Mobile operating system.Suppose that this mobile phone is provided with SCOMO client, support SCOMO agreement.SCOMO client utilizes " msi " function of WindowsMobile open system on mobile phone, and list installed by the software in Real-time Obtaining current phone.When the installation file of a mobile game Fighter1.2 is downloaded from the Internet on computing machine by user, and usage data line connects mobile phone and computing machine, this installation file is copied on mobile phone, when installing, SCOMO client obtains the title Fighter of this new mounting software, version is 1.2, and installation path " Applications Fighter ".
The inspection of SCOMO client performs the record of the installation instruction of SCOMO server, know that this new mounting software is after non-SCOMO mode is installed, start under " Inventory/Deployed " node of SCOMO as this new mounting software creative management node, and the software information got be configured in corresponding node:
Create and configure the name of " <X> " node for " Fighter123 ", the name of " <X> " node can by the self-defined name of SCOMO client;
To create and the value configuring " ID " node is 000876, with this software of unique identification on whole SCOMO;
Create and configure the value of " PkgIDRef " node for " UserPrivate ", to represent that this software is the software that non-SCOMO mode is installed;
Create and configure the value of " Name " node for " Fighter ";
To create and the value configuring " Version " node is 1.2;
To create and the value configuring " State " node is 10, to represent the current off-duty of this software;
To create and the nodal value configuring " Status " is 10, to represent that this software not yet starts unloading;
Create executable node " Operations/Remove ", when SCOMO server sends to SCOMO client the instruction performing this node, SCOMO client finds Uninstaller under program installation directory " Applications Fighter ", is unloaded by this software.After unloading, SCOMO client to delete from <Fighter123> down all nodes, namely removes the full detail of this software on management tree.
After SCOMO client creates and configures corresponding node, report the information of this mounting software to SCOMO server.The information reported comprises: the positional information of management subtree on whole SCOMO " Inventory/Deployed/Fighter123 " of this software; The status information " Status=10 " of this software; And " PkgIDRef=UserPrivate ", inform that this software of SCOMO server is for user is from mounting software, namely this software is non-SCOMO mode mounting software.
Or SCOMO server can send " Get " instruction to SCOMO client and obtain whole nodal informations under " Deployed " node, obtains software installation information whole on current device; It is information under whole <X> nodes of " UserPrivate " that " Get " instruction that also can send with parameter obtains " PkgIDRef " nodal value under " Deployed " node, obtains the software matrix that in current user equipment, non-SCOMO mode is installed.
Again for the mobile phone of a Symbian operating system.This mobile phone is provided with SCOMO client equally, and supports SCOMO agreement.In the present embodiment, SCOMO client is provided with timer, within every 24 hours, inquires about the software that once in these 24 hours, on equipment, non-SCOMO mode is newly installed or unloaded, and create Maintenance Point on SCOMO.Or SCOMO client received the instruction that SCOMO server sends after 24 hours, the information of the software that the information of synchronous SCOMO and equipment are installed.SCOMO client obtains up-to-date system file " installed-software.log ", with 24 hours before the installed-software.log file that backs up contrast, analyze the information whether having new mounting software in these 24 hours.
Suppose that a book-viewer software EReader5.5 is sent on this mobile phone by bluetooth approach by user, and install.SCOMO client query is known, or by comparative analysis, SCOMO server knows that software EReader5.5 newly installed by subscriber equipment, and from journal file, obtain name, version, the information such as description and installation path of this software.
The inspection of SCOMO client performs the record of the installation instruction of SCOMO server, judges that this software is that non-SCOMO mode is installed; SCOMO client starts as this software creation management node under " Inventory/Deployed " node of SCOMO:
Create and the name configuring " <X> " node is 456EReader, the name of this node can by the self-defined name of SCOMO client;
To create and the value configuring " ID " node is 000888, with this software of unique identification on whole SCOMO;
Create and configure the value of " PkgIDRef " node for sky, to represent that this software is the software installed in non-SCOMO mode;
To create and the value configuring " Name " node is EReader;
To create and the value configuring " Version " node is 5.5;
Create and configure the value of " Description " node for " reader "
To create and the value configuring " State " node is 10, to represent the current off-duty of this software;
To create and the nodal value configuring " Status " is 10, to represent that this software not yet starts unloading;
Create and configure executable node " Operations/Active ", when SCOMO server sends to SCOMO client the instruction performing this node, SCOMO server finds startup file under program installation directory " Applications EReader ", bring into operation this software, the value of " State " node is updated to 20 simultaneously, represents that this software is in running status;
Create and configure executable node " Operations/Remove ", when SCOMO server to SCOMO client send perform the instruction of this node time, find Uninstaller under SCOMO server to program installation directory " Applications Fighter " and unload this software.After this software is unloaded, SCOMO client deletes whole nodes down from <Fighter123>, namely removes the full detail of this software on management tree.
SCOMO server can send " Get " instruction to SCOMO client and obtain whole nodal informations under " Deployed " node, obtains software installation information whole on current device; It is information under empty whole <X> nodes that " Get " instruction that also can send with parameter obtains " PkgIDRef " nodal value under " Deployed " node, obtains the software matrix that on current device, non-SCOMO mode is installed.
If SCOMO client obtains up-to-date system file " uninstalled-software.log ", with 24 hours before the system file " uninstalled-software.log " that backs up contrast, analyze in these 24 hours and whether have software unloaded.Unloaded when being checked through EReader, the inspection of SCOMO client performs the record of the installation instruction of SCOMO server, judge that this software is that non-SCOMO mode unloads, then SCOMO client deletes <EReader> node whole nodes down.
The process flow diagram of the method for another the use software component management Object Management group software that Fig. 6 provides for the embodiment of the present invention.The present embodiment mainly carries out download management to software.As shown in Figure 6, specifically can comprise:
Step 61, obtain the description document of described software when software download.
This action can by SCOMO client executing.SCOMO client whether implementing monitoring current device can have the process of air transmission, if monitored, by obtaining the mode of the description document of transfer files, can obtain the information such as title, version being downloaded file,
Step 62, when described software is downloaded in non-SCOMO mode, according to described description document under the download node of described SCOMO, configure corresponding node for described software creation.
This action can by SCOMO client executing.SCOMO client is downloaded the information such as title, version of file according to obtaining, create and configure corresponding node under " Download " node.
After described software download completes, download management also can comprise:
Step 63, under the download node of described SCOMO, configure corresponding node for described software creation.
This action can by SCOMO client executing.SCOMO client is described software creation bag mark (PkgID) node under the distribution node of described SCOMO, for described establishment bag identification nodes is configured for the value identifying described software and download in non-SCOMO mode.For described software creation and after configuring corresponding node, the value of the establishment bag identification nodes of described software also can be reported described SCOMO server by SCOMO client.
For completing download but still uninstalled software, or have and uninstalled software on subscriber equipment, SCOMO client according to the information of software as file name or type etc. and existing information under the distribution node of SCOMO compare, if do not had, illustrate that this software is distributed in non-SCOMO mode, then under the distribution node of SCOMO, be described software creation and configure corresponding node.
For the mobile phone of an Andriod operating system.Suppose that user uses this mobile phone to receive a note with certain software download URL, user clicks this URL and downloads this software.The process that SCOMO client monitors to this mobile phone has air transmission to download, so obtain the description document of the software of this download, therefrom obtains the download URL of this software, filename, version number, descriptor, file type.SCOMO client performs the instruction record of SCOMO server by monitoring, judge that this download software is that non-SCOMO server issues, under " Download " node, then start the software creation node for this download, and by the information configuration that gets from description document in the value of " PkgURL ", " Name ", " Description ", " PkgType " node, for " PkgID " arrange special value as " UserPrivate " identifies non-SCOMO mode download.SCOMO server can equal " UserPrivate " " Download/<X>/PkgID " node by Query Value obtains the software downloaded in non-SCOMO mode that current phone is being downloaded.
After this software download success, SCOMO client is the software creation configuration node information successfully downloaded under " Inventory/Delivered " node, the value of " Name ", " Description ", " PkgType " node is carried out corresponding configuration, be that non-SCOMO mode is downloaded for " PkgID " arranges special value such as " UserPrivate " or sky to identify this software, and create "/Inventory/Delivered/<X>/Opera tions/Remove " node.SCOMO server can equal the "/Inventory/Delivered/<X>/PkgID " node of " UserPrivate " by Query Value, obtain the software that non-SCOMO mode that this mobile phone is being downloaded is downloaded.SCOMO server sends instructions under can also passing through "/Inventory/Delivered/<X>/Opera tions/Remove ", indicates SCOMO client to delete this software.
SCOMO client by the mode of the All Files on search subscriber equipment, can also obtain the software information on subscriber equipment.After SCOMO client obtains the software information of a certain software, by being compared by <name> and <PkgType> of existing software information under the file name in the software information of this software and type and " Inventory/Delivered " node, judge whether this software exists on management tree.If do not exist, then create under " Inventory/Delivered/ " and configure corresponding node to manage this software, SCOMO server can by inquiring about or delete these softwares to the query statement of SCOMO or delete instruction.
For the mobile phone of a Windows Mobile.This mobile phone is provided with SCOMO client equally, supports SCOMO agreement.In the present embodiment, SCOMO client, by searching for mobile phone storage equipment, searches the file before the software installation of the forms such as all CAB, INI, LIC, CERT to obtain the specifying information of executable file, registration (license) file or certificate file on this mobile phone.Wherein, register-file or certificate file also can be considered to the information of software.
After SCOMO client finds the file meeting the above-mentioned form enumerated, judge that the non-SCOMO mode of these files is distributed, be the corresponding nodes of these document creations under " Inventory/Delivered/ " node on SCOMO, and configuration node title, as " name ", " version ", " PkgType " etc., for " Inventory/Delivered/<X>/PkgID " arranges special value as " UserPrivate " or sky, identifying these files is that non-SCOMO mode is distributed.SCOMO server can obtain by the value of inquiring about " Inventory/Delivered/<X>/PkgID " node the software information that on subscriber equipment, all non-SCOMO modes are distributed; SCOMO server can pass through transmit operation instruction " Inventory/Delivered/<X>/Opera tions/Remove " and delete corresponding file.
The structural representation of a kind of software component management target customer end device that Fig. 7 provides for the embodiment of the present invention.This SCOMO client terminal device comprises: the first acquisition module 71, second acquisition module 72, creation module 73 and reporting module 74.First acquisition module 71 is for obtaining the software information on subscriber equipment.Second acquisition module 72 is for obtaining the information of the software that described subscriber equipment operates in non-SCOMO mode according to described software information.The software creation that creation module 73 operates for described non-SCOMO mode for the information of the software operated according to described non-SCOMO mode under the respective nodes of SCOMO also configures corresponding node.Reporting module 74 for by the information reporting of described node to SCOMO server.
Described first acquisition module can 71 can specifically for obtaining the software installation information on subscriber equipment; Described second acquisition module 72 can specifically for obtaining the information of the software that described subscriber equipment is installed in non-SCOMO mode according to described software installation information; Described creation module 73 can specifically for being described software creation according to the information of described software and configuring corresponding node under the deployment node of SCOMO.
Described first acquisition module 71 can specifically for obtaining the software download information on subscriber equipment in the process downloading software; Described second acquisition module 72 can specifically for obtaining the information of the software that described subscriber equipment is downloaded in non-SCOMO mode according to described software download information; Described creation module 73 can specifically for according to the information of described software under the download node of described SCOMO, configure corresponding node for described software creation.
Described first acquisition module 71 can have and the information of uninstalled software specifically for obtaining on subscriber equipment; Described second acquisition module 72 can specifically for the information of software of distributing in non-SCOMO mode according to described all existing and acquisition of informations of uninstalled software; Described creation module 73 can specifically for according to the information of described software under the distribution node of described SCOMO, configure corresponding node for described software creation.
Described reporting module 74 can specifically for by the positional information of management subtree in described SCOMO of described software, described software current state information, be used at least one identified in the information of the node that described software operates in non-SCOMO mode and send to described SCOMO server.
The software component management target customer end device that the embodiment of the present invention provides also can comprise: the 3rd acquisition module and knot removal module.3rd acquisition module is for obtaining the unloading information of described software; Knot removal module is used for when described software unloads in non-SCOMO mode, deletes the node for described software creation in described SCOMO according to described unloading information; Described reporting module is specifically for reporting described software unloaded to described SCOMO server.
The software component management target customer end device that the embodiment of the present invention provides also can comprise: command reception module, knot removal module.Query statement, delete instruction that command reception module sends for receiving described SCOMO server; The node that it is described software creation that knot removal module is used for according to described delete instruction deletion; Described reporting module can report the information of described node specifically for the query statement sent according to described SCOMO server.
The software component management target customer end device that the embodiment of the present invention provides also can comprise with at least one in lower module: Unload module, removing module.Unload module is for unloading described software; Removing module is for deleting described software physical file on a user device.
The structural representation of a kind of software component management object server that Fig. 8 provides for the embodiment of the present invention.This SCOMO server comprises: receiver module 81.Receiver module 81 is for receiving the information of the node using SCOMO client to report; Described node is described SCOMO client is software creation in SCOMO and the node of configuration; Described software is with the software that non-SCOMO mode operates on subscriber equipment.
The software component management object server that the embodiment of the present invention provides also can comprise: the first sending module.First sending module is for sending the query statement of the identifier comprised for identifying the software operated in non-SCOMO mode, and described query statement is used for the nodal information of the software operated in non-SCOMO mode according to described identifier query.
The software component management object server that the embodiment of the present invention provides also can comprise: the second sending module.Second sending module is for sending delete instruction, and described delete instruction is for deleting on described subscriber equipment with the software that non-SCOMO mode operates.
The information of the software that said method and device embodiment are operated in non-SCOMO mode by acquisition, and be that the software operated in non-SCOMO mode creates respective nodes under SCOMO according to the information obtained, corresponding nodal information is reported as SCOMO server, solves existing SCOMO mode and cannot be installed to the problem of the software on terminal device by non-SCOMO mode by leading subscriber.
One of ordinary skill in the art will appreciate that: all or part of step realizing said method embodiment can have been come by the hardware that programmed instruction is relevant, aforesaid program can be stored in a computer read/write memory medium, this program, when performing, performs the step comprising said method embodiment; And aforesaid storage medium comprises: ROM, RAM, magnetic disc or CD etc. various can be program code stored medium.
Last it is noted that above embodiment is only in order to illustrate technical scheme of the present invention, be not intended to limit; Although with reference to previous embodiment to invention has been detailed description, those of ordinary skill in the art is to be understood that: it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein portion of techniques feature; And these amendments or replacement, do not make the essence of appropriate technical solution depart from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (17)
1. use a method for software component management Object Management group software, it is characterized in that, comprising:
Obtain the software information on subscriber equipment, described software information comprise following in arbitrary: software installation information, software download information, the existing and information of uninstalled software;
The information of the software that described subscriber equipment operates in non-software Component Management Object mode is obtained according to described software information;
The software creation that the information of the software operated according to described non-software Component Management Object mode operates for described non-software Component Management Object mode under the respective nodes of software component management object also configures corresponding node;
By the software creation operated for described non-software Component Management Object mode and the information reporting configuring corresponding node to software component management object server;
By the software creation operated for described non-software Component Management Object mode and the information reporting configuring corresponding node comprise to software component management object server:
By the positional information of the management subtree of described software in described software component management object, described software current state information or be used at least one identified in the information of the node that described software operates in non-software Component Management Object mode and send to described software component management object server.
2. the method for use software component management Object Management group software according to claim 1, is characterized in that, the information of the software that described non-software Component Management Object mode operates at least comprise following any one:
The descriptor of dbase, software version, software.
3. the method for use software component management Object Management group software according to claim 1, is characterized in that,
The software information obtained on subscriber equipment comprises: obtain the software installation information on subscriber equipment;
Obtain the information of the software that described subscriber equipment operates in non-software Component Management Object mode according to described software information, comprising: the information obtaining the software that described subscriber equipment is installed in non-software Component Management Object mode according to described software installation information;
The software creation operated for described non-software Component Management Object mode under the respective nodes of software component management object according to the information of described software also configures corresponding node, comprising: the software creation operated for described non-software Component Management Object mode under the deployment node of software component management object according to the information of described software also configures corresponding node;
The software creation operated for described non-software Component Management Object mode under the deployment node of software component management object also configures corresponding node, comprising:
The software creation bag identification reference node operated for described non-software Component Management Object mode under the deployment node of software component management object;
For the value that described bag identification reference Joint Enterprise is installed with non-software Component Management Object for the software identifying described non-software Component Management Object mode and operate; Or the software creation operated for described non-software Component Management Object mode under the deployment node of software component management object also configures corresponding node, comprising:
Create under the deployment node of software component management object and configure new node; Described new node is the software operated for identifying described non-software Component Management Object mode is the node installed with non-software Component Management Object;
Or the software information obtained on subscriber equipment comprises:
The software download information on subscriber equipment is obtained in the process downloading software;
Obtain the information of the software that described subscriber equipment operates in non-software Component Management Object mode according to described software information, comprising: the information obtaining the software that described subscriber equipment is downloaded in non-software Component Management Object mode according to described software download information;
Information according to described software is described software creation and configures corresponding node under the respective nodes of software component management object, comprise: according to the information of described software under the download node of described software component management object, the software creation operated for described non-software Component Management Object mode also configures corresponding node;
The software creation operated for described non-software Component Management Object mode also configures corresponding node and comprises:
For the software creation bag identification nodes that described non-software Component Management Object mode operates;
For described bag identification nodes is configured for the value that the software that operates of the described non-software Component Management Object mode of mark downloads in non-software Component Management Object mode; Or the software creation operated for described non-software Component Management Object mode also configures corresponding node, comprising:
Create and configure new node, described new node is the node downloaded in non-software Component Management Object mode for identifying described software;
Or the software information obtained on subscriber equipment comprises:
Obtain on subscriber equipment and have and the information of uninstalled software;
Obtain the information of the software that described subscriber equipment operates in non-software Component Management Object mode according to described software information, comprising: according to the information of the software that all described existing and acquisition of informations of uninstalled software are distributed in non-software Component Management Object mode;
Information according to described software is described software creation and configures corresponding node under the respective nodes of software component management object, comprise: according to the information of described software under the distribution node of described software component management object, the software creation operated for described non-software Component Management Object mode also configures corresponding node;
The software creation operated for described non-software Component Management Object mode also configures corresponding node and comprises:
For the software creation bag identification nodes that described non-software Component Management Object mode operates;
For described bag identification nodes is configured for the value that the software that operates of the described non-software Component Management Object mode of mark distributes in non-software Component Management Object mode; Or the software creation operated for described non-software Component Management Object mode also configures corresponding node, comprising:
Create and configure new node, described new node is the node that the software operated for identifying described non-software Component Management Object mode is distributed in non-software Component Management Object mode.
4. the method for use software component management Object Management group software according to claim 1, it is characterized in that, by the software creation operated for described non-software Component Management Object mode and the information reporting configuring corresponding node comprise to software component management object server:
The information of described node is reported according to the query statement of described software component management object server transmission.
5. the method for the use software component management Object Management group software according to any one of claim 1-3, is characterized in that, also comprise:
Obtain the unloading information of the software that described non-software Component Management Object mode operates;
When described software unloads in non-software Component Management Object mode, delete the node for described software creation in described software component management object according to described unloading information;
Report described software unloaded to described software component management object server.
6. the method for the use software component management Object Management group software according to any one of claim 1-3, is characterized in that, also comprise:
Receive the delete instruction that described software component management object server sends;
The node of the software creation operated for described non-software Component Management Object mode is deleted according to described delete instruction.
7. the method for use software component management Object Management group software according to claim 6, is characterized in that, also comprise: unload the software that described non-software Component Management Object mode operates; Or,
Delete the physical file of software on described subscriber equipment that described non-software Component Management Object mode operates.
8. use a method for software component management Object Management group software, it is characterized in that, comprising:
Receive the information of the node using software component management object client to report; Described node is described software component management object client is software creation in software component management object and the node of configuration; Described software is with the software that non-software Component Management Object mode operates on subscriber equipment.
9. the method for use software component management Object Management group software according to claim 8, is characterized in that, also comprise:
Send the query statement of the identifier comprised for identifying the software operated in non-software Component Management Object mode, described query statement is used for the nodal information of the software operated in non-software Component Management Object mode according to described identifier query.
10. the method for use software component management Object Management group software according to claim 9, is characterized in that, also comprise:
Send delete instruction, for deleting on described subscriber equipment with the software that non-software Component Management Object mode operates.
11. 1 kinds of client terminal devices using software component management Object Management group software, is characterized in that, comprising:
First acquisition module, for obtaining the software information on subscriber equipment, described software information comprise following in arbitrary: software installation information, software download information, the existing and information of uninstalled software;
Second acquisition module, for obtaining the information of the software that described subscriber equipment operates in non-software Component Management Object mode according to described software information;
Creation module, the software creation that the information for the software operated according to described non-software Component Management Object mode operates for described non-software Component Management Object mode under the respective nodes of software component management object also configures corresponding node;
Reporting module, for by the software creation operated for described non-software Component Management Object mode and the information reporting configuring corresponding node to software component management object server;
Described reporting module specifically for by the positional information of the management subtree of described software in described software component management object, described software current state information, be used at least one identified in the information of the node that described software operates in non-software Component Management Object mode and send to described software component management object server.
The client terminal device of 12. use software component management Object Management group softwares according to claim 11, is characterized in that, described first acquisition module is specifically for obtaining the software installation information on subscriber equipment;
Described second acquisition module is specifically for obtaining the information of the software that described subscriber equipment is installed in non-software Component Management Object mode according to described software installation information;
Described creation module specifically for being described software creation according to the information of described software and configuring corresponding node under the deployment node of software component management object;
Or described first acquisition module specifically for obtaining the software download information on subscriber equipment in the process downloading software;
Described second acquisition module is specifically for obtaining the information of the software that described subscriber equipment is downloaded in non-software Component Management Object mode according to described software download information;
Described creation module specifically for according to the information of described software under the download node of described software component management object, configure corresponding node for described software creation;
Or described first acquisition module has and the information of uninstalled software specifically for obtaining on subscriber equipment;
The information of software of described second acquisition module specifically for distributing in non-software Component Management Object mode according to all described existing and acquisition of informations of uninstalled software;
Described creation module specifically for according to the information of described software under the distribution node of described software component management object, configure corresponding node for described software creation.
The client terminal device of 13. use software component management Object Management group softwares according to claim 11 or 12, is characterized in that, also comprise:
3rd acquisition module, for obtaining the unloading information of described software;
Knot removal module, for when described software unloads in non-software Component Management Object mode, deletes the node for described software creation in described software component management object according to described unloading information;
Described reporting module is specifically for reporting described software unloaded to described software component management object server.
The client terminal device of 14. use software component management Object Management group softwares according to claim 11 or 12, is characterized in that, also comprise:
Command reception module, for receiving query statement, delete instruction that described software component management object server sends;
Knot removal module, for deleting the node for described software creation according to described delete instruction;
Described reporting module reports the information of described node specifically for the query statement sent according to described software component management object server.
The client terminal device of 15. use software component management Object Management group softwares according to claim 14, is characterized in that, also comprise with at least one in lower module:
Unload module, for unloading described software;
Removing module, for deleting the physical file of described software on described subscriber equipment.
16. 1 kinds of servers using software component management Object Management group software, is characterized in that, comprising:
Receiver module, for receiving the information of the node using software component management object client to report; Described node is described software component management object client is software creation in software component management object and the node of configuration; Described software is with the software that non-software Component Management Object mode operates on subscriber equipment.
The server of 17. use software component management Object Management group softwares according to claim 16, is characterized in that, also at least comprise with any one in lower module:
First sending module, for sending the query statement of the identifier comprised for identifying the software operated in non-software Component Management Object mode, described query statement is used for the nodal information of the software operated in non-software Component Management Object mode according to described identifier query;
Second sending module, for sending delete instruction, described delete instruction is for deleting on described subscriber equipment with the software that non-software Component Management Object mode operates.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910168281.0A CN101996074B (en) | 2009-08-20 | 2009-08-20 | Method and device for managing software by using software component management object |
| PCT/CN2010/075599 WO2011020402A1 (en) | 2009-08-20 | 2010-07-30 | Method and device for managing software using software component management object |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910168281.0A CN101996074B (en) | 2009-08-20 | 2009-08-20 | Method and device for managing software by using software component management object |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101996074A CN101996074A (en) | 2011-03-30 |
| CN101996074B true CN101996074B (en) | 2014-12-24 |
Family
ID=43606632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910168281.0A Active CN101996074B (en) | 2009-08-20 | 2009-08-20 | Method and device for managing software by using software component management object |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101996074B (en) |
| WO (1) | WO2011020402A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103248649B (en) * | 2012-02-09 | 2016-08-24 | 宇龙计算机通信科技(深圳)有限公司 | Sort management method, equipment and the system of application |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101325509A (en) * | 2007-06-11 | 2008-12-17 | 华为技术有限公司 | Method, system and apparatus for installing software component |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101292979B1 (en) * | 2006-08-17 | 2013-08-02 | 삼성전자주식회사 | Method for managing software in terminal using device management server |
| KR101495341B1 (en) * | 2007-06-01 | 2015-02-25 | 삼성전자주식회사 | Method and System for assigning IDs to software compoents |
-
2009
- 2009-08-20 CN CN200910168281.0A patent/CN101996074B/en active Active
-
2010
- 2010-07-30 WO PCT/CN2010/075599 patent/WO2011020402A1/en active Application Filing
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101325509A (en) * | 2007-06-11 | 2008-12-17 | 华为技术有限公司 | Method, system and apparatus for installing software component |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2011020402A1 (en) | 2011-02-24 |
| CN101996074A (en) | 2011-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3002930B1 (en) | Method, system, terminal and device management server for installing software components | |
| JP5144659B2 (en) | Methods, systems, and terminals for maintaining capability management objects and managing capabilities | |
| CN102262544B (en) | The method and apparatus of software upgrading | |
| US9696977B2 (en) | Method and system for allocating ID of software component | |
| JP5954635B2 (en) | Method, system, terminal, and device management server for installing software components | |
| CN102487522B (en) | Management method and gateway device of terminal devices | |
| CN110865842A (en) | OTA (over the air) upgrading method and device | |
| CN109240726B (en) | Software updating method and system | |
| CN102215118B (en) | Method, device and system for realizing device management services | |
| CN101996074B (en) | Method and device for managing software by using software component management object | |
| CN101309490B (en) | Support system, method and management platform implementing terminal management | |
| CN102571390B (en) | Equipment management method, equipment and system | |
| CN113434171A (en) | Resource package updating method and device, storage medium and electronic device | |
| CN112748937A (en) | Method and device for updating eUICC operating system | |
| US20080244558A1 (en) | Content downloading in a radio communication network | |
| CN110572303B (en) | Method and device for automatically discovering nodes | |
| JP2001125791A (en) | Network install system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee after: Huawei terminal (Shenzhen) Co.,Ltd. Address before: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee before: HUAWEI DEVICE Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20181219 Address after: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee after: HUAWEI DEVICE Co.,Ltd. Address before: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee before: Huawei terminal (Shenzhen) Co.,Ltd. |