JP5469834B2 - Terminal management system - Google Patents

Description

  The present invention relates to a data saving device that saves data stored in a terminal device, a data restoring device that restores data on the terminal device, and a terminal management system that remotely manages data stored in the terminal device.

  In recent years, high performance and high functionality of mobile terminals such as mobile phones and PDAs have been advanced. Along with this, the importance of data assets stored in portable terminals is increasing. For example, in a business system using a mobile terminal, data with extremely high importance and confidentiality such as customer personal information is stored in the mobile terminal. On the other hand, there is a risk that data stored in the mobile terminal leaks to a third party who illegally obtained the mobile terminal due to loss or theft of the mobile terminal.

  From such a background, it is required to remotely manage data stored in a mobile terminal in real time. For example, a technique for remotely managing a portable terminal via a network (for example, Patent Document 1) and a technique for remotely managing a portable terminal by using a remote management command using an SMS (Short Message Service) message are proposed (for example, Patent Document 2). Has been.

  In addition, OMA (Open Mobile Alliance), which is a standard organization for mobile related technologies, has proposed a protocol for remotely managing a mobile terminal between a terminal management client provided in the mobile terminal and a terminal management server ( For example, Non-Patent Document 1).

  This protocol has “Setup Phase” and “Management Phase”. “Setup Phase” is a stage for initializing a management session between the terminal management server and the terminal management client. “Management Phase” is a stage in which the terminal management server manages the mobile terminal.

  In “Setup Phase”, the terminal management server transmits an initial message for starting the terminal management client to the mobile terminal. Subsequently, the terminal management client transmits terminal information (Deinfo) including a terminal identifier (IMEI) and the like to the terminal management server.

  In “Management Phase”, the terminal management server transmits a management message for managing the mobile terminal to the mobile terminal on the management session established in “Setup Phase”. On the other hand, the mobile terminal transmits a management response message to the terminal management server in response to the management message.

  Here, in the generation of the management message, the terminal management server resolves the data structure of the management object (MO) according to the terminal identifier included in the terminal information received from the mobile terminal. The management object is information obtained by abstracting management processing for managing data stored in the mobile terminal.

  By the way, as a technique for transferring data (for example, telephone directory data and schedule data) stored in a mobile terminal between mobile terminals, a data transfer function possessed by OBEX or FeliCaOS is known.

  Here, in the terminal management system proposed by the OMA described above, a case is considered in which data is transferred from one mobile terminal to another mobile terminal on the assumption that one mobile terminal is remotely managed. In such a case, if only data is transferred from one mobile terminal to another mobile terminal, the data transferred to the other mobile terminal is not managed.

In the OMA described above, it is proposed that data transferred to another mobile terminal is not excluded from the management target by copying the management object to a medium such as an IC card provided in the other mobile terminal. (For example, Non-Patent Document 2).
US Pat. No. 6,970,917 International Publication No. 03/055248 Pamphlet OMA Device Management Protocol OMA-TS-DM-Protocol-V1_2-200209-A, [online], Internet <URL: http://www.openmobilealliance.org/Technical/release_program/docs/copyrightclick.aspx?pck=DM&file= V1_2-20070209-A / OMA-TS-DM_Protocol-V1_2-20070209-A.pdf> OMA Device Management SmartCard OMA-RD-DM_SC-V1_0-20070904-C, [online], Internet <URL: http://www.openmobilealliance.org/Technical/release_program/docs/CopyrightClick.aspx?pck=RD&file=OMA- RD-DM_SC-V1_0-20070904-C.pdf ">

  As described above, the management object is information obtained by abstracting management processing for managing data stored in the mobile terminal. Therefore, in order to realize the management process on the mobile terminal, an application that operates on the mobile terminal that connects the abstracted management process and the actual data management is required. For example, in the case where the phone book data is a management target, when a management process for adding, editing, or deleting the phone book data is requested, an API for accessing the phone book database held by the mobile terminal is used. Thus, a telephone directory management application for adding, editing and deleting data is required. Application implementation depends on the software operating environment of the mobile terminal.

  Therefore, even if an application that operates on one mobile terminal is transferred to another mobile terminal, the application does not always operate on another mobile terminal. On the other hand, this is an application for realizing management processing by a management object transferred from one mobile terminal to another mobile terminal, and the other mobile terminal transmits an application operating on the other mobile terminal via the network. It is also possible to acquire it.

  However, an application acquired by another mobile terminal via a network does not necessarily have all of the functions of the application operating on the one mobile terminal. In such a case, remote management of data transferred from one mobile terminal to another mobile terminal becomes insufficient.

  Therefore, the present invention has been made to solve the above-described problem, and even when data is transferred from one mobile terminal to another mobile terminal, the data transferred to the other mobile terminal can be transferred. It is an object of the present invention to provide a data saving device, a data restoration device, and a terminal management system that can be sufficiently remotely managed.

  A data evacuation apparatus according to a first feature evacuates data stored in the evacuation terminal apparatus to an evacuation storage as evacuation target data from an evacuation terminal apparatus that stores data remotely managed by a terminal management system. The data saving apparatus includes a data saving management unit that receives a data saving request for saving the saving target data, and an object management unit that manages a saving data management object for remotely managing the saving target data. The data save management unit notifies the object management unit of an object save request including information for specifying the save target data. In response to the object save request, the object management unit returns information specifying the save data management object to the data save management unit. The data save management unit stores information for specifying the save data management object and information for specifying the model of the save terminal device in the save storage together with the save target data.

  In the first feature, the saved data management object includes a plurality of partial objects. The data evacuation management unit stores, in the evacuation storage, information specifying an important partial object that is a partial object having a higher importance in remote management than the other partial objects among the plurality of partial objects.

  The data restoration device according to the second feature acquires restoration target data to be remotely managed by the terminal management system from the restoration storage, and restores the restoration target data in a state of being remotely managed on the restoration terminal device. The data restoration device receives a data restoration request for requesting restoration of the restoration target data, and remotely manages the data restoration management unit that restores the restoration target data to the restoration terminal device, and the terminal data stored in the restoration terminal device And an object management unit that manages terminal data management objects that are external interfaces. In response to the data restoration request, the data restoration management unit reads, from the restoration storage, information specifying a restoration data management object that is an external interface for remotely managing the restoration target data. The data restoration management unit notifies the object management unit of an object restoration request including information specifying the restoration data management object. The object management unit extracts information specifying the restoration data management object from the object restoration request, and performs the same management process as the management process that can be executed by the terminal management system using the restoration data management object. The data restoration management unit is notified of a confirmation result indicating whether or not execution is possible using the data management object. The data restoration management unit restricts restoration of the restoration target data when the confirmation result is negative.

  In the second feature, the object management unit checks whether the terminal data management object constructed based on the same name as the restored data management object or the same structure definition as the restored data management object is managed. Include in results.

  In the second feature, the restoration data management object is constituted by one or more restoration data management partial objects. The terminal data management object is composed of one or more terminal data management partial objects. The data restoration device further includes a conversion unit. The conversion unit extracts information for specifying the restored data management partial object based on information for specifying the restored data management object or information for specifying the restored data management partial object, and is specified by the extracted information. Information for identifying the restored data management partial object is included in the information for identifying the terminal data management partial object that executes the same management processing that can be executed by the terminal management system using the restored data management partial object. Convert.

  In the second feature, the object management unit outputs a conversion request including the restored data management partial object that could not be converted by the conversion unit to an external device. The object management unit updates the terminal data management object with the restored data management partial object converted or added by the external device.

  2nd characteristic WHEREIN: The said object management part performs the management process same as the management process which the said terminal management system can perform using the said restoration data management partial object which could not be converted by the said conversion part in the said restoration terminal device The partial object to be acquired is acquired from the external device, and the partial object acquired from the external device is newly added to the terminal data management object. The data restoration apparatus further includes an acquisition unit that acquires an application that executes the same management process as the management process that can be executed by the terminal management system, using the partial object acquired from the external apparatus.

  In the second feature, the object management unit outputs a conversion request including the restored data management object or the restored data management partial object to an external device. The object management unit includes information for specifying the restored data management partial object converted or added by the external device, or information for specifying the restored data management partial object not converted or added by the external device The conversion result is obtained from the external device. The object management unit, based on the conversion result, information indicating a portion that cannot be executed by the terminal data management object in the same management processing that can be executed by the terminal management system using the restored data management object Is notified to the data restoration management unit as the confirmation result.

  In the second feature, the data restoration device includes an acquisition unit that acquires an application that performs remote management using the restoration data management object, and an operation check of the restoration data management object on the application acquired by the acquisition unit And an operation confirmation unit for performing. The object management unit reads the restoration data management object from the restoration storage when the same terminal data management object as the restoration data management object is not managed. The object management unit notifies the acquisition unit of an application acquisition request including information specifying the restored data management object. When the application is acquired in response to the application acquisition request, the object management unit notifies the operation confirmation unit of an operation confirmation request that requests operation confirmation of the restored data management object. The data restoration management unit restricts restoration of the restoration target data when the operation confirmation of the restoration data management object fails.

  In the second feature, in response to the data restoration request, the data restoration management unit reads information specifying the model of the evacuation terminal device stored in the restoration storage from the restoration storage. The data restoration management unit notifies the object management unit of the object restoration request including information specifying the model of the evacuation terminal device. The object management unit omits the operation check of the restored data management object when the model of the restoration terminal device is the same as the model of the evacuation terminal device.

  In the second feature, the restored data management object is composed of a plurality of partial objects. In response to the data restoration request, the data restoration management unit restores information identifying an important partial object that is a partial object having a higher importance in remote management than the other partial objects from among the plurality of partial objects. Read from storage. The object management unit notifies the operation confirmation unit of the operation confirmation request including information specifying the important partial object. The operation check unit only checks the operation of the important partial object.

  A terminal management system according to a third feature remotely manages migration data that is migrated from an evacuation terminal device to a restoration terminal device. The terminal management system stores the data stored in the evacuation terminal device as the migration data in the migration storage, and stores information specifying the migration data management object for remotely managing the migration data in the migration storage A evacuation device, and a data restoration device that acquires the migration data from the migration storage and restores the migration data on the restoration terminal device. The data restoration device restricts restoration of the migration data when the same management object as the migration data management object is not managed by the device itself.

  In the third feature, the data saving apparatus stores the migration data management object in a migration storage. The data restoration device reads the migration data management object from the migration storage when the same management object as the migration data management object is not managed by the device itself. The data restoration device acquires an application for performing remote management using the migration data management object. The data restoration apparatus confirms the operation of the migration data management object on the application. The data restoration device restricts restoration of the migration data when the operation check of the migration data management object fails.

  In the third feature, the terminal management system further includes a terminal management server that remotely manages terminal data stored in the evacuation terminal device or the restoration terminal device. The data restoration device acquires a command group for operating and editing the migration data management object from the terminal management server. The data restoration device confirms the operation of the migration data management object on the application according to a group of instructions acquired from the terminal management server.

  According to the present invention, even when data is transferred from one mobile terminal to another mobile terminal, a data evacuation device that can sufficiently manage the data transferred to another mobile terminal, A data restoration device and a terminal management system can be provided.

  Hereinafter, a terminal management system according to an embodiment of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

  However, it should be noted that the drawings are schematic and ratios of dimensions and the like are different from actual ones. Therefore, specific dimensions and the like should be determined in consideration of the following description. Moreover, it is a matter of course that portions having different dimensional relationships and ratios are included between the drawings.

[First Embodiment]
(Configuration of terminal management system)
Hereinafter, the configuration of the terminal management system according to the first embodiment will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration of a terminal management system 1 according to the first embodiment.

  As illustrated in FIG. 1, the terminal management system 1 includes an evacuation terminal device 10, a restoration terminal device 20, a terminal management server 100, an application distribution server 200, and a network 300.

  The evacuation terminal device 10 is a device that stores data remotely managed by the terminal management system 1. The evacuation terminal device 10 is a mobile terminal such as a PDA or a mobile phone, and has a wireless communication function. However, the evacuation terminal device 10 may be a terminal such as a PC having a wired communication function. Further, the evacuation terminal apparatus 10 includes a data evacuation apparatus 10a that evacuates data stored in the evacuation terminal apparatus 10 to the evacuation storage as evacuation target data.

  The restoration terminal device 20 is a device that stores data to be remotely managed by the terminal management system 1. The restoration terminal device 20 is a mobile terminal such as a PDA or a mobile phone, and has a wireless communication function. However, the restoration terminal device 20 may be a terminal such as a PC having a wired communication function. The restoration terminal device 20 includes a data restoration device 20a that restores the data stored in the restoration storage as restoration target data on the restoration terminal device 20.

  The terminal management server 100 is a server that remotely manages terminals such as the evacuation terminal device 10 and the restoration terminal device 20. The terminal management server 100 has a function of remotely managing a terminal by a method compliant with OMA-DM (Device Management) standardized by, for example, OMA (Open Mobile Alliance).

  The application distribution server 200 distributes an application that performs remote management of terminal data stored in a terminal such as the evacuation terminal apparatus 10 or the restoration terminal apparatus 20. Specifically, the application is activated by remote management using a management object (MO) for managing terminal data, and manages terminal data in accordance with a remote management command. Here, it should be noted that the management object is information (for example, Management Object used in OMA-DM) that abstracts terminal data management processing. The application distribution server 200 distributes the application in accordance with a request from the restoration terminal device 20.

  The network 300 is a network such as a wireless LAN, a wired LAN, or a mobile communication network. The network 300 may be any network as long as it connects the evacuation terminal device 10, the restoration terminal device 20, the terminal management server 100, and the application distribution server 200.

  In the first embodiment, a case is considered in which terminal data is transferred from the evacuation terminal device 10 to the restoration terminal device 20. In the data saving device 10a provided in the saving terminal device 10, the terminal data is handled as saving target data to be saved in the saving storage. On the other hand, in the data restoration device 20a provided in the restoration terminal device 20, the terminal data is handled as restoration target data to be restored from the restoration storage. The save target data and the restore target data are migration data transferred from the save terminal device 10 to the restore terminal device 20.

(Configuration of data backup device)
Hereinafter, the configuration of the data saving apparatus according to the first embodiment will be described with reference to the drawings. FIG. 2 is a diagram illustrating a configuration of the data saving apparatus 10a according to the first embodiment.

  As illustrated in FIG. 2, the data saving apparatus 10 a includes an application processing unit 11, a storage unit 12, a saving storage 13, a data saving management unit 14, and an object management unit 15.

  The application processing unit 11 processes an application that performs remote management using a management object.

  The storage unit 12 is an internal storage medium (for example, a flash memory) provided in the data saving device 10a, and stores terminal data that is remotely managed by the terminal management system 1.

  The save storage 13 is a storage medium that stores terminal data stored in the storage unit 12 as save target data. The save storage 13 is an external storage medium that is detachably provided in the data save device 10a, such as an SD card or a SIM (Subscriber Identity Module) card. The save storage 13 may be a network storage provided on the network 300 instead of an external storage medium.

  In the case where the evacuation terminal apparatus 10 and the restoration terminal apparatus 20 are directly connected by wire or wirelessly, the evacuation storage 13 may be a storage provided in the restoration terminal apparatus 20.

  The data saving management unit 14 receives a data saving request for requesting saving of data to be saved. In response to the data save request, the data save management unit 14 notifies the object save unit 15 of an object save request including information specifying the save target data. Here, the information for specifying the save target data is information that can uniquely specify the type of the save target data, and is, for example, a data type name such as “phone book”, “call origination / incoming history”, and “schedule”. .

  Subsequently, the data save management unit 14 acquires information specifying the management object (saved data management object) corresponding to the save target data from the object management unit 15. The data save management unit 14 stores information for specifying the save data management object in the save storage 13 together with the save target data.

  The object management unit 15 manages the management object 15a for remotely managing the terminal data stored in the storage unit 12 in association with the terminal data. It should be noted that the management object 15a is information obtained by abstracting terminal data management processing as described above. For example, the management object 15a is a management object used in OMA-DM.

  In response to the object save request, the object management unit 15 returns information specifying the management object (saved data management object) corresponding to the save target data to the data save management unit 14. The information for specifying the saved data management object may be the saved data management object itself or information for identifying the saved data management object. Here, the information for identifying the saved data management object is information that can uniquely identify the saved data management object. For example, if the saved data management object has an XML title, the value of the XML signature, the saved data management object, The name of the root node of the data management object.

  Remote management using a management object standardized by OMA-DM requires implementation of an application that connects management processing abstracted by the management object and actual data management. In the implementation of this application, it is desirable that the data structure of the management object and the API of the application are related. In this desirable form, the identity of the managed objects need only match at the data structure level.

  Unlike other signature methods, XML Signature can generate a signature for the data structure and partial information of XML. The XML Signature can determine whether or not alteration on the communication path has been performed on the data structure and the partial information. Utilizing this characteristic, by using XML Signature, the identity of the migration-source management object and the migration-destination management object is not only a complete match including the value, but also only the data structure that does not include the value. A match can be determined. If the data structures match, the affinity with the application related to the managed object can be kept high. Therefore, it is possible to migrate the management object and data to the migration destination portable terminal while maintaining the management process that could be performed by the migration source management object.

(Configuration of data restoration device)
Hereinafter, the configuration of the data restoration device according to the first embodiment will be described with reference to the drawings. FIG. 3 is a diagram illustrating a configuration of the data restoration device 20a according to the first embodiment.

  As shown in FIG. 3, the data restoration device 20a includes an application processing unit 21, a storage unit 22, a restoration storage 23, a data restoration management unit 24, an object management unit 25, an application acquisition unit 26, and an operation check. Part 27.

  The application processing unit 21 processes an application that performs remote management using a management object.

  The storage unit 22 is an internal storage medium (for example, a flash memory) provided in the data restoration device 20a, and stores terminal data that is remotely managed by the terminal management system 1.

  The restoration storage 23 is a storage medium that stores data to be remotely managed by the terminal management system 1 as restoration target data. The restoration storage 23 is an external storage medium that is detachably provided in the data restoration device 20a, such as an SD card or a SIM card. The restoration storage 23 may be a network storage provided on the network 300 instead of an external storage medium.

  In the case where the evacuation terminal device 10 and the restoration terminal device 20 are directly connected by wire or wireless, the restoration storage 23 may be a storage provided in the evacuation terminal device 10.

  Here, it should be noted that the restoration storage 23 is the same storage medium (migration storage) as the save storage 13 described above. Therefore, the restoration storage 23 stores restoration target data (that is, save target data). The restoration storage 23 stores information for specifying a restoration data management object (that is, a saving data management object) for remotely managing restoration target data (that is, saving target data).

  The restoration target data and the saving target data are referred to as migration data as necessary. The restored data management object and the saved data management object are referred to as a migration data management object as necessary.

  The data restoration management unit 24 receives a data restoration request for requesting restoration of restoration target data. In response to the data restoration request, the data restoration management unit 24 reads, from the restoration storage 23, information specifying a restoration data management object for remotely managing restoration target data. Subsequently, the data restoration management unit 24 notifies the object management unit 25 of an object restoration request including information for specifying the restoration data management object. Here, the information for identifying the restoration data management object is information that can uniquely identify the restoration data management object. For example, if the restoration data management object is XML, the value of the XML signature, the restoration data management object, The name of the root node of the data management object.

  The data restoration management unit 24 acquires a confirmation result indicating whether or not the same management object 25 a as the restoration data management object is managed from the object management unit 25. The data restoration management unit 24 permits the restoration of the restoration target data when the same management object 25a as the restoration data management object is managed.

  On the other hand, if the same management object 25a as the restoration data management object is not managed, the data restoration management unit 24, except when the operation confirmation of the restoration data management object stored in the restoration storage 23 is successful, Limit the restoration of data to be restored. The data restoration management unit 24 permits restoration of restoration target data when the operation confirmation of the restoration data management object stored in the restoration storage 23 is successful.

  Here, the restriction on the restoration of the restoration target data is a concept including not restoring the restoration target data or invalidating (removing or overwriting with “0”) the restored restoration target data (restoration data). It should be noted that there are.

  The object management unit 25 manages a management object 25a (terminal data management object) for remotely managing terminal data stored in the storage unit 22 in association with terminal data. It should be noted that the management object 25a is information obtained by abstracting terminal data management processing as described above. The management object 25a is, for example, a Management Object used in OMA-DM.

  In response to the object restoration request, the object management unit 25 checks whether or not the same management object 25a (terminal data management object) as the restoration data management object is managed. The object management unit 25 notifies the data restoration management unit 24 of a confirmation result indicating whether or not the same management object 25a as the restoration data management object is managed.

  Here, as a method for confirming whether or not the same object as the restoration data management object is included in the management object 25a, the following method can be considered using the information for specifying the restoration data management object described above. For example, when the information specifying the restored data management object is XML Signature, a method may be considered in which the identity is determined by taking the XML Signature of the partial object of the management object 25a and comparing the two. For example, if the information specifying the restoration data management object is the name of the root node of the restoration data management object, the management object 25a is queried with the name, and the name of the root node of the restoration data management object exists. The method of confirming whether it is possible can be considered. In general, the latter method cannot guarantee the identity with the restored data management object. However, for example, when the data structure of the restored data management object is standardized, the identity can be guaranteed. An example of such a data structure is FUMO (Firmware Update Management Object) standardized by OMA-DM.

  If the same management object 25 a as the restored data management object is not managed, the object management unit 25 reads the restored data management object from the restoration storage 23. The object management unit 25 notifies the application acquisition unit 26 of an application acquisition request including information for specifying the restored data management object. Subsequently, when the application is acquired in response to the application acquisition request, the object management unit 25 notifies the operation confirmation unit 27 of an operation confirmation request for requesting operation confirmation of the restored data management object.

  The application acquisition unit 26 acquires, from the application distribution server 200, an application that performs remote management using the restored data management object. Specifically, the application acquisition unit 26 transmits an application distribution request associated with the restored data management object to the application distribution server 200. The application distribution server 200 distributes the application associated with the restored data management object in response to the application distribution request.

  The operation confirmation unit 27 confirms the operation of the restored data management object on the application acquired by the application acquisition unit 26. The operation confirmation unit 27 notifies the data restoration management unit 24 of the operation confirmation result of the restored data management object. The operation confirmation unit 27 may notify the operation confirmation result indirectly to the data restoration management unit 24 via the object management unit 25, and the operation confirmation unit 27 operates directly without using the object management unit 25. The confirmation result may be notified to the data restoration management unit 24.

  Hereinafter, the operation confirmation of the restored data management object will be specifically described.

  The operation confirmation unit 27 performs management processing of restoration target data on the application acquired by the application acquisition unit 26 in accordance with a command group for operating and editing each node constituting the restoration data management object. The operation confirmation unit 27 determines whether or not a processing violation occurs in the management process of the restoration target data. The operation confirmation unit 27 determines that the operation confirmation of the restored data management object has succeeded when no processing violation occurs. On the other hand, when a processing violation occurs, the operation check unit 27 determines that the operation check of the restored data management object has failed.

  Note that the command group for operating and editing each node constituting the restored data management object may be generated by the operation check unit 27 or acquired from the terminal management server 100.

  First, a case where the operation check unit 27 generates a command group will be described. For example, taking the technology defined by OMA as an example, the restored data management object has a tree structure composed of a plurality of nodes. Therefore, unless the operation editing of the upper node is normally performed, the operation editing of the node (lower node) lower than the upper node is not performed. For example, the operation check unit 27 searches for nodes with depth priority, and executes accessible “syncML commands” in order from the upper node. The accessible “syncML command” is set as “Access Type” which is one of the properties set in each node.

  Next, a case where an instruction group is acquired from the terminal management server 100 will be described. In such a case, the operation check unit 27 needs to notify the terminal management server 100 of information specifying the restored data management object.

  For example, taking the technology defined by OMA as an example, the operation confirmation unit 27 is realized by an OMA-DM client and transmits a management request message to the terminal management server 100. For example, as a management request message, DM protocol Pkg # 1 standardized by OMA-DMWG is used. Pkg # 1 is defined by OMA so as to describe “DevInfo” including “Ext” node. Therefore, the operation confirmation unit 27 includes information for specifying the restoration data management object under the “Ext” node, and includes the information in Pkg # 1. Here, the information for specifying the restored data management object included under the “Ext” node is information that can uniquely identify the restored data management object. For example, if the restored data management object is in XML , XML Signature value and the name of the root node of the restored data management object.

  On the other hand, the terminal management server 100 generates a command group for operating and editing each node constituting the restored data management object in accordance with the management request message (for example, Pkg # 1) received from the data restoration device 20a. Subsequently, the terminal management server 100 transmits a management command message including a command group for operating and editing the restored data management object to the data restoring device 20a. For example, the management command message uses DM protocol Pkg # 2 standardized by OMA-DMWG.

  The operation confirmation unit 27 provided in the data restoration device 20a operates and edits the restoration data management object based on the management command message, and records the processing result as a log. The operation confirmation unit 27 outputs the log as an operation confirmation result.

(Operation of terminal management system)
Hereinafter, the operation of the terminal management system according to the first embodiment will be described with reference to the drawings. FIG. 4 is a sequence diagram showing the operation of the terminal management system 1 according to the first embodiment.

  As shown in FIG. 4, in step 10, the data evacuation device 10a stores the migration data (that is, evacuation target data) to be migrated to the data restoration device 20a in the migration storage (ie, the evacuation storage 13). The data saving device 10a also transfers a migration data management object (ie, save data management object) for remotely managing migration data (ie, save target data) to be migrated to the data restoration device 20a to migration storage (ie, save). Store in storage 13).

  In step 11, the data restoration device 20a determines whether or not the same management object 25a as the migration data management object (that is, the restoration data management object) stored in the migration storage (ie, the restoration storage 23) has already been managed by the own device. To check. When the same management object 25a as the restoration data management object is already managed by the data restoration device 20a, the data restoration device 20a proceeds to the process of step 18. On the other hand, if the same management object 25a as the restoration data management object is not managed by the data restoration device 20a, the data restoration device 20a proceeds to the process of step 12.

  Here, as a method for confirming whether or not the same object as the restoration data management object is included in the management object 25a, the following method can be considered using the information for specifying the restoration data management object described above. For example, when the information specifying the restored data management object is XML Signature, a method may be considered in which the identity is determined by taking the XML Signature of the partial object of the management object 25a and comparing the two. For example, if the information specifying the restoration data management object is the name of the root node of the restoration data management object, the management object 25a is queried with the name, and the name of the root node of the restoration data management object exists. The method of confirming whether it is possible can be considered. In general, the latter method cannot guarantee the identity with the restored data management object. However, for example, when the data structure of the restored data management object is standardized, the identity can be guaranteed. An example of such a data structure is FUMO (Firmware Update Management Object) standardized by OMA-DM.

  In step 12, the data restoration device 20a reads the migration data management object (that is, the restoration data management object) stored in the migration storage (that is, the restoration storage 23) from the storage. Subsequently, the data restoration device 20 a transmits a distribution request for an application for performing remote management using the restored data management object to the application distribution server 200.

  In step 13, the application distribution server 200 distributes the application associated with the restoration data management object to the data restoration device 20a in response to the application distribution request.

  In step 14, the data restoration apparatus 20 a installs the application acquired from the application distribution server 200.

  In step 15, the data restoration device 20a acquires a management request message (for example, Pkg described above) including information for identifying the restoration data management object in order to obtain a command group for operating and editing each node constituting the restoration data management object. # 1) is transmitted to the terminal management server 100.

  In step 16, the terminal management server 100 transmits a management command message including a command group for operating and editing each node constituting the restored data management object to the data restoring device 20a.

  In step 17, the data restoration device 20 a checks the operation of the restoration data management object on the application acquired from the application distribution server 200.

  In step 18, the data restoration device 20a restores the terminal data (that is, restoration target data) stored in the storage (that is, the restoration storage 23).

  Here, if the same management object 25a as the restoration data management object is already managed by the own apparatus, the data restoration device 20a permits the restoration of the restoration target data. Further, when the same management object 25a as the restoration data management object is not managed by the data restoration device 20a, the data restoration device 20a restores the restoration target data except when the operation confirmation of the restoration data management object is successful. Restrict. For example, the restriction on restoration includes not permitting restoration of data, permitting restoration of only data that can be managed by a node that has been successfully confirmed by the operation check, and the like. The data restoration device 20a permits the restoration of the restoration target data when the operation confirmation of the restoration data management object is successful.

(Operation of data backup device)
Hereinafter, the operation of the data saving apparatus according to the first embodiment will be described with reference to the drawings. FIG. 5 is a sequence diagram showing the operation of the data saving apparatus 10a according to the first embodiment.

  As shown in FIG. 5, in step 20, the data save management unit 14 receives a data save request for requesting save of save target data from a human interface (for example, an input key).

  In step 21, the data save management unit 14 stores the save target data in the save storage 13 in response to the data save request.

  In step 22, the data save management unit 14 notifies the object management unit 15 of an object save request including information for specifying save target data. Here, the information for specifying the save target data is information that can uniquely specify the type of the save target data, and is, for example, a data type name such as “phone book”, “call origination / incoming history”, and “schedule”. .

  In step 23, the object management unit 15 returns information specifying the management object (saved data management object) corresponding to the save target data to the data save management unit 14 in response to the object save request. The data save management unit 14 stores information for specifying the save data management object in the save storage 13 together with the save target data. Here, the information for identifying the saved data management object is information that can uniquely identify the saved data management object. For example, if the saved data management object has an XML title, the value of the XML signature, the saved data management object, The name of the root node of the data management object. When the free capacity of the save storage 13 is sufficient to store the save data management object, the object management unit 15 may include the save data management object in the data stored in the save storage 13.

  In step 24, the object management unit 15 notifies the data save management unit 14 of an object save response indicating that the save data management object has been saved.

  In step 25, the data saving management unit 14 notifies a saving response indicating completion of saving of saving target data to a human interface (for example, a display).

(Operation of data restoration device)
Hereinafter, the operation of the data restoration apparatus according to the first embodiment will be described with reference to the drawings. FIG. 6 is a sequence diagram showing the operation of the data restoration device 20a according to the first embodiment.

  As shown in FIG. 6, in step 30, the data restoration management unit 24 receives a data restoration request for requesting restoration of restoration target data from a human interface (for example, an input key).

  In step 31, in response to the data restoration request, information specifying a restoration data management object for remotely managing restoration target data is read from the restoration storage 23.

  In step 32, the data restoration management unit 24 notifies the object management unit 25 of an object restoration request including information for specifying the restoration data management object.

  In step 33, the object management unit 25 confirms whether or not the same management object 25a as the restoration data management object is managed in response to the object restoration request. If the same management object 25a as the restored data management object is managed, the object management unit 25 proceeds to the process of step 39. On the other hand, if the same management object 25a as the restored data management object is not managed, the object management unit 25 proceeds to the process of step 34.

  Here, as a method for confirming whether or not the same object as the restoration data management object is included in the management object 25a, the following method can be considered using the information for specifying the restoration data management object described above. For example, when the information specifying the restored data management object is XML Signature, a method may be considered in which the identity is determined by taking the XML Signature of the partial object of the management object 25a and comparing the two. For example, if the information specifying the restoration data management object is the name of the root node of the restoration data management object, the management object 25a is queried with the name, and the name of the root node of the restoration data management object exists. The method of confirming whether it is possible can be considered. In general, the latter method cannot guarantee the identity with the restored data management object. However, for example, when the data structure of the restored data management object is standardized, the identity can be guaranteed. An example of such a data structure is FUMO (Firmware Update Management Object) standardized by OMA-DM.

  In step 34, the object management unit 25 acquires the restored data management object by using information for specifying the restored data management object. For example, the data restoration device 20a transmits information identifying the restoration data management object to the terminal management server 100, and the terminal management server 100 restores the restoration data management object corresponding to the information received from the data restoration device 20a. May be distributed to the data restoration device 20a. Alternatively, when the restoration data management object is stored in the restoration storage 23, the object management unit 25 may read the restoration data management object from the restoration storage 23.

  In step 35, the object management unit 25 notifies the application acquisition unit 26 of an application acquisition request including information specifying the restored data management object.

  In step 36, the application acquisition unit 26 acquires an application for performing remote management using the restored data management object from the application distribution server 200 in response to the application acquisition request, and installs the application in the restored terminal device 20. Subsequently, the application acquisition unit 26 acquires the application in response to the application acquisition request, and notifies the object management unit 25 that the installation of the application is completed.

  In step 37, the object management unit 25 notifies the operation confirmation unit 27 of an operation confirmation request for requesting operation confirmation of the restored data management object.

  In step 38, the operation confirmation unit 27 confirms the operation of the restored data management object on the application acquired from the application distribution server 200. Subsequently, the operation confirmation unit 27 notifies the object management unit 25 of the operation confirmation result of the restored data management object.

  In step 39, the object management unit 25 notifies the data restoration management unit 24 of an object restoration response. The object restoration response includes information indicating whether or not the same management object 25a as the restoration data management object is managed, the operation confirmation result of the restoration data management object, and the like.

  In step 40, when the same management object 25a as the restoration data management object is managed, the data restoration management unit 24 permits the restoration of the restoration target data. If the same management object 25a as the restoration data management object is not managed, the data restoration management unit 24 restores the restoration target data except when the operation confirmation of the restoration data management object stored in the restoration storage 23 is successful. Restrict restores. The data restoration management unit 24 permits restoration of restoration target data when the operation confirmation of the restoration data management object stored in the restoration storage 23 is successful.

  The data restoration management unit 24 reads the restoration target data from the restoration storage 23 when restoration of the restoration target data is permitted.

  In step 41, the data restoration management unit 24 stores the restored data to be restored (restored data) in the storage unit 22 (internal storage medium), and the restoration of the data to be restored is completed in a human interface (for example, a display). A restoration response indicating is sent.

(Function and effect)
In the first embodiment, the data evacuation device 10a transfers the migration data management object (saved data management object) to the migration storage (evacuation storage) together with the migration data (evacuation target data) to be migrated from the evacuation terminal device 10 to the restoration terminal device 20. 13).

  When the same management object 25a as the restoration data management object is already managed by the own device, the data restoration device 20a permits the restoration of the restoration target data. On the other hand, when the same management object 25a as the restoration data management object is not managed by the data restoration device 20a, the data restoration device 20a restores the restoration target data except when the operation check of the restoration data management object is successful. Limit.

  Therefore, even when data is migrated from the evacuation terminal device 10 to the restoration terminal device 20, it is possible to prevent remote management of data from becoming insufficient due to the fact that the management object does not operate normally on the application. can do.

[Second Embodiment]
The second embodiment will be described below with reference to the drawings. In the following, differences between the first embodiment and the second embodiment described above will be mainly described.

  Specifically, in the second embodiment, the data saving apparatus stores information for specifying the model of the saving terminal apparatus in the saving storage. The information specifying the model of the evacuation terminal device is information for specifying the software operating environment of the mobile terminal, and is, for example, a model name determined by the manufacturer that developed the evacuation terminal device. On the other hand, the data restoration device omits the operation confirmation of the restoration data management object when the model of the restoration terminal device is the same as the model of the evacuation terminal device.

  The reason that it can be omitted is that when the save terminal device and the restoration terminal device have the same model, they have a common software operating environment. Therefore, the same application as that operated on the evacuation terminal device can be used as the remote management application installed by the data restoration device. Therefore, the application operated on the restoration terminal device has the same function as that of the application operated on the evacuation terminal device, and therefore it is not necessary to check the operation.

(Operation of data restoration device)
Hereinafter, an operation of the data restoration apparatus according to the second embodiment will be described with reference to the drawings. FIG. 7 is a sequence diagram showing an operation of the data restoration device 20a according to the second embodiment. In FIG. 7, it should be noted that the same step numbers are assigned to the same processes as in FIG.

  As shown in FIG. 7, in step 341, the object management unit 25 reads information specifying the model of the evacuation terminal device 10 from the restoration storage 23 in addition to the restoration data management object.

  In step 361, the object management unit 25 determines whether the model of the restoration terminal device 20 is the same as the model of the evacuation terminal device 10. If the model of the restoration terminal device 20 is different from the model of the evacuation terminal device 10, the object management unit 25 proceeds to the process of step 37. On the other hand, when the model of the restoration terminal device 20 is the same as that of the evacuation terminal device 10, the object management unit 25 proceeds to the process of step 39.

  As described above, in the second embodiment, when the model of the restoration terminal device 20 is the same as that of the evacuation terminal device 10, the processing of step 37 and step 38, that is, the operation check of the restoration data management object is omitted. .

(Function and effect)
According to the second embodiment, the data restoration device 20a omits the operation confirmation of the restoration data management object when the model of the restoration terminal device 20 is the same as the model of the evacuation terminal device 10. Therefore, it is possible to reduce the processing load of the data restoration device 20a.

[Third Embodiment]
The third embodiment will be described below. In the following, differences between the first embodiment and the third embodiment described above will be mainly described.

  Specifically, the data evacuation device 10a (data evacuation management unit 14) is an important partial object having a higher importance in remote management than other partial objects among a plurality of partial objects constituting the evacuated data management object. Information for identifying the partial object (for example, position information indicating the position of the important partial object) is stored in the save storage 13.

  Here, the partial object having high importance in remote management can be set independently by the administrator using the terminal management system. The partial object having high importance in remote management is set by describing information indicating the importance in the definition file of the managed object. Alternatively, a partial object having high importance in remote management is set by describing it as property information of the partial object. For example, if the management object is a Management Object standardized by OMA-DM, an example of the former setting method is a free description area such as a Description element of a DDF (Device Description Framework) file that is a definition file of the Management Object. Information (importance level) indicating importance may be described as the value of. The information indicating the importance is, for example, a numerical value that increases as the importance of the partial object increases. For example, if the managed object is a Management Object standardized by OMA-DM, the latter example of the setting method includes information indicating importance as a value of a free description area such as a title element that is a Property of the DDF file. It only has to be described. Of course, regardless of the standardization of OMA-DM, a unique element may be defined and information indicating importance as the element may be described.

  On the other hand, the data restoration device 20a specifies information (for example, an important partial object that is a partial object having a higher importance in remote management than other partial objects among a plurality of partial objects constituting the restored data management object (for example, Position information indicating the position of the important partial object) is read from the restoration storage 23. The data restoration device 20a only performs the operation check of the important partial object. That is, the data restoration device 20a omits the operation check of the partial objects other than the important partial object.

  Specifically, the data restoration management unit 24 specifies information that identifies an important partial object that is a partial object having a higher degree of importance in remote management than other partial objects, in response to a data restoration request. (For example, position information indicating the position of the important partial object) is read from the restoration storage 23. The object management unit 25 notifies the operation confirmation unit 27 of an operation confirmation request including information specifying the important partial object. The motion check unit 27 only checks the motion of the important partial object.

  For example, taking the technology defined by OMA as an example, a management object (that is, a saved data management object and a restored data management object) has a tree structure composed of a plurality of nodes (partial objects). The position of an important node (important partial object) corresponding to an important management process in remote management of terminal data is represented by a notation that specifies the position of the node in the tree structure, such as XPATH.

  Next, consider a case where an instruction group for operating and editing an important node (important partial object) is acquired from the terminal management server 100. In such a case, the data restoration device 20a transmits a management request message to the terminal management server 100. For example, as a management request message, DM protocol Pkg # 1 standardized by OMA-DMWG is used. Pkg # 1 includes an “Ext” node included in “DevInfo”. The data restoration device 20a includes, under the “Ext” node, position information for specifying the position of the important node (important partial object) among the plurality of nodes constituting the restoration data management object.

  On the other hand, the terminal management server 100 generates a command group for operating and editing an important node (important partial object) according to a management request message (for example, Pkg # 1) received from the data restoration device 20a. Subsequently, the terminal management server 100 transmits a management command message including a command group for operating and editing an important node (important partial object) to the data restoration device 20a. For example, the management command message uses DM protocol Pkg # 2 standardized by OMA-DMWG.

(Function and effect)
According to the third embodiment, the data restoration device 20a performs only the operation confirmation of the important partial object. That is, the data restoration device 20a omits the operation check of the partial objects other than the important partial object. Therefore, it is possible to reduce the processing load of the data restoration device 20a.

[Fourth Embodiment]
The fourth embodiment will be described below. In the following, differences between the above-described first embodiment and the fourth embodiment will be mainly described.

  Specifically, in the fourth embodiment, the data evacuation device stores information specifying the model of the data evacuation device in the evacuation storage. The information specifying the model of the evacuation terminal device is information for specifying the software operating environment of the mobile terminal, and is, for example, a model name (for example, ΔΔΔ) determined by the manufacturer that developed the evacuation terminal device. The data restoration device separates the management object (restored data management object) received from the restoration storage (the saved storage) into partial objects (restored data management partial objects). The partial object is indicated by a path from the root node to each leaf node, for example.

  The data restoration device converts each partial object (restored data management partial object) into a partial object (terminal data management partial object) of a management object (terminal data management object) managed by the object management unit. Each of the conversion source partial object (restored data management partial object) and the conversion destination partial object (terminal data management partial object) performs the same management process on the management target data managed by the management object. Conversion processing is performed so that

(Configuration of data restoration device)
FIG. 8 is a block diagram showing a configuration of a data restoration device 20a according to the fourth embodiment. In FIG. 8, the data restoration device 20 a includes an object conversion unit 28.

  When the object management unit 25 receives the object restoration request, the object management unit 25 notifies the object conversion unit 28 of an object conversion request including information for specifying the restoration data management object included in the object restoration request and information for specifying the model of the evacuation terminal. To do. The object conversion request may include information specifying the restored data management partial object instead of the information specifying the restored data management object.

  The object management unit 25 receives an object conversion response including a partial object that has been converted into an object by the object conversion unit 28 and position information (for example, XPATH) of the partial object that has not been converted by the object conversion unit 28.

  The object management unit 25 notifies the application acquisition unit 26 of an application acquisition request including position information of a partial object that has not been converted into an object included in the object conversion response. Subsequently, in response to the application acquisition response, the object management unit 25 requests an operation confirmation of the partial object specified by the position information where the application has been acquired when the application acquisition response indicates successful acquisition of the application. A confirmation request is notified to the operation confirmation unit 27. The operation check request includes position information that the application has acquired.

  The application acquisition unit 26 acquires, from the application distribution server 200, an application that performs remote management using the partial object specified by the position information included in the application acquisition request. Specifically, the application acquisition unit 26 transmits, to the application distribution server 200, an application distribution request associated with position information that identifies the partial object. In response to an application distribution request, the application distribution server 200 distributes an application associated with position information for specifying a partial object. The application acquisition unit 26 notifies the object management unit 25 of an application acquisition response including position information that has acquired the application and position information that has not been able to acquire the application.

  The motion confirmation unit 27 confirms the motion of the partial object on the application acquired by the application acquisition unit 26. The operation confirmation unit 27 notifies the object management unit 25 of the operation confirmation result.

  The object conversion unit 28 extracts the restored data management partial object based on the information specifying the restored data management object or the information specifying the restored data management partial object.

  Specifically, when receiving the object conversion request, the object conversion unit 28 separates the management object included in the object conversion request into partial objects. If the partial object is a tagged structured object (or document) such as a Management Object defined in OMA-DM, for example, the partial object is separated into a path from the root node to each leaf node.

  The object conversion unit 28 converts the restored data management partial object into information for specifying the terminal data management partial object that executes the same management process that can be executed by the terminal management system using the restored data management object.

  Specifically, the object conversion unit 28 includes a conversion table that associates the restored data management partial object with the terminal data management partial object. The conversion table associates the restored data management partial object with the terminal data management partial object from the viewpoint that the same management processing is possible.

  FIG. 9 is a diagram illustrating an example of a conversion table according to the fourth embodiment. The object conversion unit 28 converts (rereads) the restored data management partial object (110b in FIG. 9) into the terminal data management partial object (110c in FIG. 9) using the conversion table shown in FIG. It is assumed that this conversion table is created by the management system operator or the administrator of the management target data. The conversion table may be included in the object conversion unit in advance from the factory shipment stage. The conversion table may be downloaded via a network.

  As shown in FIG. 9, the conversion table is preferably provided for each device model (100a, 100b, 100c). When a conversion table is provided for each model of the device, the object conversion unit 28 selects an appropriate conversion table based on information for specifying the model of the saving terminal included in the object conversion request. Specifically, the object conversion unit 28 confirms and selects 110a in FIG. When the restoration terminal device 20 is a device included in an embedded device such as a mobile phone, the size of the conversion table cannot be increased so much in consideration of the capacity of a storage area accessible by the device. Generally speaking, it should be noted that there are partial objects that cannot be converted by the conversion table. The object conversion unit 28 notifies the object management unit 25 of an object conversion response including the converted partial object and the partial object that cannot be converted.

  Upon receiving the object conversion response, the object management unit 25 requests object conversion from an external device such as a server (for example, a terminal management server) on the network when a partial object that could not be converted is included in the object conversion response. May be. For this request, the object management unit 25 notifies the server of an object conversion request including a partial object that could not be converted (included in the object conversion response). For example, if the server is an OMA-DM server, the object management unit 25 notifies the object conversion request via the OMA-DM client. The OMA-DM client notifies the OMA-DM server of the object conversion request by using, for example, the Generic Alert defined by the OMA-DM protocol. When receiving the object conversion request, the OMA-DM server converts the partial object in response to the object conversion request. The OMA-DM server includes the conversion table described above, and converts the partial object included in the object conversion request into a partial object of a management object managed by the migration destination terminal.

  It should be noted here that some partial objects cannot be converted even by the server. The converted partial object is included in the object conversion response and transmitted to the OMA-DM client. For partial objects that cannot be converted, a command group (a group of Add commands for adding a node in the OMA-DM command) for registering the partial object as a managed object managed by the object management unit 25 is sent to the DM client. Here, when the restoration terminal apparatus 20 fails to add a node due to the storage capacity being exceeded or the like, the partial object that has failed to be added is included as an object conversion response, and, for example, OMA-DM using a generic alert or the like. Send to DM client. When receiving the object conversion response, the OMA-DM client notifies the object management unit 25 of the object conversion response.

  The object management unit 25 may further include the restoration target data held by the data restoration management unit 24 as an object conversion request and send it to the server. Assuming that the server is an OMA-DM server, the server that has received the object conversion request performs partial object conversion as described above. For a partial object that has been converted, an instruction group for setting restoration target data managed by the partial object for the converted partial object (Replace that instructs overwriting of values in the OMA-DM command) A group of commands) is generated and sent to the OMA-DM client of the restoration terminal device 20. When the server receives the execution result of the instruction group from the OMA-DM client, the server includes the partial object in which the execution has failed as an object conversion response, and uses, for example, the OMA-DM using the Generic Alert defined in the OMA-DM protocol Send to client. When receiving the object conversion response, the OMA-DM client notifies the object management unit 25.

  Note that, when adding a partial object, the server may instruct the restoration terminal device 20 to download and introduce an application for managing restoration target data using the partial object. For example, by using a management object (SCOMO) that manages software components discussed in the WG of OMA-DM, it is possible to download and install an application to the restoration terminal device 20 in a server-driven manner. Specifically, the object management unit 25 provided in the data restoration device 20a receives a request for downloading an application. In response to the download request, the object management unit 25 notifies the application 26 of an application acquisition request. The application acquisition unit 26 downloads an application that operates on the restoration terminal device 20 from the server, and introduces the application to the restoration terminal device 20.

  Further, the server may generate a command group for checking the operation of the added partial object and send it to the OMA-DM client in order to check the management operation of the application installed in the restoration terminal device 20. . If the server accepts the restoration target data, the restoration target data is set for the partial object that has been successfully confirmed to the management operation based on the introduction result of the application received from the OMA-DM client and the management operation confirmation result. . Application installation results that include partial objects for which application installation has failed, management operation confirmation results that include partial objects for which management operation confirmation has failed, and restoration target data setting results that include partial objects for which restoration target data settings have failed It is included in the conversion response and sent to the OMA-DM client. When receiving the object conversion response, the OMA-DM client notifies the object management unit 25.

  If the object conversion response includes a partial object for which object conversion has been successful, the object management unit 25 updates the terminal data management object with the partial object for which object conversion has been successful. That is, the object management unit 25 replaces the partial object corresponding to the partial object that has been successfully converted from the partial objects included in the terminal data management object with the partial object that has been converted by the external device (server).

  On the other hand, when the object conversion response includes a partial object in which the object addition has been successful, the object management unit 25 has succeeded in the object addition (that is, the partial object acquired from the external device (server)). Is newly added to the terminal data management object. Subsequently, the object management unit 25 notifies the application acquisition unit 26 of an application acquisition request including a partial object in which object addition has been successful. As described above, the application acquisition unit 26 acquires an application that executes management processing on the restoration terminal device 20 using the partial object that has been successfully added.

  On the other hand, if the object conversion response includes a partial object that has failed to be converted (including data setting failure or object addition failure depending on the system configuration), the object management unit 25 restores the object including the partial object. The response is notified to the data restoration management unit 25. When the object conversion response includes an application introduction result or a management operation confirmation result, the object management unit 25 notifies the data restoration management unit 25 of an object restoration response including a partial object that has not been successfully confirmed.

  Upon receiving the object restoration response, the data restoration management unit 24 restricts restoration of restoration target data managed by the partial object when the object restoration response includes a partial object that has failed to be restored.

(Function and effect)
According to the fourth embodiment, the data restoration device 20a replaces an object to be restored with a management object that it manages. That is, since the data restoration device 20a only needs to add an object that cannot be replaced, the space efficiency is increased. In addition, with respect to an object that can be read, an application for managing using the object has already been introduced, so that it is possible to avoid the introduction of a useless application.

[Other Embodiments]
Although the present invention has been described with reference to the above-described embodiments, it should not be understood that the descriptions and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples and operational techniques will be apparent to those skilled in the art.

  In the first embodiment described above, the data restoration device 20a reads the restoration data management object from the restoration storage 23 and restores the restoration data when the same management object 25a as the restoration data management object is not managed by the own device. Get an application that performs remote management using managed objects. However, the present invention is not limited to this. Specifically, the data restoration device 20a may immediately limit the restoration of the restoration target data when the same management object 25a as the restoration data management object is not managed by the own device.

  In the third embodiment described above, the data restoration device 20a uses “DevInfo” standardized by OMA-DMWG to determine the position of the important node (important partial object) constituting the restoration data management object. 100 is notified. However, the present invention is not limited to this. Specifically, the data restoration device 20a uses the “Generic Alert” standardized by OMA-DMWG to indicate the position of the important node (important partial object) constituting the restoration data management object to the terminal management server 100. You may be notified.

It is a figure which shows the structure of the terminal management system 1 which concerns on 1st Embodiment. It is a figure which shows the structure of the data evacuation apparatus 10a which concerns on 1st Embodiment. It is a figure which shows the structure of the data decompression | restoration apparatus 20a which concerns on 1st Embodiment. It is a sequence diagram which shows operation | movement of the terminal management system 1 which concerns on 1st Embodiment. It is a sequence diagram which shows operation | movement of the data evacuation apparatus 10a which concerns on 1st Embodiment. It is a sequence diagram which shows operation | movement of the data restoration apparatus 20a which concerns on 1st Embodiment. It is a sequence diagram which shows operation | movement of the data restoration apparatus 20a which concerns on 2nd Embodiment. It is a figure which shows the structure of the data restoration apparatus 20a which concerns on 4th Embodiment. It is a figure which shows the conversion table which concerns on 4th Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Terminal management system, 10 ... Evacuation terminal device, 10a ... Data evacuation device, 11 ... Application processing part, 12 ... Storage part, 13 ... Evacuation storage, 14 ... Data evacuation management unit, 15 ... object management unit, 15a ... management object, 20 ... restoration terminal device, 20a ... data restoration device, 21 ... application processing unit, 22 ... storage unit , 23 ... Restoration storage, 24 ... Data restoration management unit, 25 ... Object management unit, 25a ... Management object, 26 ... Application acquisition unit, 27 ... Operation confirmation unit, 100. ..Terminal management server 200 ... Application distribution server 300 ... Network

Claims (12)

A data evacuation device for evacuating the data stored in the evacuation terminal device as evacuation target data to the evacuation storage from the evacuation terminal device storing data remotely managed by the terminal management system;
A terminal management system including a data restoration device that obtains restoration target data to be remotely managed by the terminal management system from a restoration storage, and restores the restoration target data in a state of being remotely managed on the restoration terminal device. And
The evacuation target data and the restoration target data are migration data to be migrated from the evacuation terminal device to the restoration terminal device,
The data saving device is:
A data evacuation management unit that accepts a data evacuation request for evacuating the evacuation target data;
A first object management unit for managing a save data management object for remotely managing the save target data;
The data save management unit notifies the first object management unit of an object save request including information specifying the save target data;
In response to the object saving request, the first object management unit returns information specifying the saved data management object to the data saving management unit,
The data save management unit stores information for specifying the save data management object and information for specifying the model of the save terminal device in the save storage together with the save target data,
The data restoration device includes:
A data restoration management unit that accepts a data restoration request for requesting restoration of the restoration target data, and restores the restoration target data to the restoration terminal device;
A second object management unit that manages a terminal data management object that is an external interface for remotely managing terminal data stored in the restored terminal device;
In response to the data restoration request, the data restoration management unit reads information identifying a restoration data management object that is an external interface for remotely managing the restoration target data from the restoration storage, and stores the restoration data management object. Notifying the second object management unit of an object restoration request including information to be identified,
The second object management unit extracts information identifying the restored data management object from the object restoration request, and performs the same management process as the management process that can be executed by the terminal management system using the restored data management object. Notifying the data restoration management unit of a confirmation result indicating whether or not execution is possible using the terminal data management object,
The terminal management system, wherein the data restoration management unit restricts restoration of the restoration target data when the confirmation result is negative. The save data management object is composed of a plurality of partial objects,
The data evacuation management unit stores, in the evacuation storage, information specifying an important partial object that is a partial object having a higher importance in remote management than the other partial objects among the plurality of partial objects. The terminal management system according to claim 1.   The second object management unit includes, in the confirmation result, whether or not a terminal data management object constructed based on the same name as the restored data management object or the same structure definition as the restored data management object is managed. The terminal management system according to claim 1. The restoration data management object is composed of one or more restoration data management partial objects,
The terminal data management object is composed of one or more terminal data management partial objects,
Based on the information for specifying the restored data management object or the information for specifying the restored data management partial object, the information for identifying the restored data management partial object is extracted, and the restored data management specified by the extracted information A conversion unit that converts information identifying the restored data management partial object into information identifying the terminal data management partial object that executes the same management process as the management process executable by the terminal management system using the partial object; The terminal management system according to claim 1, further comprising: The second object management unit outputs a conversion request including the restored data management partial object that could not be converted by the conversion unit to an external device,
The terminal management system according to claim 4, wherein the second object management unit updates the terminal data management object with the restored data management partial object converted by the external device. The second object management unit uses the restored data management partial object that could not be converted by the conversion unit to execute a partial object that executes the same management process as the management process that can be executed by the terminal management system on the restored terminal device. Obtained from an external device, newly adding a partial object obtained from the external device to the terminal data management object,
The terminal management according to claim 4, further comprising an acquisition unit that acquires an application that executes the same management process as the management process that can be executed by the terminal management system, using the partial object acquired from the external device. system. The second object management unit outputs a conversion request including the restored data management object or the restored data management partial object to an external device;
The second object management unit is information for specifying the restored data management partial object converted or added by the external device, or information for specifying the restored data management partial object that has not been converted or added by the external device From the external device, the conversion result including
The second object management unit, based on the conversion result, out of the same management process that can be executed by the terminal management system using the restored data management object, a part that cannot be executed by the terminal data management object The terminal management system according to claim 4 , wherein the information to be shown is notified to the data restoration management unit as the confirmation result. An acquisition unit for acquiring an application for performing remote management using the restored data management object;
An operation confirmation unit that confirms the operation of the restored data management object on the application acquired by the acquisition unit;
The second object management unit reads the restoration data management object from the restoration storage when the same terminal data management object as the restoration data management object is not managed;
The second object management unit notifies the acquisition unit of an application acquisition request including information specifying the restored data management object,
The second object management unit, when the application is acquired in response to the application acquisition request, notifies the operation confirmation unit of an operation confirmation request for requesting operation confirmation of the restored data management object;
The terminal management system according to claim 1, wherein the data restoration management unit restricts restoration of the restoration target data when an operation check of the restoration data management object fails. In response to the data restoration request, the data restoration management unit reads information identifying the model of the evacuation terminal device stored in the restoration storage from the restoration storage,
The data restoration management unit notifies the second object management unit of the object restoration request including information specifying a model of the evacuation terminal device,
The said 2nd object management part abbreviate | omits the operation | movement confirmation of the said restoration | recovery data management object, when the model of the said restoration | recovery terminal device is the same as the model of the said evacuation terminal device. Terminal management system. The restored data management object is composed of a plurality of partial objects,
In response to the data restoration request, the data restoration management unit restores information identifying an important partial object that is a partial object having a higher importance in remote management than the other partial objects from among the plurality of partial objects. Read from storage,
The second object management unit notifies the operation confirmation unit of the operation confirmation request including information identifying the important partial object;
The terminal management system according to claim 8, wherein the operation check unit performs only the operation check of the important partial object. The data evacuation device stores a migration data management object for remotely managing the migration data in a migration storage,
The data restoration device reads the migration data management object from the migration storage when the same management object as the migration data management object is not managed by its own device,
The data restoration device acquires an application for performing remote management using the migration data management object,
The data restoration device performs an operation check of the migration data management object on the application,
The terminal management system according to claim 1, wherein the data restoration device restricts restoration of the migration data when an operation check of the migration data management object fails. A terminal management server for remotely managing terminal data stored in the evacuation terminal device or the restoration terminal device;
The data restoration device acquires a command group for operating and editing the migration data management object from the terminal management server,
The terminal management system according to claim 11, wherein the data restoration apparatus performs an operation check of the migration data management object on the application according to a group of instructions acquired from the terminal management server.

Images