WO2007003103A1 - Méthode de partage de données et méthode de récupération de données sauvegardées - Google Patents

Méthode de partage de données et méthode de récupération de données sauvegardées Download PDF

Info

Publication number
WO2007003103A1
WO2007003103A1 PCT/CN2006/001432 CN2006001432W WO2007003103A1 WO 2007003103 A1 WO2007003103 A1 WO 2007003103A1 CN 2006001432 W CN2006001432 W CN 2006001432W WO 2007003103 A1 WO2007003103 A1 WO 2007003103A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
data
information
management server
shared data
Prior art date
Application number
PCT/CN2006/001432
Other languages
English (en)
Chinese (zh)
Inventor
Kepeng Li
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007003103A1 publication Critical patent/WO2007003103A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments

Definitions

  • the present invention relates to the field of communication device management technologies, and in particular, to a data management method for a communication device. More specifically, it relates to data sharing and data backup recovery methods.
  • a mobile terminal is an important component of an entire mobile operation service system, and along with an increasing performance of a mobile terminal, various software (refer to application software, such as game software, etc.) and firmware (refer to terminal equipment) running in the terminal device Low-level platform software) is also emerging.
  • application software such as game software, etc.
  • firmware refer to terminal equipment
  • Low-level platform software Low-level platform software
  • OMA Open Mobile Alliance
  • DM Device Management
  • the specific processing flow of the anti-virus software update packet sent by the DM server is shown in Figure 1.
  • the specific implementation process is as follows (the part of the process of establishing the connection phase between the initial terminal device and the DM server is omitted).
  • the DM server sends a request message for obtaining the software version information to the terminal device.
  • the DM server obtains the related software information from the management tree of the terminal device by sending a script with a Get command, as follows:
  • the terminal device feeds back a response message carrying its own software version information, wherein the terminal device returns the software version information to the DM server through the Results command, as follows:
  • the DM server selects the software update data packet corresponding to the software according to the software version information fed back by the terminal device, and sends the software update data packet to the terminal device; wherein the DM server sends the software update data packet to the terminal device through the Replace command. details as follows:
  • the terminal device saves the software update data packet delivered by the DM server, and runs the software update data packet to upgrade and install its own anti-virus software;
  • the terminal device feeds back a success message to the DM server to indicate that the terminal device has successfully received the software update data packet.
  • the terminal device can only passively receive data sent by the DM server, but cannot upload data to the DM server, and cannot actively download data from the DM server. In this way, the user cannot share his own data.
  • the user forwards the characteristic data on the terminal device to the friend through the DM server, thereby realizing data sharing, wherein the characteristic data here includes but is not limited to application data (such as ringtones). , screensavers and wallpapers, etc., applications (firmware, software) and configuration parameters, etc.; also can not get the data that others are willing to share, which makes it difficult to share data between different terminal devices, so that users can not get better user experience.
  • the terminal device will have its own data information (such as ringtone, screen saver, wallpaper, application software and parameter configuration).
  • the data is backed up to the DM server in a tree-like storage structure to implement data backup processing of the terminal device.
  • the terminal device obtains each backup data one by one from the tree-like storage structure stored by the DM server. Then, the device is restored to the terminal device, thereby implementing data recovery processing of the terminal device.
  • the tree storage structure on which the terminal device performs data backup and recovery processing is as shown in FIG. 2, wherein the "Backup" node and the "Restore” node in the tree storage structure are executable nodes, which can be respectively executed by Exec commands. Call execution.
  • the terminal device can remotely back up the data information to the DM server by executing the "Backup" node command.
  • the specific processing procedure is as follows:
  • the terminal device can restore the backup data from the DM server by executing the "Restore" node command.
  • the specific processing procedure is as follows:
  • the backup data recovery processing of the terminal device from the DM server is based on the application name (Application Name), the application manufacturer (Application Manufacture), the application version (Application Version) and the like, and the corresponding data is searched in the DM server. Restore the discovered application data to the local.
  • the existing OMA DM-based terminal device data backup and recovery method in the proposed state has a narrow application scope, and can only be applied to backup and recovery of data of the terminal device, and cannot be applied to user replacement.
  • Data backup and recovery processing for terminal devices due to the weak function of the tree storage structure on which data backup and recovery processing depends, some data may not have information such as name, manufacturer and version; thus the terminal device backs up data to the DM server. After that, if you want to restore the backup data from the DM server, how to find the data with no related name, manufacturer and version information from the tree storage structure stored in the DM server for backup data recovery is more difficult. solved problem. Summary of the invention
  • the object of the present invention is to provide a data sharing method to enable different terminal devices to pass
  • the DM server implements data sharing.
  • the present invention also provides a data backup and recovery method, so that the data backup of the terminal device and its recovery processing can be applied to a wider range.
  • a data sharing method including the steps of: the source terminal device participating in the data sharing reporting the shared data to the device management server;
  • the device management server delivers the shared data reported by the source terminal device to the corresponding destination terminal device according to the source terminal device information and the destination terminal device information that are involved in the data sharing.
  • the process of reporting the shared data to the device management server includes:
  • the source terminal device reports the shared data to the device management server according to the request of the device management server;
  • the source terminal device actively reports the shared data to the device management server.
  • the step of the device management server delivering the shared data to the destination terminal device includes: the destination terminal device requests the device management server to download the shared data;
  • the device management server sends the shared data to the destination terminal device in response to the request.
  • the user reports the source terminal device information and the destination terminal device information that participate in the data sharing to the device management server by using an external notification manner; or
  • the source terminal device or the destination terminal device carries the source terminal device information and the destination terminal device information that are involved in the data sharing in the shared data and reports them to the device management server.
  • the terminal device information is an international mobile station device identification code of the terminal device or an international mobile subscriber identity of the user to which the terminal device belongs.
  • the device management server authenticates the source terminal device, and determines whether the source terminal device can share data with the destination terminal device.
  • the authentication of the source terminal device includes:
  • the device management server reads a destination terminal device identifier list set in the source terminal device; and determining that the destination terminal device identifier is in the destination terminal device identifier list When the source terminal device is allowed to share the shared data to the destination terminal device.
  • the device management server authenticates the destination terminal device, and determines whether the destination terminal device can share the shared data provided by the source terminal device.
  • the authenticating the target terminal device includes:
  • the device management server reads the source terminal device identifier list set in the destination terminal device; When it is determined that the source terminal device identifier is in the source terminal device identifier list, the destination terminal device is allowed to share the shared data provided by the source terminal device.
  • the method further comprises:
  • the DM server obtains the shared data from the source terminal device, and saves the acquired shared data, and then sends the shared data to the destination terminal device; or
  • the DM server directly sends the shared data received from the source terminal device to the destination terminal device;
  • the DM server saves the acquired shared data, and after the shared data is sent to the destination terminal device, deletes the saved shared data; or
  • the shared data is identified.
  • the DM server sends the saved shared data to the destination terminal device according to the identifier.
  • another data sharing method for implementing data sharing between terminal devices based on an Open Mobile Alliance device management specification, including the steps of: sharing data provided by a source terminal device participating in data sharing The address information of the stored location is reported to the device management server;
  • the device management server sends the address information reported by the source terminal device to the corresponding destination terminal device according to the source terminal device information and the destination terminal device information that participate in the data sharing; the destination terminal device stores the shared data according to the obtained address information.
  • the location gets the shared data provided by the source terminal device.
  • the method further comprises the steps of:
  • the user to which the source terminal device belongs sets the authentication key of the address information, and notifies the set authentication key to the user to which the destination terminal device belongs;
  • the device management server authenticates the user to which the destination terminal device belongs before sending the address information to the corresponding destination terminal device.
  • the address information is sent to the destination terminal device.
  • the address information is a universal resource locator of a location where the shared data is stored on the source terminal device.
  • the destination terminal device accesses an address stored by the shared data through a network transmission protocol, and acquires the shared data.
  • a data backup and recovery method comprising the steps of:
  • the original terminal device sends its own data information to the device management server for backup.
  • the original terminal device or the updated terminal device restores the data information backed up in the device management server to the local device.
  • the step of reporting the data information to the device management server includes the following steps:
  • the device management server sends a message requesting the original terminal device to report the data information to be backed up to the original terminal device;
  • the original terminal device reports the data information to be backed up to the device management server in response to the received request message.
  • the original terminal device actively reports the data information to be backed up to the device management server.
  • the device management server delivers the data information to be backed up to the original terminal device or the updated terminal device;
  • the steps of restoring the data information backed up in the device management server to the local device of the terminal device include:
  • the original terminal device or the updated terminal device requests the device management server to download the backed up data information
  • the device management server delivers the backed up data information to the original terminal device or the updated terminal device in response to the received request.
  • the data backup and recovery method further comprises:
  • the device management server associates the backup data information reported by the original terminal device with the user identification information of the user to which the original device belongs.
  • the corresponding backup data information is searched according to the user identification information of the original terminal device or the user to which the updated terminal device belongs.
  • another data backup and recovery method for implementing terminal device data backup and recovery processing based on the Open Mobile Alliance device management specification, including the steps of:
  • the original terminal device sends the address information of the backup location of its own data information to the device.
  • Management server for storage
  • the original terminal device or the updated terminal device acquires address information of the location where the data information is backed up in the device management server;
  • the backup data location is accessed to the backup location of the data information according to the obtained address information, and the backup data information is restored to the local device.
  • the method further comprises the steps of:
  • the user of the original terminal device sets an authentication key for obtaining the address information; and before the device management server obtains the address information, the user of the original terminal device is authenticated;
  • the device management server After the user of the original terminal device passes the authentication, the device management server sends the address information to the original terminal device or the updated terminal device.
  • the address information is a universal resource locator of the location where the data information is backed up.
  • the data sharing method sets the address information of the location where the shared data or the shared data is located to the DM server through the source terminal device, and the DM server according to the source terminal device information and the destination terminal device information participating in the data sharing.
  • Providing the shared data to the destination terminal device or providing the address information of the location where the shared data is stored to the destination terminal device, and the destination terminal device acquires the shared data according to the address information of the location where the shared data is stored, thereby implementing different terminal devices.
  • Data sharing can be achieved through the DM server. Improve user satisfaction.
  • the data backup and recovery method provided by the present invention sets the data information to be backed up by the original terminal device or the address information of the location where the data information to be backed up is set to the DM server, and the subsequent data information in the original terminal device is lost or damaged.
  • FIG. 1 is a flowchart of a specific process of sending an update packet by a DM server;
  • FIG. 2 is a schematic diagram of a tree storage structure for data backup and recovery processing of a terminal device
  • FIG. 3 is a schematic diagram of a tree storage structure in a terminal device according to the method provided by the present invention
  • FIG. 4 is a schematic diagram of a data sharing implementation process according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a processing procedure for authenticating a terminal device by a DM server according to the present invention
  • FIG. 6 is a schematic diagram of an implementation process of reporting shared data from a source terminal device to a DM server according to the present invention
  • FIG. 7 is a schematic diagram of another implementation process of reporting shared data from a source terminal device to a DM server according to the present invention.
  • FIG. 8 is a schematic diagram of an implementation process of a DM server transmitting shared data to a destination terminal device according to the present invention
  • FIG. 9 is a schematic diagram of an implementation process of a DM server transmitting shared data to a destination terminal device according to the present invention.
  • FIG. 10 is a schematic diagram showing an implementation process of data information backup and recovery processing according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of an implementation process of an exemplary data backup and recovery method according to the present invention.
  • FIG. 12 is a process flow diagram of another exemplary data backup and recovery method according to the present invention.
  • FIG. 13 is a schematic diagram showing a process of realizing data sharing between terminal devices in accordance with an embodiment of the present invention.
  • FIG. 14 is a flowchart showing a process of implementing data backup recovery in accordance with another embodiment of the present invention.
  • the two device management-based data sharing methods proposed by the present invention are respectively described.
  • the first method for data sharing based on device management is to realize mutual sharing of data between terminal devices by relaying and forwarding shared data by the DM server;
  • the second method for data sharing based on device management is adopted by the DM server.
  • the address information of the location where the shared data is stored is forwarded to share data between the terminal devices.
  • the present invention is directed to the above two data sharing methods, and accordingly, a data backup and recovery method based on device management is proposed.
  • FIG. 3 shows a subtree tree storage structure stored in the terminal device according to the present invention, and FIG. 3 is referred to.
  • the storage structure strategy is used to facilitate the DM server to find.
  • the data to be sent (including shared data, address information of the location where the shared data is stored, pre-backed up data information, or backup data information)
  • the address information of the storage location, etc. is uniformly stored in the shared subtree
  • the data to be received (including the shared data, the address information of the location where the shared data is stored, the restored backup data information, or the address information of the location where the backup data information is stored, etc., etc.) ) is also stored in the shared subtree.
  • the internal node is the starting node of the shared subtree and contains shared data information, allowed operating permission descriptions, and some operational commands.
  • the internal node can be placed anywhere under the root node of the device management tree (DM tree). It is a permanent node (a permanent node refers to a node that the DM server cannot delete), which can be generated by the device manufacturer or by other management parties. Need to be produced. It is described in the Device Description Framework (DDF, Device Description Framework) document in its specific location on the DM tree.
  • DDF Device Description Framework
  • This node is the parent node of the shared data information, and the user will be willing to share the shared data. Placed under this node, the shared data obtained from other terminal devices is also placed under this node,
  • DMAgent is an application running on the terminal device, which is responsible for the device management service, interacts with the DM server, interprets the execution device management command, as long as the terminal supporting the DM service has DMAgent) or the user organizes the use of the node. data.
  • This node is used to describe the name of the shared data.
  • the node is used to store description information of the shared data.
  • the node is used to store the URI of the shared data on the DM tree.
  • the shared data is the node data on the DM tree, only the URI of the shared data is stored, thereby avoiding wasting storage space; and when the shared data is not in the DM tree, the node is used.
  • the ⁇ Data> node below stores the actual shared data.
  • This node is used to store the actual shared data, that is, when it is sent, it stores shared data that is not on the DM tree, and also stores the received shared data.
  • This node is used to describe the type of shared data, which is convenient for recipients to identify.
  • This node is used to describe the size of the shared data.
  • This node is used to store other relevant information about the shared data.
  • This node is used to describe a terminal device that allows reading of a shared subtree, that is, a terminal device that allows acquisition of shared data from the shared subtree.
  • the node is used to describe the IMSI (International Mobile Subscriber Identit) information of the terminal device that is allowed to obtain the information of the shared subtree.
  • the IMSI included in the node may be added, modified, and deleted by the user.
  • This node is used to describe a terminal device that allows writing of a shared subtree, that is, a terminal device that allows transmission of shared data to the shared subtree.
  • the node is used to describe the IMSI information of the terminal device that allows the shared data to be sent to the shared subtree.
  • the IMSI included in the node can be added, modified, and deleted by the user.
  • This node is used to describe the parent node of the related operations on the shared subtree.
  • the node exists as a collection of related operations for sharing data. It is equivalent to a container. It is followed by some related operation commands.
  • This node can be used by the Exec command (the Exec command is a command in the DM protocol. Execute the executable node. Since Upload and Download are not existing commands in the DM protocol, they must be called by Exec to initiate the upload operation and upload the shared data to the DM server. Upload can call other protocols to complete the upload operation. The DM server can be notified to extract.
  • the node can be initiated by the Exec command (this Exec command can be initiated by the DM server or by the terminal device, but all executed by the terminal device) to initiate the download operation, that is, download the shared data from the DM server to the shared subtree. Download can call other protocols (such as OMA Download protocol) to complete the download operation, or notify the DM server to deliver.
  • Exec command can be initiated by the DM server or by the terminal device, but all executed by the terminal device
  • Download can call other protocols (such as OMA Download protocol) to complete the download operation, or notify the DM server to deliver.
  • This node is used as a reservation for future extensions and can be used to describe other related operations on the shared subtree.
  • This node is used to store other relevant information of the shared subtree, which is reserved for future extensions.
  • the following describes an invention solution for relaying shared data by a DM server to implement data sharing between terminal devices.
  • the present invention implements data between terminal devices by relaying and forwarding shared data by a DM server.
  • Schematic diagram of the main implementation process of sharing, the main implementation process is as follows:
  • step S01 a session connection is established between the DM server and the same terminal device (the process of establishing the session connection phase is clearly defined in the OMA DM specification, which is not described here), where the connection establishment phase includes the DM server source.
  • the process of authorization authentication by the terminal device which will be explained later.
  • Step S02 the source terminal device participating in the data sharing reports the shared data to the DM server; the process may report the shared data to the DM server by the source terminal device actively; The source terminal device may request the source terminal device to report the shared data, and the source terminal device reports the shared data in response to the request of the DM server.
  • Step S03 the DM server establishes a session connection with the destination terminal device (the process of establishing the session connection phase is clearly defined in the OMA DM specification, and is not described here), wherein the establishment connection phase includes the DM server for the purpose.
  • the process of authorization authentication by the terminal device which will be explained later.
  • Step S04 The DM server sends the shared data reported by the source terminal device to the corresponding destination terminal device according to the source terminal device information and the destination terminal device information that participate in the data sharing.
  • the process may be performed by the DM server directly sending the shared data to the destination terminal device.
  • the destination terminal device may also request the DM server, and the DM server downloads the shared data to the destination terminal device in response to the request.
  • the source terminal device information and the destination terminal device information that notify the DM server to participate in data sharing can be implemented in the following two ways:
  • the user notifies the source terminal device information and the destination terminal device information participating in the data sharing by means of an external notification mode (ie, a method other than the DM protocol, such as the user calling the operator's customer service center, or the user logging in to the Web site).
  • an external notification mode ie, a method other than the DM protocol, such as the user calling the operator's customer service center, or the user logging in to the Web site.
  • the data transmission mode may also be that the source terminal device uploads the shared data to the DM server, and the destination terminal device downloads from the DM server.
  • the source terminal device notifies the DM server of the source terminal device information and the destination terminal device information that participate in the data sharing in the shared data. That is, the source terminal device information or the destination terminal device information is carried in the shared data, and the DM server is notified by the DM protocol command, the destination terminal device to which the shared data is to be transmitted, or from which source terminal device the shared data is to be acquired.
  • the address of the DM server is processed into a direct address in the shared data, and the address of the source terminal device or the destination terminal device is processed into an indirect address. And because the current OMA DM protocol cannot support the data bearer indirect address for reporting
  • ⁇ Indirect> is set to be used in the shared data initiated by the source terminal device or the destination terminal device. It should be used together with the existing tag ⁇ 8011 « ⁇ > or 3 ⁇ 4 61>, and the ⁇ 80111 ⁇ > is used together to indicate the source terminal device address as the indirect.
  • the address, used in conjunction with ⁇ Ding & 1 ⁇ 1>, represents the destination terminal device address as an indirect address.
  • ⁇ Source>/ ⁇ LocURI> is the international mobile device identifier IMEI of the source terminal device
  • ⁇ Target>/ ⁇ LocURI> is directly Address, which is the address information of the DM server.
  • ⁇ 8 1108 ⁇ > message body container, ⁇ Exec>/ ⁇ Item>/ ⁇ Target> is an executable command node, indicating upload, and Indirect address information, that is, the destination terminal device IMSI. Therefore, the command program can be used to notify the DM server that the shared data uploaded to the DM server is forwarded to the destination terminal device.
  • ⁇ Exec>/ ⁇ Upload> ⁇ Target>/ ⁇ Indirect>/ ⁇ LoclI I> is used together to indicate that the shared data is to be uploaded to the destination terminal device; and if the destination terminal device is to be downloaded from the source terminal device, For data, ⁇ Exec>/ ⁇ Download> should be used together with ⁇ 8011 ⁇ >/ ⁇ 1]1(1 601;>/ ⁇ 0001 ⁇ >.
  • the terminal device information of the source terminal device or the destination terminal device participating in the data sharing may be an International Mobile Station Equipment Identity (IMEI) of the terminal device, or may be an International Mobile Subscriber Identity (IMSI) of the user to which the terminal device belongs. ).
  • IMEI International Mobile Station Equipment Identity
  • IMSI International Mobile Subscriber Identity
  • the DM server needs to authenticate whether the source terminal device can share the shared data to the destination terminal device, and the authentication process is:
  • the DM server reads a list of destination terminal device identifiers set in the source terminal device (which may be an IMSI list of the destination terminal device);
  • the source terminal device is allowed to share the shared data to the destination terminal device.
  • the DM server also needs to authenticate whether the destination terminal device can share the shared data provided by the source terminal device, and the authentication process is:
  • a source terminal device identifier list (which may be an IMSI list of the source terminal device) of the provider of the shared data that can be written to the destination terminal device in the destination terminal device;
  • the DM server reads the source terminal device identifier list set in the destination terminal device (source terminal) The IMSI list of devices);
  • the destination terminal device is allowed to share the shared number provided by the source terminal device.
  • the DM server needs to perform authentication authentication on both the transmitting and receiving sides of the shared data respectively; in step S01, the DM server needs to authenticate whether the source terminal device allows the shared data to be sent to the destination terminal device, and the authentication is performed. The process is to see if the IMSI of the destination terminal device is in the ⁇ Read Allowed> list of the shared subtree stored by the source terminal device. Similarly, in step S03, the DM server needs to authenticate whether the destination terminal device is allowed to receive the shared data from the source terminal device, and the authentication process is to see whether the IMSI of the source terminal device is in the shared subtree stored by the destination terminal device. ⁇ ' ⁇ Allowed> (Allow write) in the ⁇ 1 ⁇ 1> list.
  • Fig. 5 is a schematic diagram showing the process of authenticating a terminal device by a DM server in the present invention, with reference to Fig. 5.
  • the specific processing of its authentication is as follows:
  • Step S11 the DM server notifies the terminal device through the Notification message, requesting to establish a connection;
  • Step S12 The terminal device responds to the request, and establishes an initial connection with the DM server (processed by the DM Agent agent in the terminal device);
  • Step S13 The DM server queries the terminal device for the read and write permission information set in the shared subtree stored by the terminal device.
  • the following command can be used to query the permission permission information set in the shared subtree stored by the terminal device:
  • Step S14 The DM Agent in the terminal device feeds back the read and write permission information stored in the subtree to the DM server.
  • the following command can be used to feedback the read permission information stored in the shared subtree to the DM server:
  • Step S15 The DM server determines, according to the obtained read/write permission information of the terminal device, whether the IMSI of the shared data receiver is in the list of permitted read data of the shared data sender, if yes, indicating The receiving party can obtain the shared data from the terminal device. (Similarly, the DM server can also determine whether the IMSI of the shared data sender is allowed to write in the shared data receiver according to the read and write permission information allowed by the obtained terminal device. ⁇ 1- Allowed ⁇ ⁇ IMSI> in the list, if it indicates that the sender can share data to the receiver), the DM server can continue forwarding operations; otherwise, the DM server will not be able to obtain shared data from the sender;
  • Step S16 The DM server sends an authentication pass information to the user through a UI (User Interface) interface;
  • UI User Interface
  • Step S17 the user confirms, accepts the request
  • step S18 the user responds to the confirmation message to the DM server.
  • the process in which the source terminal device reports the shared data to the DM server in the foregoing step S2 can be implemented in two ways, as follows:
  • FIG. 6 is a schematic diagram of a first implementation process of reporting shared data from a source terminal device to a DM server according to the present invention. Referring to FIG. 6, the specific implementation process is as follows:
  • Step S21 The DM server sends a request message for requesting the source terminal device to report the shared data to the source terminal device, that is, the DM server requests the source terminal device to use the Get command.
  • Step S22 The source terminal device reports the shared data to the DM server in response to the received request message, that is, the source terminal device returns the shared data to the DM server by using the Results command.
  • FIG. 7 is a schematic diagram of a second implementation process of reporting shared data from a source terminal device to a DM server according to the present invention. Referring to FIG. 7, the specific implementation process is as follows:
  • Step S31 setting an active upload executable command in the source terminal device (such as an executable command Upload in the shared subtree stored in the terminal device); the source terminal device shares the data by running an active upload executable command uploaded by itself. Reported to the DM server;
  • Step S32 After receiving the shared data reported by the source terminal device, the DM server feeds back the successful receiving message to the source terminal device.
  • the process of forwarding the shared data to the destination terminal device by the DM server in the above step S4 can also be implemented in two ways, as follows:
  • FIG. 8 is a schematic diagram of a first implementation process of the DM server transmitting the shared data to the destination terminal device in the present invention. Referring to FIG. 8, the specific implementation process is as follows:
  • Step S41 The DM server directly delivers the shared data to the destination terminal device by using the Replace command.
  • Step S42 After receiving the shared data, the destination terminal device feeds back the successfully received message to the DM server.
  • FIG. 9 is a schematic diagram of a second implementation process of the DM server transmitting the shared data to the destination terminal device in the present invention. Referring to FIG. 9, the specific implementation process is as follows:
  • Step S51 setting an active download executable command (such as an executable command Download in the shared subtree stored in the terminal device) in the destination terminal device; the destination terminal device downloads the executable command to the DM server by running the set active download command Request to download shared data;
  • an active download executable command such as an executable command Download in the shared subtree stored in the terminal device
  • Step S52 The DM server sends the shared data to the destination terminal device in response to the received request.
  • Data parsing can be done in the following ways: (1) DM server resolution
  • the DM server obtains the shared data from the source terminal device, parses the shared data according to the manufacturer model and the data type description of the source terminal device, and converts the shared data into a destination terminal device according to the manufacturer model of the destination terminal device. data.
  • the destination terminal device parses the received shared data, which may be completed by the DM Agent, or the user may organize the usage data.
  • the DM server can set a policy for saving and deleting shared data, as follows:
  • the DM server obtains the shared data from the source terminal device, saves the acquired shared data, and then delivers the shared data to the destination terminal device.
  • the DM server does not store the shared data, but provides a channel from the source terminal device to the destination terminal device.
  • the DM server receives the shared data from the source terminal device and delivers the shared data to the destination terminal device.
  • the DM server delivers the shared data to the destination terminal device, the saved shared data is deleted to avoid wasting storage space.
  • the DM server delivers the shared data to the corresponding destination terminal device, the saved shared data is not deleted, and the uploader is marked for the shared data.
  • the DM server does not need to re-source from the source. The terminal device requests to share the data, and directly sends the saved shared data to the destination terminal device.
  • the user can put the data information on the terminal device into its own sharer. The tree is then uploaded to the DM server for storage. When the data on the terminal device is damaged or lost, or the user replaces the terminal device, the previously saved data information can be downloaded from the DM server, thus realizing the backup and recovery of the data.
  • users can be more The terminal equipment is changed, and is not limited to replacing the terminal equipment of the same brand, and may be terminal equipment of different brands and different models.
  • the user can set ⁇ 1 ⁇ 11( ⁇ 6(1> and ⁇ 1 ⁇ &(1 Allowed>) in the shared subtree as their own, which is equivalent to Only the data information is shared with itself, thus avoiding the danger of others stealing data information.
  • the user can delete the data information stored in the shared subtree to save storage on the terminal device.
  • the DM server needs to associate the data information uploaded by the user with the IMSI of the user to which the terminal device uploading the data information, and store it in the form of a directory, so that the user can download from the DM server when the user downloads and restores. Get the backup data information in this storage directory.
  • FIG. 10 is a schematic diagram of a main implementation process for implementing data information backup and recovery processing by relaying and forwarding backup data information through a DM server according to the present invention.
  • the main implementation process is as follows:
  • Step S61 The original terminal device reports the data information of the original terminal device to the DM server for backup processing; wherein the process of reporting the data information to the DM server may also be performed in two ways:
  • the first type is a request message for the DM server to request the original terminal device to report the data information of the pre-backup to the original terminal device;
  • the original terminal device then reports the pre-backed data information to the DM server in response to the received request message.
  • the second method is to set an active upload executable command in the original terminal device (that is, an executable command Upload in the shared subtree stored in the terminal device);
  • the original terminal device reports the pre-backup data information to the DM server by running the active upload executable command Upload.
  • step S62 when the original terminal device loses or destroys data information, or when the user replaces the terminal device (not limited to replacing different brands and different types of terminal devices), the original terminal device or the updated terminal device may back up the DM server.
  • the data information is further restored to the local device of the terminal device; the process of restoring the backed up data information from the DM server to the local device can also be implemented in the following two ways:
  • the first type is that the DM server directly sends the backed up data information to the original terminal device or the updated terminal device.
  • the second method is to set an active download executable command in the original terminal device or the update terminal device (such as the executable command Download in the shared subtree stored in the terminal device);
  • the original terminal device or the updated terminal device requests the DM server to download the backed up data information by running an active download executable command (Download) set by itself;
  • the DM server delivers the backup data information to the original terminal device or the update terminal device in response to the received request.
  • the DM server may associate the backup data information reported by the original terminal device with the user identification information of the user to which the original terminal device belongs, such as the IMSI of the user, etc., so that the subsequent backup data information recovery processing may be performed according to the original terminal.
  • the device or the user identification information of the user to which the terminal device belongs searches for the corresponding backup data information, thereby improving the convenience and efficiency for the DM server to find the corresponding backup data information according to the request of the terminal device.
  • FIG. 11 is a schematic diagram of a specific implementation process of a data backup and recovery method based on device management according to the present invention. Referring to FIG. 11, the specific implementation process is as follows:
  • Step S71 a connection establishment phase between the original terminal device and the DM server is performed according to a Setup Phase stage of the OMA DM standard;
  • Step S72 The original terminal device uploads the pre-backed data information to the DM server; for example, the following command may be used for uploading:
  • Step S73 the DM server saves the backup data information reported by the original terminal device.
  • Step S74 the DM server responds to the original terminal device with a successful receiving message.
  • Step S75 When the original terminal device appears to lose or damage its own data, the original terminal device sends the original terminal device to the DM server. Sending a request for requesting the DM server to deliver backup data information For example, you can use the following command to request the DM server to deliver the backup data information: ⁇ Exec> ⁇ Item>
  • Step S76 The DM server responds to the received request message, searches for corresponding backup data information, and returns to the original terminal device.
  • Step S77 The DM server deletes the downloaded backup data information to save storage space; or deletes the backup data information for the next recovery use (this step is optional).
  • FIG. 12 is a schematic diagram of a processing procedure of a data backup and recovery method based on device management applied to a terminal device when a user replaces a terminal device. Referring to FIG. 12, the specific implementation process is as follows:
  • Step S81 establishing a connection phase between the terminal device A (ie, the original terminal device) and the DM server, according to a Setup Phase stage of the OMADM standard;
  • Step S82 the terminal device A uploads the pre-backup data information to the DM server (the Upload executable command may be used);
  • Step S83 The DM server saves the received pre-backup data information.
  • Step S84 The DM server returns the successfully received information to the terminal device A.
  • step S85 the user replaces the terminal device A with the terminal device B, and the terminal device B establishes a session connection with the DM server according to the Setup Phase of the OMADM standard.
  • the terminal device B needs to be further authenticated, and the authentication and authentication process can be referred to the foregoing FIG. 5;
  • Step S86 the terminal device B downloads the backed up data information from the DM server (the download executable command may be used);
  • Step S87 The terminal device B saves and restores the downloaded backup data information.
  • Step S88 the terminal device B returns the successful recovery information to the DM server.
  • Step S89 the DM server may delete the downloaded backup data information to save the save. Storage space; you can also not delete the backup data information for the next recovery use (this step is optional).
  • FIG. 13 is a storage location of the shared data by the DM server.
  • the main processing procedure of the address information to realize the sharing of data between the terminal devices is as follows: Referring to FIG. 13, the main processing procedure is as follows:
  • Step S91 The source terminal device participating in the data sharing reports the address information of the location where the shared data is stored to the DM server, where the source terminal device can store the shared data that needs to be shared in any node having a storage function in the network system (including In the source terminal device itself, the address information of the node storing the shared data may be set to the DM server; wherein the address information of the shared data location mentioned herein may be the location where the shared data is stored in the source terminal device.
  • the source terminal device may report the address information of the location where the shared data is stored to the DM server by using the method of actively reporting (executing the Upload command) or receiving the request from the DM server.
  • Step S92 The DM server saves address information of a location where the shared data reported by the source terminal device is stored;
  • Step S93 The DM server sends the address information reported by the source terminal device to the corresponding destination terminal device according to the source terminal device information and the destination terminal device information that participate in the data sharing; wherein the destination terminal device can also actively request the DM server to download. (Execute the Download command) or directly accept the DM server to download the address information stored in the DM server;
  • Step S95 The destination terminal device returns the successfully received information to the DM server.
  • Step S96 The destination terminal device obtains the shared data provided by the source terminal device by accessing the location where the shared data is stored according to the obtained address information. a network transmission protocol (such as TCP/IP protocol, etc.), and accessing the location where the shared data is stored according to the address information of the location where the shared data is stored (the address information can be the URI information of the location where the shared data is stored in the source terminal device) Achieve the purpose of obtaining shared data.
  • the user to which the source terminal device belongs may further set a key for obtaining the address information in the DM server, and notify the user to which the destination terminal device belongs, and the key information set by the user and the user of the user.
  • the IMSI corresponds to the storage; if the DM server sends the address information to the corresponding destination terminal device, the user to which the destination terminal device belongs is required to input the key for obtaining the address information; if the user inputs the key correctly, the address is obtained.
  • the information is sent to the destination terminal device, thereby achieving the purpose of securely sharing data.
  • the present invention also proposes a scheme for realizing data backup and recovery by relaying and forwarding the address information of the location where the backup data information is stored by the DM server
  • FIG. 14 is an address of the location where the backup data information is relayed and forwarded by the DM server according to the present invention.
  • the main processing procedure of the data backup and recovery is as follows: Referring to FIG. 14, the main implementation process is as follows: Step S101: The original terminal device reports the address information of the backup location of the data information that is owned by the original terminal device to the DM server for storage; The device can also report the address information of the location where the backup data information is stored to the DM server by means of the active report (executing the upload command) or receiving the request from the DM server. The location of the backup data information mentioned here is stored.
  • the address information may be general resource locator (UI) information, etc., where the backup data information is stored.
  • UI general resource locator
  • Step S102 the DM server stores the address information of the location where the backup data information reported by the original terminal device is stored;
  • Step S103 the DM server returns the successful receiving information to the original terminal device.
  • Step S104 When the backup data recovery is required, the original terminal device (or the updated terminal device) obtains the address information of the backup location of the data information in the DM server; The original terminal device (or the updated terminal device) may also adopt the method of actively requesting the DM server to download (execute the Download command) or directly accept the DM server to download the address information stored in the DM server; Step S105, the original terminal device (or the update terminal device) returns a successful receiving message to the DM server;
  • Step S106 The original terminal device (or the updated terminal device) accesses the backup location of the data information according to the obtained address information, and further restores the backup data information to the terminal device locally.
  • the original terminal device (or the updated terminal device) can obtain the backup data information by using a network transmission protocol (such as TCP/IP protocol) and accessing the location where the backup data information is stored according to the address information of the location where the backup data information is stored. the goal of.
  • a network transmission protocol such as TCP/IP protocol
  • the user to which the original terminal device belongs may further set a key for obtaining the address information in the DM server; the DM server stores the key information set by the user and the IMSI of the user, so that the DM server sends the address information to the corresponding original.
  • the user of the original terminal device is required to input the key for obtaining the address information; if the user inputs the key correctly, the address information is sent to the original terminal device, thereby implementing the terminal device securely.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne une méthode de partage de données comprenant : des dispositifs terminaux source partageant la liaison amont de données vers le serveur de gestion de dispositif ; le serveur de gestion de dispositif envoie les données partagées de liaison amont par les dispositifs terminaux source en liaison aval vers les dispositifs terminaux de destination correspondants en fonction des informations des dispositifs terminaux source et des dispositifs terminaux de destination. La présente invention concerne également une méthode de récupération de données sauvegardées comprenant : des dispositifs terminaux source ou des dispositifs terminaux mis à jour récupèrent les données sauvegardées dans le serveur de gestion de dispositif et les envoient vers les dispositifs terminaux locaux lorsque les données sauvegardées doivent être récupérées. L’invention peut réaliser différents dispositifs terminaux de partage de données par le serveur DM et peut fournir aux utilisateurs des services plus sûrs et plus fiables.
PCT/CN2006/001432 2005-06-30 2006-06-23 Méthode de partage de données et méthode de récupération de données sauvegardées WO2007003103A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510080259.2 2005-06-30
CN200510080259.2A CN100515112C (zh) 2005-06-30 2005-06-30 数据共享方法及其数据备份恢复方法、及相关设备

Publications (1)

Publication Number Publication Date
WO2007003103A1 true WO2007003103A1 (fr) 2007-01-11

Family

ID=37579000

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001432 WO2007003103A1 (fr) 2005-06-30 2006-06-23 Méthode de partage de données et méthode de récupération de données sauvegardées

Country Status (2)

Country Link
CN (1) CN100515112C (fr)
WO (1) WO2007003103A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107395739A (zh) * 2017-08-11 2017-11-24 安徽晶奇网络科技股份有限公司 一种数据交换共享平台

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101557616B (zh) * 2009-05-19 2011-05-11 杭州华三通信技术有限公司 接入点切换备份接入控制器的方法及接入点和接入控制器
CN101720084A (zh) * 2009-12-18 2010-06-02 中兴通讯股份有限公司 终端数据的处理方法、终端以及系统
CN101790155A (zh) * 2009-12-30 2010-07-28 中兴通讯股份有限公司 一种更新移动终端安全算法的方法、装置及系统
CN102194403A (zh) * 2010-03-17 2011-09-21 上海仰邦软件科技有限公司 基于Microblaze软核技术的LED大屏幕异步控制系统
CN102523282A (zh) * 2011-12-14 2012-06-27 北京百纳威尔科技有限公司 移动终端共享数据的方法、装置及网络服务器
CN102999379B (zh) * 2012-12-14 2015-08-12 东莞宇龙通信科技有限公司 终端和数据共享方法
CN103037007A (zh) * 2012-12-24 2013-04-10 珠海金山办公软件有限公司 基于地理位置服务的数据分享方法及系统
CN104243538A (zh) * 2013-06-24 2014-12-24 腾讯科技（深圳）有限公司 资源分享方法和系统
CN106547646B (zh) * 2015-09-23 2020-06-16 菜鸟智能物流控股有限公司 一种数据备份及恢复方法、数据备份及恢复装置
CN106603650B (zh) * 2016-12-08 2020-08-14 宇龙计算机通信科技(深圳)有限公司 共享位置信息的方法及终端设备
CN107295078A (zh) * 2017-06-19 2017-10-24 山东浪潮通软信息科技有限公司 一种补丁分发跟踪及控制系统及方法
CN107124475A (zh) * 2017-06-30 2017-09-01 江西博瑞彤芸科技有限公司 一种图像数据的共享方法
CN107402848A (zh) * 2017-07-31 2017-11-28 郑州云海信息技术有限公司 一种快照数据一致性的实现方法
CN107395516A (zh) * 2017-09-05 2017-11-24 济南浚达信息技术有限公司 一种基于物联网的互联网数据备份方法
CN112492503A (zh) * 2019-08-20 2021-03-12 普天信息技术有限公司 集群终端定位共享方法、电子设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1510677A (zh) * 2002-12-23 2004-07-07 �ʼҷ����ֵ��ӹɷ����޹�˾ 运用WebDVD技术分享内容的方法
KR20050000829A (ko) * 2003-06-25 2005-01-06 쎄테콤코리아 주식회사 무선 게임기에서의 게임 컨텐츠 공유 방법
EP1542424A1 (fr) * 2003-12-12 2005-06-15 France Telecom Système et procédé de partage de données entre des terminaux WAP

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1510677A (zh) * 2002-12-23 2004-07-07 �ʼҷ����ֵ��ӹɷ����޹�˾ 运用WebDVD技术分享内容的方法
KR20050000829A (ko) * 2003-06-25 2005-01-06 쎄테콤코리아 주식회사 무선 게임기에서의 게임 컨텐츠 공유 방법
EP1542424A1 (fr) * 2003-12-12 2005-06-15 France Telecom Système et procédé de partage de données entre des terminaux WAP

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107395739A (zh) * 2017-08-11 2017-11-24 安徽晶奇网络科技股份有限公司 一种数据交换共享平台

Also Published As

Publication number Publication date
CN100515112C (zh) 2009-07-15
CN1889742A (zh) 2007-01-03

Similar Documents

Publication Publication Date Title
WO2007003103A1 (fr) Méthode de partage de données et méthode de récupération de données sauvegardées
US8555064B2 (en) Security system and method for wireless communication system
US8438616B2 (en) Method for terminal configuration and management and terminal device
US7809366B2 (en) Mobile device client
CN112449315B (zh) 一种网络切片的管理方法及相关装置
US11102017B2 (en) Robust event handling in an electronic subscriber identity module (eSIM) notification service
JP2012511268A (ja) 端末機器、端末機器を設定する方法および装置
JP2009500759A (ja) シンプルネットワーク管理プロトコルに基づいたデータ管理のための方法及びシステム
WO2010127508A1 (fr) Procédé et appareil permettant d'effectuer une gestion de dispositif par un dispositif de passerelle et serveur de gestion de dispositif correspondant
WO2010028571A1 (fr) Procédé d’émission de gros objets de données, système d’émission, dispositif émetteur et dispositif récepteur
US20230059030A1 (en) Secure communication method and related apparatus and system
JP2023539038A (ja) 複数個のｅＳＩＭプロファイルを設置及び管理する方法及び装置
CN115989688A (zh) 用于在设备改变故障的情况下恢复简档的方法和装置
KR102059643B1 (ko) 디바이스 관리 방법과 서버, 시스템 및 모바일 장치
JP6476319B2 (ja) 移動無線通信ネットワークに移動端末の接続を確立するための方法、及び無線アクセスネットワーク構成要素
KR20220018897A (ko) 복수 개의 eSIM 프로파일을 설치, 관리하는 방법 및 장치
WO2010124571A1 (fr) Procédé, client et serveur d'acquisition d'informations de noeud
CN101616372A (zh) 实现自动配置无线终端的方法及系统
KR20220018892A (ko) 복수 개의 eSIM 프로파일을 설치, 관리하는 방법 및 장치
KR20220018875A (ko) 복수 개의 eSIM 프로파일을 설치, 관리하는 방법 및 장치
KR20220018882A (ko) 복수 개의 eSIM 프로파일을 설치, 관리하는 방법 및 장치
KR20100021690A (ko) 이동 통신 시스템의 인증과 비계층 프로토콜 보안 운영을 효율적으로 지원하는 관리 방법 및 시스템
WO2022042055A1 (fr) Procédé et système de gestion de découpage de réseau, et support d'enregistrement lisible par ordinateur
WO2024001889A1 (fr) Procédé et dispositif de demande de politique v2x
KR101148889B1 (ko) 자체보안기능을 구비한 모바일터미널 및 이의 보안강화방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06761314

Country of ref document: EP

Kind code of ref document: A1