WO2006122486A1 - Procede de mise a jour et de retour en arriere de donnees de dispositifs terminaux - Google Patents

Procede de mise a jour et de retour en arriere de donnees de dispositifs terminaux Download PDF

Info

Publication number
WO2006122486A1
WO2006122486A1 PCT/CN2006/000963 CN2006000963W WO2006122486A1 WO 2006122486 A1 WO2006122486 A1 WO 2006122486A1 CN 2006000963 W CN2006000963 W CN 2006000963W WO 2006122486 A1 WO2006122486 A1 WO 2006122486A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
terminal device
node
backup
updated
Prior art date
Application number
PCT/CN2006/000963
Other languages
English (en)
Chinese (zh)
Inventor
Jie Tang
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 WO2006122486A1 publication Critical patent/WO2006122486A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • H04W8/245Transfer of terminal data from a network towards a terminal

Definitions

  • the present invention relates to the field of communications and information technology, and more particularly to a method of updating and restoring terminal device data. Background technique
  • Mobile terminal equipment is an important part of the entire mobile operation service system. As the functionality of terminal devices becomes more complex, the likelihood of problems with the terminal device software increases significantly. How to quickly and effectively solve problems in the terminal, improve service quality, and reduce operating costs of system equipment has become a concern of terminal equipment manufacturers.
  • the system provides a mechanism for configuring terminal device parameters from the server side and transmitting update packages to the terminal devices to update the terminal device software.
  • OMADM Device Management
  • the current method is to back up the data before the update on the server side, and re-issue the data before the update when a logic error occurs to complete the data recovery.
  • FIG. 1 is a flow chart of data backup and data update signaling in the prior art. Referring to FIG. 2, the process flow is as follows:
  • Step 1 Establish a connection between the server and the terminal device according to the OMA DM standard;
  • Step 2 The server sends a parameter acquisition configuration message according to the data involved in the update;
  • Step 3 The terminal device configures a message according to the acquired parameter, ⁇ Reminder, and upload the corresponding parameter data;
  • Step 4 After receiving the uploaded data, the server backs up the data on the server side.
  • Step 5 The server sends an update package, and the terminal device receives the update operation.
  • Step 6 The terminal device reports the update status.
  • Step 1 According to OMA DM The standard establishes a connection between the server and the terminal device; Step 2: The terminal device informs the server of the parameters that need to be restored by telephone, WEB or other means;
  • Step 3 The server delivers an update package, and the content of the update package is related data backed up before the last update;
  • Step 4 After the terminal device receives the update package, it performs an update operation and completes the recovery.
  • backup data on the server side occupies server resources; since the data is backed up on the server side, and the original data is on the terminal device, it is necessary to upload relevant data before each update, and increase The consumption of network resources is large; and the transmission of data on the mobile network will increase the probability of error.
  • the present invention provides a method for updating terminal device data, so as to solve the problem that the consumption of server resources and network resources is large in the prior art, and that data transmission on the network is error-prone.
  • the present invention also provides a method for recovering data of a terminal device by using the backed up data, which is used to solve the problem that the network resource is consumed in the prior art, and the data is easily error-prone on the network, and the user cannot Recovery, the problem that the server side cannot actively recover.
  • the method for updating terminal device data provided by the present invention includes:
  • the terminal device After receiving the update data, the terminal device backs up the original data that needs to be updated on the terminal device;
  • the updated data is used to overwrite data that needs to be updated on the terminal device.
  • the terminal device manages data by using a tree structure, and manages data by using a database or a data list.
  • a backup node is created in the tree structure before the first backup, and when the backup is performed, the data to be updated is copied to the corresponding node under the backup node.
  • a backup node is created in the tree structure before the data update operation, and the data to be updated is copied to the backup node.
  • the backup node is created under the node where the data to be updated is located.
  • the terminal device After the update operation is completed, the terminal device reports to the area server whether the update operation is successful.
  • a method for restoring data of a terminal device comprising the steps of: determining data that needs to be restored;
  • the restored data is overwritten with the corresponding current data on the terminal device.
  • the device management server Determining the data that needs to be restored by the device management server DM Server and sending a recovery request message to the terminal device, and the terminal device performs a recovery operation after receiving the message; or, the DM Server determines the data to be restored, and the terminal device
  • the recovery data is submitted to the device management server, and the device management server restores the data of the terminal device according to the device management 0MA process of the Open Mobile Alliance; or
  • the recovery operation is triggered directly on the terminal device and the data that needs to be recovered is determined.
  • the recovery request message carries the recovery object information, and is used to notify the terminal device that the data needs to be restored.
  • the terminal device determines whether the recovery is successful, and draws the picture
  • the server sends a recovery status message.
  • the method for updating terminal device data provided by the present invention backs up relevant data in the terminal device before updating the data, and does not need to upload the data, thereby saving server and network resources and reducing the amount of data transmitted by the network.
  • the method for recovering data of the terminal device provided by the present invention, since the data is backed up in the terminal device, the data of the backup is not needed to be recovered during the recovery, thereby saving network resources and reducing the amount of data transmitted by the network; When the problem occurs, the data that can be backed up can be recovered by itself. When the operator finds that there is a problem after updating, the server can actively send a request recovery message to the terminal device to recover the data.
  • FIG. 3 is a flow chart of a method for updating data according to the present invention.
  • FIG. 5 is a schematic diagram of a data structure according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a data structure in accordance with an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a data structure after backup according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a data structure after updating according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a data structure after backup according to the method of the present invention.
  • FIG. 10 is a schematic diagram of a data structure after a backup node is created under a root node according to the present invention
  • FIG. 11 is a schematic diagram of a data structure after a backup node and other nodes except the root node are created according to the present invention
  • FIG. 13 is a signaling flowchart of a method for restoring data provided by the present invention. detailed description
  • the present invention provides a method of updating terminal device data in device management.
  • the data management structure of the terminal device is a tree structure, or uses a database or a data list to compare data. Manage. Now taking the data management structure as a tree structure as an example, the method of the present invention will be described below with reference to examples.
  • Example 1 The update process is initiated by the terminal device, and different versions of the data to be updated are backed up under the same ⁇ node.
  • FIG. 3 is a flowchart of a method according to the present invention.
  • FIG. 4 is a signaling flowchart of a method according to the present invention. Referring to FIG. 3 and FIG. 4, the method includes the following specific steps: S11, a terminal device, and a device management server. (DM Server) establishes a connection.
  • DM Server DM Server
  • the user terminal device sends a connection establishment request message to the DM server, and after receiving the message, the DM server sends a response message to the user terminal device to complete the connection between the user terminal device and the DM server.
  • the terminal device sends a data configuration request message to the DM server.
  • the terminal device constructs a data configuration request message according to the data content updated by the user and the path of the node where the data is located. And sending, by the terminal device, the data configuration request message to the DM server, to notify the DM server of the update data, and configuring the DM server to perform corresponding configuration according to the path, so that the update is updated. Data can be automatically copied to the corresponding data node.
  • the DM Server sends the update data according to the content of the received data configuration request message.
  • the DM server After receiving the data configuration request message, the DM server obtains the data content that the user wants to update, and the path of the data, and constructs the related data as an update data packet, and sends the data to the user terminal device.
  • Figure 5 shows the data structure before the backup node is created.
  • Figure 6 shows the data structure after the backup node is created.
  • the terminal device configures a data path in the request message according to the sent data, and creates a backup node for storing the data to be updated under the node where the data to be updated on the terminal device is located.
  • the user can determine whether the data to be updated is important, and select whether to back up the data to be updated, which can save time and storage space.
  • the data structure of the data to be updated is backed up. It can be seen from the figure that the data to be backed up according to the household selection will be The backup data is backed up to the backup node, and the data to be updated is backed up on the terminal device to complete the backup work. If you need to update the data under the same node again, the backup node will not be created. Instead, the data to be updated will be directly backed up to the created backup node and the previous data will be overwritten.
  • FIG. 8 is a schematic diagram of the updated data structure. As can be seen from the figure, after the update, the data to be updated is overwritten by the updated data.
  • steps S14 and S15 and step S13 described in this embodiment may be interchanged, or steps S14 and S15 may be performed simultaneously with step S13 as long as the update is to be performed before the start of the update data operation. Backing up data to the terminal device should be within the scope of the present invention.
  • Example 2 The update process is initiated by the terminal device, and different versions of the data to be updated are backed up under different backup nodes.
  • the terminal device establishes a connection with a device management server (DM Server). (same as instance - same content)
  • DM Server device management server
  • the terminal device sends a data configuration request message to the DM server. (same as the example one)
  • the DM Server sends the update data according to the content of the received data configuration request message. (same content as in example one)
  • the terminal device When the backup needs to be backed up, the terminal device creates a backup node with the current data version number under the node where the data to be updated is located, and stores the data of the current backup. Then, if the data under the same node needs to be updated again, Create a backup node with the current data version number and store the data for that backup. This way the data does not overwrite the previous data for maintenance.
  • Back up the data to be updated to the corresponding backup node It is up to the user to determine whether the data to be updated is important before the backup, and whether to back up the data to be updated. After the selection, the data to be updated is backed up to the backup node with the same version number, and the data to be updated is backed up on the terminal device to complete the backup work.
  • steps S24 and S25 and step S23 described in this embodiment may be interchanged, or steps S24 and S25 may be performed simultaneously with step S23, as long as the data to be updated is backed up before the start of the update data operation. It should be within the scope of the present invention to the terminal device.
  • Example 3 The update process is initiated by the terminal device, and the data to be updated is backed up under any node in the tree structure.
  • the terminal device establishes a connection with a device management server (DM Server). (same as example one)
  • DM Server device management server
  • the terminal device sends a data configuration request message to the DM server. (same as the example one)
  • the DM Server sends the update data according to the content of the received data configuration request message. (same content as in example one)
  • the backup node can be created under the root node or under any other node, and the related data can be backed up on the terminal device.
  • step S33 The sequence between steps S34 and S35 and step S33 described in this embodiment may be interchanged, or steps S34 and S35 may be performed simultaneously with step S33, as long as the data to be updated is backed up before the start of the update data operation. It should be within the scope of the present invention to the terminal device.
  • Example 4 The update process is initiated by the terminal device, and the backup tree and backup related data are created.
  • the terminal device establishes a connection with the device management server (DM Server). (same as example one)
  • DM Server device management server
  • the terminal device sends a data configuration request message to the DM server. (same as the example one)
  • the DM Server sends the update data according to the content of the received data configuration request message. (same content as in example one)
  • Figure 11 shows the data structure after the backup node and other nodes except the original root node are created before the first backup.
  • a backup node is created under the root node of the tree data structure on the terminal device, and each node having the same structure as the other nodes under the original root node is created under the backup node. These created nodes are used to store data under their corresponding nodes.
  • the backup node and the backup tree structure under the backup node may also not be created under the original root node, and may be created under any node in the original tree structure.
  • the data to be updated is important before the backup and to choose whether to back up the data to be updated. Because the node structure under the backup node is the same as the data structure under the original root node, the data under the root node is automatically backed up to the corresponding node under the backup node to complete the backup operation. In this step, only the data that needs to be updated can be backed up to the corresponding node under the backup node to save time and space.
  • the process of updating the terminal device data according to the present invention may also be initiated by the DM Server.
  • the DM Server sends the connection to the terminal device.
  • the parameter configuration request message carries a content list that needs to be updated in the parameter configuration request message, so that the terminal device learns the content involved in the current update, and accordingly, the terminal device actively backs up the related data before the update operation starts.
  • the method for actively updating the terminal device data by the DM server may also be implemented by the following process: After the connection between the terminal device and the DM server is established, the parameter configuration request message is not sent, but a creation message is sent.
  • the creation message carries a creation path for informing the terminal device where to create a backup node in the data management structure, for example: creating a backup node under the node where the data to be updated is located; waiting for the terminal device to be created at the corresponding location After the backup node is reported and reported, the DM Server sends a backup message to the terminal device. After receiving the data, the terminal device backs up the corresponding data to the created backup node. After that, the data update process is performed.
  • the present invention uses a database or data list to manage data, a corresponding data management structure is established on the device terminal.
  • the related data and its path are backed up to the database or data list for subsequent operations to find and call.
  • the server side can also initiate the recovery process.
  • the method of the present invention utilizes the data backed up by the above scheme to provide a method for restoring terminal device data in device management. The method of the invention will now be described in three examples.
  • Example 1 The data recovery process initiated by the DM Server.
  • FIG. 12 is a flow chart showing the steps of the method of the present invention.
  • FIG. 13 is a signaling flowchart of the method of the present invention. As can be seen from the above two figures, the method includes the following steps:
  • the device management server establishes a connection with the terminal device.
  • the DM Server sends a connection establishment request message to the user terminal device, and after receiving the message, the user terminal device sends a response message to the DM Server to complete the connection between the DM Server and the user terminal device.
  • the device management server sends a recovery request message to the terminal device.
  • the DM Server After the connection is established, the DM Server initiates the recovery process.
  • the data content corresponding to the error is carried in the recovery request message to inform the terminal device which data needs to be recovered, according to the update error that the operator has confirmed.
  • the recovery request message is then sent to the user terminal device.
  • the terminal device After receiving the recovery request message, the terminal device determines, according to the content in the message, the data that needs to be restored, and searches for and extracts the backup data corresponding thereto, if the manner of creating different backup nodes for different versions of data is adopted. , the user can choose which version of the data to restore.
  • the original path of the data is the upper node of the backup node; if the backup tree is used, Or the method of creating a backup node under any node, as shown in FIG. 10 and FIG. 11, the original path of the data is the path of the node where the original data needs to be restored under the original root node.
  • the current data is overwritten with the extracted backup data to complete the recovery operation.
  • the terminal device determines whether the recovery is successful. After the judgment result is obtained, the terminal device sends a recovery situation message to the DM server, where the recovery situation message carries a code for identifying the recovery situation, for example: 1 represents recovery success, 2 represents recovery failure, and 3 represents no corresponding recovery data. .
  • the DM Server obtains and parses the code, and then determines whether it is necessary to initiate the recovery process again. If the code DM Server according to the recovery situation confirms that the recovery process does not need to be initiated again, a deletion message is sent to the terminal device, and the terminal device is notified to delete the backed up data. After the results show that the recovery is successful, the terminal device can also actively delete the backup data to save storage space. Of course, after the recovery is successful, the backup data may not be deleted for subsequent processes.
  • Example 2 The user recovers the data autonomously.
  • Example 3 Upload the backup data and then deliver it.
  • the device management server establishes a connection with the terminal device. (same content as in Example 1)
  • the DM Server extracts corresponding data and its path from the terminal device according to the data content that needs to be restored.
  • the data is packaged and sent to the terminal device.
  • the terminal device overwrites the current data with the data in the data packet.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé de mise à jour et de retour en arrière des données d'un dispositif terminal. Le procédé comprend la sauvegarde des données devant être mises à jour avant que le dispositif terminal effectue l'opération de mise à jour de manière à résoudre le problème dans l'état antérieur de la technique d'une consommation importante de ressources de serveur et de réseau et permet également d'éviter le problème d'une transmission de données aisément défectueuse. Avec le procédé de la présente invention, il n'est pas nécessaire de transmettre les données de sauvegarde pendant le retour en arrière, ce qui permet d'économiser des ressources de réseau et de réduire la quantité de données transmises par le réseau. Si des utilisateurs découvrent des erreurs après la mise à jour, ils peuvent retrouver les données de sauvegarde et effectuer le retour en arrière par eux-mêmes. Et si des opérateurs trouvent des erreurs après la mise à jour, ils peuvent envoyer une requête de retour en arrière depuis le serveur au dispositif terminal et effectuer le retour en arrière des données.
PCT/CN2006/000963 2005-05-19 2006-05-15 Procede de mise a jour et de retour en arriere de donnees de dispositifs terminaux WO2006122486A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2005100709610A CN100450015C (zh) 2005-05-19 2005-05-19 在设备管理中更新和恢复终端设备数据的方法及终端设备
CN200510070961.0 2005-05-19

Publications (1)

Publication Number Publication Date
WO2006122486A1 true WO2006122486A1 (fr) 2006-11-23

Family

ID=37425745

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/000963 WO2006122486A1 (fr) 2005-05-19 2006-05-15 Procede de mise a jour et de retour en arriere de donnees de dispositifs terminaux

Country Status (2)

Country Link
CN (1) CN100450015C (fr)
WO (1) WO2006122486A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1976517B (zh) * 2006-11-30 2010-08-11 华为技术有限公司 移动终端
CN101026850A (zh) * 2007-03-09 2007-08-29 华为技术有限公司 移动终端软件自动升级的方法及系统、移动终端和软件管理服务器
US9002787B2 (en) 2009-01-30 2015-04-07 Blackberry Limited Method and apparatus for tracking device management data changes
CN101790156B (zh) * 2009-11-19 2011-10-26 北京邮电大学 基于策略优化的终端软件故障修复方法及装置
CN101771727B (zh) * 2010-02-25 2014-12-17 中兴通讯股份有限公司 一种同步更新设备管理对象信息的方法和装置
CN101917351A (zh) * 2010-03-31 2010-12-15 迈普通信技术股份有限公司 路由器上组播转发方法及转发路由器
CN102281159A (zh) * 2011-09-06 2011-12-14 曙光信息产业(北京)有限公司 集群系统的恢复方法
CN103685176B (zh) * 2012-09-11 2017-03-22 联想(北京)有限公司 终端设备、设备管理服务器以及连接建立方法
CN104901840A (zh) * 2015-07-01 2015-09-09 冯旋宇 路由器的数据更新的方法及路由器
CN106446111B (zh) * 2016-09-14 2020-01-14 Oppo广东移动通信有限公司 一种数据迁移的方法及终端
CN107608859A (zh) * 2017-09-29 2018-01-19 郑州云海信息技术有限公司 存储系统状态监控方法、装置、设备及计算机存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003309485A (ja) * 2002-04-16 2003-10-31 Matsushita Electric Ind Co Ltd ソフトウェア更新装置及びソフトウェア更新方法
WO2004063899A2 (fr) * 2003-01-13 2004-07-29 Bitfone Corporation Combine mobile ayant la capacite de mettre a jour son agent de mise a jour
US20050132351A1 (en) * 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6978453B2 (en) * 2002-10-21 2005-12-20 Bitfone Corporation System with required enhancements to syncML DM environment to support firmware updates
US8250565B2 (en) * 2003-06-27 2012-08-21 Hewlett-Packard Development Company, L.P. System and method for downloading update packages into a mobile handset in a carrier network
US7392512B2 (en) * 2003-09-08 2008-06-24 Microsoft Corporation System and method for automatic conversion from WAP client provisioning XML represented objects to OMA DM tree structure represented objects

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003309485A (ja) * 2002-04-16 2003-10-31 Matsushita Electric Ind Co Ltd ソフトウェア更新装置及びソフトウェア更新方法
WO2004063899A2 (fr) * 2003-01-13 2004-07-29 Bitfone Corporation Combine mobile ayant la capacite de mettre a jour son agent de mise a jour
US20050132351A1 (en) * 2003-12-12 2005-06-16 Randall Roderick K. Updating electronic device software employing rollback

Also Published As

Publication number Publication date
CN1866854A (zh) 2006-11-22
CN100450015C (zh) 2009-01-07

Similar Documents

Publication Publication Date Title
WO2006122486A1 (fr) Procede de mise a jour et de retour en arriere de donnees de dispositifs terminaux
US8495616B2 (en) Method for upgrading communication equipment
CN107547245B (zh) 一种版本升级方法和装置
CN100568854C (zh) 一种保持邻居关系的方法和接口板
CN101888304A (zh) 一种路由设备的升级方法、装置和系统
US20080195693A1 (en) Method and Device for Monitoring and Upgrading Software in Device Management
EP2582089A1 (fr) Système et procédé de mise en uvre d'une configuration automatique d'équipements
CN101883355B (zh) 终端参数的配置方法和系统、终端管理装置
CN101313518A (zh) 通信终端设备管理方法及通信终端和系统
JP2009500759A (ja) シンプルネットワーク管理プロトコルに基づいたデータ管理のための方法及びシステム
WO2011137793A1 (fr) Procédé, appareil et système de réseau pour effectuer une mise à jour à distance de dispositifs zigbee
CN105743948A (zh) 一种网络版本升级的方法及装置
WO2011006328A1 (fr) Système et procédé pour la mise à jour du micrologiciel d'un dispositif, serveur de gestion de dispositifs et terminal mobile
CN101651706A (zh) 一种数据发送和接收方法以及系统和装置
CN101980484B (zh) 一种实现路由器全保护的方法及系统
CN111786893A (zh) mesh组网中无线路由器软件版本的同步方法和装置
WO2016065853A1 (fr) Procédé et dispositif d'auto-rétablissement après déconnexion d'une station de base
WO2012155630A1 (fr) Procédé, dispositif et système pour reprise après sinistre
CN111371680B (zh) 双机热备的路由管理方法、装置、设备及存储介质
CN102143604A (zh) 实现无线接入点控制和配置隧道恢复的方法、系统及装置
CN106411574B (zh) 一种管理控制方法和装置
JP2003337717A (ja) オンライントランザクション処理の障害時復旧同期システム
CN102611717A (zh) 一种业务数据发送方法、系统、客户端代理及服务器代理
WO2009079866A1 (fr) Procédé et système srlatifs au processus de mise à niveau de micrologiciel de terminal mobile
CN100488129C (zh) 处理批配置的方法和网管设备及网络系统

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

NENP Non-entry into the national phase

Ref country code: RU

WWW Wipo information: withdrawn in national office

Country of ref document: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06741853

Country of ref document: EP

Kind code of ref document: A1