WO2005059774A1 - A method of maintaining information in a computing device - Google Patents

A method of maintaining information in a computing device Download PDF

Info

Publication number
WO2005059774A1
WO2005059774A1 PCT/GB2004/005270 GB2004005270W WO2005059774A1 WO 2005059774 A1 WO2005059774 A1 WO 2005059774A1 GB 2004005270 W GB2004005270 W GB 2004005270W WO 2005059774 A1 WO2005059774 A1 WO 2005059774A1
Authority
WO
WIPO (PCT)
Prior art keywords
computing device
information
application
contacts
store
Prior art date
Application number
PCT/GB2004/005270
Other languages
French (fr)
Inventor
Britta Kilander
Original Assignee
Symbian Software Limited
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 Symbian Software Limited filed Critical Symbian Software Limited
Publication of WO2005059774A1 publication Critical patent/WO2005059774A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/273—Asynchronous replication or reconciliation

Definitions

  • the present invention relates to a method of maintaining information in computing devices and in particular, to a method of maintaining and, optionally, storing directory information in computing devices.
  • computing device as used herein is to be expansively construed to cover any form of electrical device and includes, data recording devices, such as digital still and movie cameras of any form factor, computers of any type or form, including hand held and personal computers, and communication devices of any form factor, including mobile phones, smart phones, communicators which combine communications, image recording and/or playback, and computing functionality within a single device, and other forms of wireless and wired information devices.
  • data recording devices such as digital still and movie cameras of any form factor
  • computers of any type or form including hand held and personal computers
  • communication devices of any form factor including mobile phones, smart phones, communicators which combine communications, image recording and/or playback, and computing functionality within a single device, and other forms of wireless and wired information devices.
  • Directory information on computing devices such as personal organisers, mobile telephones and computers, is typically kept in some form of contacts store with database-like characteristics, whereby details of individual contacts can be created, retrieved, updated or deleted.
  • personal organisers and mobile telephones usually have bespoke applications which can handle this task.
  • PCs personal computers
  • these devices are more likely to have common application programs for handling contacts information, such as Microsoft OutlookTM or Lotus NotesTM.
  • Contacts information on any of these devices can be input to and updated in the contacts store in a number of different ways.
  • the most basic method is that of direct input by the device user operating on individual contact details through a keypad or other input device, such as a touch screen arranged to display a simulated keypad.
  • Other methods rely on direct electronic input into the contacts store.
  • One straightforward method is the ability to add the addressing information from a specific communication to the contacts store. For example, most electronic mail packages have the ability to add the contact details of the sender of a message received to the local address book, and most mobile phones are able to store the originating numbers of calls received to a local phone book.
  • a more sophisticated method operating on the individual contact level is the ability to receive, and integrate into the contacts store, details held in a standard record format, such as the versit Consortium's vCard format for electronic business cards. Such details can be received directly via personal networking technologies such as infrared or Bluetooth, or can alternatively be received via indirect techniques, such as embedding in electronic mails.
  • Another method can be used by computing devices with the ability to handle standard file formats, such as comma-delimited text records. With this method, an entire file is read into a contacts store, either directly or via a field remapping mechanism.
  • the method of direct owner input limits, in essence, the usefulness of the contacts store to that of an aide memoire; the only information that the owner can input is information that the owner already possess.
  • the methods involving direct electronic input have a more general utility in that they can result in a contacts store which contains information of which the owner was previously unaware as well as information that the owner was simply unable to remember.
  • a method of maintaining contacts information in a computing device comprising providing information indicative of a stored individual contact or a subset of contacts from an application on the computing device to a further application on a remote computing device, and providing one or more further items of information relating to the contact or subset of contacts from the further application to the application on the computing device.
  • a computing device arranged to operate in accordance with a method according to the first aspect.
  • a third aspect of the present invention there is provided computer software arranged to cause a computing device to operate in accordance with a method according to the first aspect.
  • figure 1 illustrates a flowchart of a method for maintaining contacts information in accordance with an embodiment of the present invention.
  • the operation may be considered to be analogous in certain respects to the mechanical step of using a telephone directory or some other publicly available data source to look up, as an example, a telephone number from a known name and also an associated physical address.
  • a user of a requesting computing device sends a request to update or supplement the details of a contact held by that user in a contacts store on the device. This is shown as step 1 in figure 1.
  • the requesting computing device passes sufficient information about the contact from its own contacts store to a contacts store held in a remote application on a remote computing device. This information is preferably such that that the remote application is able to uniquely identify the contact, the additional information required by the requesting user about the contact, and whether the additional information is authorised for release to that particular requesting user.
  • the remote computing device receives the request and checks the details of the request.
  • the remote computing device determines whether the requested information is available from the remote application running on the remote computing device. If the requested information is not available to send to the user making the request, the remote application sends an appropriate message or code to the requesting user to inform that the requested information cannot be provided.
  • the requested information may simply not be available in the remote application because the relevant details have not been inputted.
  • the information held about a contact in the remote application may be present but may only be accessible by selected users and not including the requesting user. The users who may have access may be determined by the contact when that contact requests the posting of his or her details in the remote application.
  • the request is completed.
  • the computing device of the requesting user is passed the additional information as requested, as shown by step 6 of figure 1.
  • the requesting user may be passed an appropriate code by the remote application if a request is determined to be ambiguous or malformed.
  • the present invention may be applied to particular advantage in the area of mobile phones.
  • Contacts information on a mobile phone or on a SIM is often incomplete. For example, there may be a name and mobile phone number for a contact, but no landline, email or street address for that contact.
  • the connection to the wireless network may be relatively slow, unreliable and expensive.
  • the phone itself may have limited memory and processing power. Synchronising an entire database to obtain this information, even if one was available over the wireless air space, would be impractical and uneconomical when only one datum is required. There are no methods or applications currently available with the capability of filling in the blank fields in such a database.
  • the contacts application would reside on a mobile device with the capability of communicating with a networked service run by a mobile phone operator or service provider. When requested, this operator provided service would return the full contact information corresponding to a unique but incomplete set. Typically, provision of a name and mobile phone number would return the corresponding landline and street address and possibly the email address also.
  • the invention could also be used to obtain updated information when a contact store entry becomes out of date (if someone moves, or changes their phone number or email address).
  • the present invention may be implemented using publicly available data. Enhancements are possible and can be provided on the basis of the agreement of each contact.
  • the device could opt to update all contacts entries, or just selected ones. This could be a free service provided for the benefit of all users, or it could be a chargeable service offered by network operators or third parties which would generate revenue.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Databases & Information Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

A contacts database held on a computing device of a user is maintained by the user providing a request to a contacts database held on a remote computing device. The request identifies a particular contact and further information required about that contact. The further information is then selectively downloaded from the remote computing device to the contacts database on the computing device of the user.

Description

A METHOD OF MAINTAINING INFORMATION IN A COMPUTING DEVICE
The present invention relates to a method of maintaining information in computing devices and in particular, to a method of maintaining and, optionally, storing directory information in computing devices.
The term computing device as used herein is to be expansively construed to cover any form of electrical device and includes, data recording devices, such as digital still and movie cameras of any form factor, computers of any type or form, including hand held and personal computers, and communication devices of any form factor, including mobile phones, smart phones, communicators which combine communications, image recording and/or playback, and computing functionality within a single device, and other forms of wireless and wired information devices.
Directory information on computing devices, such as personal organisers, mobile telephones and computers, is typically kept in some form of contacts store with database-like characteristics, whereby details of individual contacts can be created, retrieved, updated or deleted. Personal organisers and mobile telephones usually have bespoke applications which can handle this task. However, because personal computers (PCs) tend to have common operating systems, these devices are more likely to have common application programs for handling contacts information, such as Microsoft Outlook™ or Lotus Notes™.
Contacts information on any of these devices can be input to and updated in the contacts store in a number of different ways. The most basic method is that of direct input by the device user operating on individual contact details through a keypad or other input device, such as a touch screen arranged to display a simulated keypad. Other methods rely on direct electronic input into the contacts store. One straightforward method is the ability to add the addressing information from a specific communication to the contacts store. For example, most electronic mail packages have the ability to add the contact details of the sender of a message received to the local address book, and most mobile phones are able to store the originating numbers of calls received to a local phone book.
A more sophisticated method operating on the individual contact level is the ability to receive, and integrate into the contacts store, details held in a standard record format, such as the versit Consortium's vCard format for electronic business cards. Such details can be received directly via personal networking technologies such as infrared or Bluetooth, or can alternatively be received via indirect techniques, such as embedding in electronic mails.
There are also methods of inputting multiple rather than individual contacts into a store. A common method is to synchronise the contacts store with a similar store held on a local device or on a network. The Open Mobile Alliance is a standards body operating in the wireless arena and, currently, this body has commenced an initiative, known as The Open Mobile Alliance SyncML initiative, which has as an aim to standardise this synchronised input of information in this area. The precise details of such synchronisation processes currently tend to vary from one implementation to another. However,, the effect of all of them is that of a 'bulk update', whereby any missing or altered information is copied from one store to another to effect a bulk update of the information.
Another method, often used for initial population of a contacts store, can be used by computing devices with the ability to handle standard file formats, such as comma-delimited text records. With this method, an entire file is read into a contacts store, either directly or via a field remapping mechanism.
In addition to its relatively slow speed of data input, the method of direct owner input limits, in essence, the usefulness of the contacts store to that of an aide memoire; the only information that the owner can input is information that the owner already possess. In contrast, the methods involving direct electronic input have a more general utility in that they can result in a contacts store which contains information of which the owner was previously unaware as well as information that the owner was simply unable to remember.
However, none of the methods involving direct electronic input is able to retrieve discrete additional items of information on demand when the owner of the contacts store needs them. For instance, an owner of a mobile phone who has the name and mobile phone number of a contact has no way of retrieving the address or landline number of that contact when that owner requires it, even if the owner knows where the information is held. The methods of obtaining details on individual contacts as described above are, therefore, considered unsatisfactory because they cannot be initiated by the owner of the contacts store (they are 'push' rather 'pull' methods for providing information to the owner), whilst the methods of obtaining multiple contacts described above are, in general, considered to be satisfactory because they operate on the entire contents of a contacts store rather than on the basis of individual records within a contacts store. The above limitations mean that owners of computing devices are not able to take full advantage of available databases, whether private or public, to supplement or complete contacts information held in their local store.
Therefore, it is an object of the present invention to provide a method whereby an owner of a contacts store on a device is able to request one or more specific items of additional information relating to a contact in the store from a contacts store held remotely from the device.
According to a first aspect of the present invention there is provided a method of maintaining contacts information in a computing device, the method comprising providing information indicative of a stored individual contact or a subset of contacts from an application on the computing device to a further application on a remote computing device, and providing one or more further items of information relating to the contact or subset of contacts from the further application to the application on the computing device.
According to a second aspect of the present invention there is provided a computing device arranged to operate in accordance with a method according to the first aspect.
According to a third aspect of the present invention there is provided computer software arranged to cause a computing device to operate in accordance with a method according to the first aspect.
An embodiment of the present invention will now be described, by way of further example only, with reference to figure 1 which illustrates a flowchart of a method for maintaining contacts information in accordance with an embodiment of the present invention.
In the following description the information required by a user is assumed to be that needed to complete or supplement known details about a contact. Therefore, the operation may be considered to be analogous in certain respects to the mechanical step of using a telephone directory or some other publicly available data source to look up, as an example, a telephone number from a known name and also an associated physical address.
Referring to figure 1 , a user of a requesting computing device sends a request to update or supplement the details of a contact held by that user in a contacts store on the device. This is shown as step 1 in figure 1. The requesting computing device passes sufficient information about the contact from its own contacts store to a contacts store held in a remote application on a remote computing device. This information is preferably such that that the remote application is able to uniquely identify the contact, the additional information required by the requesting user about the contact, and whether the additional information is authorised for release to that particular requesting user. As shown by steps 2 and 3 of figure 1 , the remote computing device receives the request and checks the details of the request. From step 4 of figure 1 the remote computing device then determines whether the requested information is available from the remote application running on the remote computing device. If the requested information is not available to send to the user making the request, the remote application sends an appropriate message or code to the requesting user to inform that the requested information cannot be provided.
It is envisaged that there may be a variety of reasons why the requested information cannot be provided to the requesting user. For example, the requested information may simply not be available in the remote application because the relevant details have not been inputted. Alternatively, the information held about a contact in the remote application may be present but may only be accessible by selected users and not including the requesting user. The users who may have access may be determined by the contact when that contact requests the posting of his or her details in the remote application.
Hence, if at step 4 it is determined that the remote application is authorised to release the information to the requesting user, the request is completed. When the request completes, the computing device of the requesting user is passed the additional information as requested, as shown by step 6 of figure 1. Although not shown in the flow chart illustrated in figure 1 , it is also possible that the requesting user may be passed an appropriate code by the remote application if a request is determined to be ambiguous or malformed.
The present invention may be applied to particular advantage in the area of mobile phones. Contacts information on a mobile phone or on a SIM is often incomplete. For example, there may be a name and mobile phone number for a contact, but no landline, email or street address for that contact. The connection to the wireless network may be relatively slow, unreliable and expensive. Furthermore, the phone itself may have limited memory and processing power. Synchronising an entire database to obtain this information, even if one was available over the wireless air space, would be impractical and uneconomical when only one datum is required. There are no methods or applications currently available with the capability of filling in the blank fields in such a database.
In this application of the invention, the contacts application would reside on a mobile device with the capability of communicating with a networked service run by a mobile phone operator or service provider. When requested, this operator provided service would return the full contact information corresponding to a unique but incomplete set. Typically, provision of a name and mobile phone number would return the corresponding landline and street address and possibly the email address also. The invention could also be used to obtain updated information when a contact store entry becomes out of date (if someone moves, or changes their phone number or email address).
The present invention may be implemented using publicly available data. Enhancements are possible and can be provided on the basis of the agreement of each contact. The device could opt to update all contacts entries, or just selected ones. This could be a free service provided for the benefit of all users, or it could be a chargeable service offered by network operators or third parties which would generate revenue.
While the description above relates to mobile phones accessing networked services, the invention could be equally useful to fixed computer access directory services over wired networks. Peer-to-peer implementations between users are also possible.
Although the present invention has been described with reference to particular embodiments, it will be appreciated that modifications may be effected whilst remaining within the scope of the present invention as defined by the appended claims.

Claims

Claims: 1. A method of maintaining contacts information in a computing device, the method comprising providing information indicative of a stored individual contact or a subset of contacts from an application on the computing device to a further application on a remote computing device, and providing one or more further items of information relating to the contact or subset of contacts from the further application to the application on the computing device.
2. A method according to claim 1 wherein the application and the further application are arranged respectively to have a client-server relationship.
3. A method according to claim 1 wherein the application and the further application are arranged to have a peer relationship.
4. A method according to any one of claims 1 to 3 wherein the further application is arranged as a public store of contacts information and not to require authorisation for the application to obtain access to the further items of information.
5. A method according to any one of claims 1 to 3 wherein the further application is arranged as a private store of contacts information and to require authorisation for the application to obtain access to the further items of information.
6. A method according to any one of the preceding claims wherein the computing device and the remote computing device are arranged to communicate over a wireless link.
7. A method according to claim 6 wherein the wireless link is arrangeα to comprise any one or more of a cellular phone network, infrared, Bluetooth or a 802.11 WiFi network.
8. A method according to any one of claims 1 to 5 wherein the computing device and the remote computing device are arranged to communicate over a wired link.
9. A method according to claim 8 wherein the wired link is arranged to comprise any one or more of an Ethernet, cable, telephone, or serial link.
10. A method according to any one of claims 6 to 9 wherein a mark-up language is used to provide communication between the computing device and the remote computing device.
11. A method according to claim 10 wherein the mark-up language comprises SyncML.
12. A method according to any one of claims 1 to 7, or claim 10 when appendant to claim 6 or 7, or claim 11, wherein the computing device is selected to comprise a mobile phone.
13. A computing device arranged to operate in accordance with a method as claimed in any one of claims 1 to 11.
14. Computer software arranged to cause a computing device to operate in accordance with a method as claimed in any one of claims 1 to 12.
PCT/GB2004/005270 2003-12-17 2004-12-16 A method of maintaining information in a computing device WO2005059774A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0329279A GB2409298A (en) 2003-12-17 2003-12-17 Updating or adding to a stored contacts data entry
GB0329279.4 2003-12-17

Publications (1)

Publication Number Publication Date
WO2005059774A1 true WO2005059774A1 (en) 2005-06-30

Family

ID=30471256

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2004/005270 WO2005059774A1 (en) 2003-12-17 2004-12-16 A method of maintaining information in a computing device

Country Status (2)

Country Link
GB (1) GB2409298A (en)
WO (1) WO2005059774A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2007200273B2 (en) * 2006-01-25 2012-01-19 Cityland Enterprises Pty Ltd Contact management system
EP2073502B1 (en) 2007-12-21 2013-09-18 Vodafone Holding GmbH Providing communication services at a mobile terminal in dependence of a foreign recipient's contact data
US9178942B1 (en) * 2014-10-17 2015-11-03 ConnectID Limited Systems and methods for updating native contact information

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6418311B1 (en) * 1999-10-27 2002-07-09 Qualcomm, Incorporated Search and replace features for handset phonebook
JP2002262352A (en) * 2001-03-01 2002-09-13 Estore Corp Data management system, data management unit and program
WO2002073992A1 (en) * 2001-03-14 2002-09-19 Telefonaktiebolaget Lm Ericsson (Publ) System and method for updating a phone book in a mobile communication system
US20030022677A1 (en) * 2001-06-21 2003-01-30 Lauri Piikivi Transporting data
JP2003046671A (en) * 2001-08-01 2003-02-14 Nec Corp Method for managing telephone book information of portable terminal
US20030135647A1 (en) * 2002-01-16 2003-07-17 International Business Machines Corporation Web browser control of telephone directories

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2260392C (en) * 1998-01-31 2002-11-19 Kunio Nagashima Communication system capable of displaying addresser information and method for displaying addresser-related information
EP1100282A1 (en) * 1999-11-04 2001-05-16 Motorola Semiconducteurs S.A. Transparent access to remote devices
NO314059B1 (en) * 2000-11-10 2003-01-20 Imp Technology As Procedure for structuring and searching information
DE60224849T2 (en) * 2002-04-30 2009-01-22 Nokia Corp. METHOD AND DEVICE FOR MANAGING TREE DATA EXCHANGE

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6418311B1 (en) * 1999-10-27 2002-07-09 Qualcomm, Incorporated Search and replace features for handset phonebook
JP2002262352A (en) * 2001-03-01 2002-09-13 Estore Corp Data management system, data management unit and program
WO2002073992A1 (en) * 2001-03-14 2002-09-19 Telefonaktiebolaget Lm Ericsson (Publ) System and method for updating a phone book in a mobile communication system
US20030022677A1 (en) * 2001-06-21 2003-01-30 Lauri Piikivi Transporting data
JP2003046671A (en) * 2001-08-01 2003-02-14 Nec Corp Method for managing telephone book information of portable terminal
US20030135647A1 (en) * 2002-01-16 2003-07-17 International Business Machines Corporation Web browser control of telephone directories

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PATENT ABSTRACTS OF JAPAN vol. 2003, no. 01 14 January 2003 (2003-01-14) *
PATENT ABSTRACTS OF JAPAN vol. 2003, no. 06 3 June 2003 (2003-06-03) *

Also Published As

Publication number Publication date
GB0329279D0 (en) 2004-01-21
GB2409298A (en) 2005-06-22

Similar Documents

Publication Publication Date Title
CA2653096C (en) Data synchronization
US9594821B2 (en) Method and apparatus for synchronizing how data is stored in different data stores
CN1998224A (en) Advanced contact identification system
CN1729468B (en) Data synchronization
US20030220966A1 (en) System and method for dynamic content dependent conflict resolution
US6101505A (en) Method of managing files of a portable information terminal according to available memory
US20070250645A1 (en) Mobile phone data backup system
US9020983B2 (en) Address list system and method of implementing an address list
KR20110008334A (en) System and method for a converged network-based address book
CN101808046A (en) Method and system for managing name card information
WO2015089504A1 (en) Systems and methods of address book management
KR20000054371A (en) IMS using PDAs mobile telephone pagers wire and wireless internet and DBMS
US20030140091A1 (en) Telephone number capture from Web page
SG182362A1 (en) System and method for a global directory service
US20050176425A1 (en) Server system, method of transmitting contents, and program
KR100724975B1 (en) An electronic business card service system and method by using presence information
US8184787B2 (en) System and method for generating a personalized bill using a personal address book
KR100570504B1 (en) System And Method For Remote Management Of Personal Contents
WO2005059774A1 (en) A method of maintaining information in a computing device
US20050021867A1 (en) Synchronization arrangement
US20070276962A1 (en) File Synchronisation
KR100925377B1 (en) System for providing open daiary service using contact information list of mobile termianl and method thereof
KR20020008606A (en) Electronic name card exchanging service method
JP2006018390A (en) News information provision method to cellphone or portable terminal
KR20070030516A (en) Method for synchronizing the address book of mobile terminal

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

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