EP1680746B1 - Protocole de transfert de fichiers pour ordinateur mobile - Google Patents

Protocole de transfert de fichiers pour ordinateur mobile Download PDF

Info

Publication number
EP1680746B1
EP1680746B1 EP04795208A EP04795208A EP1680746B1 EP 1680746 B1 EP1680746 B1 EP 1680746B1 EP 04795208 A EP04795208 A EP 04795208A EP 04795208 A EP04795208 A EP 04795208A EP 1680746 B1 EP1680746 B1 EP 1680746B1
Authority
EP
European Patent Office
Prior art keywords
protocol
node
file
operating system
message block
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
EP04795208A
Other languages
German (de)
English (en)
Other versions
EP1680746A4 (fr
EP1680746A2 (fr
Inventor
Jianyu Roy Zheng
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Electronics Inc
Original Assignee
Sony Electronics Inc
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
Priority claimed from US10/962,862 external-priority patent/US7033157B2/en
Application filed by Sony Electronics Inc filed Critical Sony Electronics Inc
Publication of EP1680746A2 publication Critical patent/EP1680746A2/fr
Publication of EP1680746A4 publication Critical patent/EP1680746A4/fr
Application granted granted Critical
Publication of EP1680746B1 publication Critical patent/EP1680746B1/fr
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Definitions

  • the present invention relates generally to computer file sharing and transfers using mobile computers.
  • Computer files can be transferred between computers using one of a variety of protocols, most of which are intended for use with personal computer operating systems (OS).
  • OS personal computer operating systems
  • FTP File Transfer Protocol
  • PCs which essentially is a top level application program that relies on processing and communication layers in a PC OS, enables files to be transferred with security control to do such things as navigate, create, and delete directories, and to copy and delete files, and so on.
  • a more widely used protocol is the server message block (SMB) protocol, which facilitates even more operations including sharing files, serial ports, and printers. SMB can also provide for two levels of security.
  • Bluetooth is intended for wireless environments and which essentially offers the same capabilities as FTP. All of these protocols assume use with a PC OS and require both ends of the transmission (client and server, for instance) to possess communication protocol stacks that match each other.
  • the above protocols are designed with the PC OS in mind, but that other OS such as Palm OS are used in smaller wireless devices such as wireless telephones and personal digital assistants (PDA).
  • PDA personal digital assistants
  • the Palm OS does not have all of the PC OS features that conventional file sharing protocols assume.
  • the Palm OS does not have a conventional file system in its internal memory, which is relatively small.
  • US patent application US -A- 2002/0078154 discloses a scheme which provides a WAP (Wireless Application Protocol) chat server which allows users of WAP devices to chat in real time.
  • WAP Wireless Application Protocol
  • a method for communicating using a device having a Palm operating system includes preferentially using server message block (SMB) to communicate with a node, and if use of SMB to communicate with the node is not possible, using file transfer protocol (FTP). If use of FTP is not possible to communicate with the node, Bluetooth is used.
  • SMB server message block
  • FTP file transfer protocol
  • a protocol for communication between the device and a communication node if a protocol for communication between the device and a communication node has not been identified, it is determined whether the node can communicate using a SMB dialect available to the device, and if so, SMB is selected as the communication protocol. If the node cannot communicate using a SMB dialect available to the device, the node is queried with a FTP message and if an appropriate response is received, FTP is selected as the communication protocol. On the other hand, if an appropriate response is not received, identifications of devices are attempted to be gathered using Bluetooth, and if an identification matches the identification of the node, Bluetooth is selected as the communication protocol.
  • a user name can be automatically set to a default name.
  • file sharing between the device and node that entails a read or write may be executed by temporarily copying a file to an internal Palm OS memory of the device, performing the read or write on the file, and then copying the file back to the node to overwrite a previous version of the file at the node.
  • the method can include transferring a file that is not in Palm OS format between the internal memory and the node by wrapping the file in a Palm OS stream in the internal memory and performing a read or a write on the file.
  • the method can include transferring a file between the expansion memory and the node by byte-to-byte copying of the file using a file allocation table (FAT) of the expansion memory.
  • FAT file allocation table
  • the file may be transferred through the internal memory.
  • a system in another embodiment, includes a processor communicating using a protocol stack.
  • the stack can include an application layer having at least two application layer protocols selected from the group including Bluetooth, file transfer protocol (FTP), and server message block (SMB).
  • FTP file transfer protocol
  • SMB server message block
  • a protocol layer is on top of the application layer for selecting which application layer protocol to use to communicate with a node.
  • a Palm OS device has an internal memory, an expansion memory, and a Palm operating system (OS) accessing the memories.
  • Means are provided to the Palm OS for determining whether the node can communicate using a SMB dialect available to the device, and if so, selecting SMB as the communication protocol.
  • Means are also provided to the Palm OS for, if the node cannot communicate using a SMB dialect available to the device, querying the node with a FTP message, and if an appropriate response is received, selecting FTP as the communication protocol.
  • means are provided for, if an appropriate response is not received, gathering identifications of devices using Bluetooth. If an identification matches an identification of the node, Bluetooth is selected.
  • a system is shown, generally designated 10, that includes one or more servers 12 communicating with one or more mobile computing devices 14.
  • the mobile computing device 14 may be a wireless telephone, personal digital assistant (PDA), or other device that uses a non-personal computer (PC) operating system (OS), and in the embodiment shown that uses a Palm OS 16.
  • the OS 16 can access an internal memory 18 and an expansion memory 20 that may be implemented by an expansion memory card.
  • the OS 16 also accesses at least two transceivers 22 for purposes to be shortly disclosed for communicating with the server 12 over a wired or wireless link 24.
  • the transceivers 22 can include modems, 802.11 devices, and Bluetooth infrared (IR) and/or radiofrequency (rf) transceivers.
  • FIG. 2 shows one embodiment of the protocol stack 26 of the present invention, which need not be exactly paired in the server 12.
  • the stack 26 can include an application layer that includes a top-most mFTP layer which functions as described herein over a Bluetooth FTP layer, a SMB layer, and a FTP layer.
  • the Bluetooth FTP layer is on top of a conventional Object Exchange protocol (OBEX) presentation, session, network, and transport layer. Under the OBEX layer in turn can be conventional Bluetooth (radiofrequency) and infrared data link and physical layers.
  • OBEX Object Exchange protocol
  • the data link and physical layer for the SMB layer is a conventional IEEE 802.11 layer
  • the data link and physical layer for the FTP layer is a conventional modem.
  • a conventional Palm OS TCP/IP stack serves as the network and transport layer for both the SMB layer and FTP layer.
  • a net basic input/output system (NetBIOS) layer is provided as a session layer between the SMB layer and Palm OS TCP/IP layer. The logic below is implemented by the cooperation between the mFTP layer, Bluetooth FTP layer, SMB layer with NetBIOS layer, and FTP layer.
  • processor of the computer 14 accesses the OS 16 to undertake the logic shown and discussed below, which may be executed by a processor as a series of computer-executable instructions.
  • the instructions may be contained on a data storage device with a computer readable medium, such as a computer diskette having a computer usable medium with computer readable code elements stored thereon. Or, the instructions may be stored on a DASD array, magnetic tape, conventional hard disk drive, electronic read-only memory, optical storage device, or other appropriate data storage device, such as the internal memory 18.
  • the computer-executable instructions may be lines of compiled C ++ compatible code or JAVA ® .
  • the flow charts herein illustrate the structure of the logic of the present invention as embodied in computer program software.
  • the flow charts illustrate the structures of computer program code elements including logic circuits on an integrated circuit, that function according to this invention.
  • the invention is practiced in its essential embodiment by a machine component that renders the program code elements in a form that instructs a digital processing apparatus (that is, a computer) to perform a sequence of function acts corresponding to those shown.
  • Figure 3 illustrates the logic of the present mFTP. It is to be understood that Figure 3 assumes that a correct user name and password have been input and accepted.
  • SMB SMB, Bluetooth, or FTP
  • FTP desired underlying protocol
  • the logic flows to block 30 to use the specified protocol. Otherwise, the logic flows to decision diamond 32 to determine whether a suitable SMB dialect can be negotiated with the server. If so, SMB is selected as the protocol at block 34, and the user name is automatically set to the default name at block 36. In contrast, if no SMB dialect can be agreed upon, the logic flows to block 38 to query the server using FTP, and then at decision diamond 40 it is determined whether a suitable response has been received. If so, the logic selects FTP as the protocol at block 42. Otherwise, all Bluetooth devices in the proximity of the device are located at block 44 using Bluetooth principles known in the art.
  • SMB SMB, Bluetooth, or FTP
  • decision diamond 46 it is determined whether any device name that is returned as a result of the previous locating step matches the name of the desired file server with which connection is to be made. If not the logic ends at state 48, but otherwise the logic connects to the server using Bluetooth at block 50, and then automatically sets the user name to default at block 36.
  • Figure 4 shows the logic for sharing files between the device and server.
  • Block 52 simply indicates that directories are created, deleted, and navigated and files deleted using the conventional features of the underlying protocol selected as a result of Figure 3 .
  • Decision diamond 54 indicates that if SMB was selected in Figure 3 , reading and writing files may be done conventionally at block 56. However, if FTP or Bluetooth is the selected protocol, the logic proceeds to block 58 to temporarily copy the file to be shared to the local internal Palm OS memory of the device using the underlying file transfer service. A read (or write, as appropriate) is then executed on the temporary version at block 60, and the result is copied back to the appropriate location in the server at block 62 to overwrite the version on the remote server. Running a Palm OS application on the device from the remote server is executed using the read or write file function described above.
  • FIG. 5 shows the file transfer logic.
  • Decision diamond 64 represents a branch in the logic depending on whether the file is to be transferred between the server 12 and the local internal Palm OS memory 18 or between the server and the expansion Palm OS memory 20. In the former case, the logic flows to decision diamond 66 to determine whether the file in question is in Palm OS format, and if it is the logic moves to block 68 to receive the file from the server (for a read) or transfer the file to the server (for a write) using Palm OS principles known in the art. If the file is not in OS format, however, the logic proceeds to block 70 to wrap the file in a Palm OS stream in the internal memory of the Palm OS so that the file can be read or written but not necessarily be directly accessible to an end user of the device.
  • the logic moves from decision diamond 64 to block 72 to transfer the file using the FAT in a byte-to-byte copy, using the Palm OS native internal memory as a transmission medium.
  • FAT file allocation table

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Claims (8)

  1. Procédés de communication utilisant un dispositif (14) possédant un système d'exploitation Palm (16), comportant l'utilisation d'un protocole de bloc de message de serveur pour communiquer avec un noeud (12), et si l'utilisation du protocole de bloc de message de serveur pour communiquer avec le noeud (12) est pas possible, l'utilisation d'un protocole de transfert de fichiers, et si l'utilisation du protocole de transfert de fichiers n'est pas possible pour communiquer avec le noeud (12), l'utilisation du protocole Bluetooth, dans lequel si le protocole de fichiers de transfert ou le protocole Bluetooth est sélectionné en tant que protocole de communication, le partage de fichiers entre le dispositif (14) et le noeud (12) qui entraîne une lecture ou une écriture est exécuté en copiant temporairement un fichier depuis le noeud (12) vers une mémoire de système d'exploitation Palm interne du dispositif (14), en effectuant la lecture ou l'écriture sur le fichier, et ensuite en recopiant le fichier vers le noeud (12) pour écraser une version précédente du fichier dans le noeud (12).
  2. Procédé selon la revendication 1, dans lequel si le protocole pour une communication entre le dispositif (14) et un noeud de communication (12) n'a pas été identifié, déterminer si le noeud (12) peut communiquer en utilisant un dialecte de bloc de message de serveur disponible dans le dispositif (14), et ainsi, sélectionner le protocole de bloc de message de serveur en tant que protocole de communication.
  3. Procédé selon la revendication 2, dans lequel, si le noeud (12) ne peut pas communiquer en utilisant un dialecte de bloc de message de serveur disponible dans le dispositif (14), le noeud (12) est interrogé grâce à un message de protocole de transfert de fichiers et si une réponse appropriée est reçue, le protocole de transfert de fichiers est sélectionné en tant que protocole de communication.
  4. Procédé selon la revendication 3, dans lequel, si une réponse appropriée n'est pas reçue, des identifications du dispositif (14) sont attendues pour être rassemblées en utilisant le protocole Bluetooth, et si une identification correspond à l'identification du noeud (12), le protocole Bluetooth est sélectionné en tant que protocole de communication.
  5. Procédé selon la revendication 1, dans lequel, si le protocole de bloc de message de serveur ou le protocole Bluetooth est sélectionné en tant que protocole de communication, un nom d'utilisateur est automatiquement déterminé comme nom par défaut.
  6. Procédé selon la revendication 1, comportant le transfert d'au moins un fichier non pas dans le format de système d'exploitation Palm entre une mémoire de système d'exploitation Palm interne (18) du dispositif (14) et le noeud (12) en bouclant le fichier dans le flux de système d'exploitation Palm dans la mémoire interne (18) et en effectuant au moins l'une d'une lecture ou d'une écriture sur le fichier.
  7. Procédé selon la revendication 1, comportant le transfert d'au moins un fichier entre une mémoire de système d'exploitation Palm d'extension (20) du dispositif (14) et le noeud (12) par copie octet par octet du fichier en utilisant une table d'allocation de fichiers de la mémoire d'extension (20), le fichier étant transféré par l'intermédiaire d'une mémoire de système d'exploitation Palm interne (18) du dispositif (14).
  8. Dispositif de système d'exploitation Palm (14), comportant :
    au moins une mémoire interne (18) ;
    au moins une mémoire d'extension (20) ;
    au moins un système d'exploitation Palm (16) ayant accès aux mémoires (18, 20) ;
    un moyen pour déterminer si un noeud (12) peut communiquer en utilisant un dialecte de bloc de message de serveur disponible dans le dispositif (14) ;
    un moyen pour sélectionner le protocole de bloc de message de serveur en tant que protocole de communication si le protocole de bloc de message de serveur entre le dispositif (14) et le noeud (12) est possible ;
    un moyen, si le noeud (12) ne peut pas communiquer en utilisant le protocole de bloc de message de serveur disponible dans le dispositif (14), pour interroger le noeud (12) grâce à un message de protocole de transfert de fichiers ;
    un moyen, si une réponse appropriée est reçue, pour sélectionner le protocole de transfert de fichiers en tant que protocole de communication ;
    un moyen, si une réponse appropriée n'est pas reçue, pour rassembler des identifications du dispositif (14) en utilisant le protocole Bluetooth ;
    un moyen, si une identification correspond à une identification du noeud (12), pour sélectionner le protocole Bluetooth en tant que protocole de communication ; et
    un moyen, si le protocole de transfert de fichiers ou le protocole Bluetooth est sélectionné en tant que protocole de communication, un partage de fichiers entre le dispositif (14) et le noeud (12) qui entraîne une lecture ou une écriture est exécuté en copiant temporairement un fichier du noeud (12) vers une mémoire du système d'exploitation Palm interne du dispositif (14), pour effectuer la lecture ou l'écriture sur le fichier, et ensuite en recopiant le fichier vers le noeud (12) pour écraser une version précédente du fichier dans le noeud (12).
EP04795208A 2003-11-07 2004-10-14 Protocole de transfert de fichiers pour ordinateur mobile Expired - Fee Related EP1680746B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US51828503P 2003-11-07 2003-11-07
US10/962,862 US7033157B2 (en) 2001-12-04 2004-10-12 Process and apparatus for producing a golf ball with deep dimples
PCT/US2004/034014 WO2005048025A2 (fr) 2003-11-07 2004-10-14 Protocole de transfert de fichiers pour ordinateur mobile

Publications (3)

Publication Number Publication Date
EP1680746A2 EP1680746A2 (fr) 2006-07-19
EP1680746A4 EP1680746A4 (fr) 2006-10-25
EP1680746B1 true EP1680746B1 (fr) 2009-03-25

Family

ID=34594902

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04795208A Expired - Fee Related EP1680746B1 (fr) 2003-11-07 2004-10-14 Protocole de transfert de fichiers pour ordinateur mobile

Country Status (4)

Country Link
EP (1) EP1680746B1 (fr)
JP (1) JP2007512593A (fr)
KR (1) KR20060111492A (fr)
WO (1) WO2005048025A2 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006333433A (ja) 2005-05-25 2006-12-07 Microsoft Corp データ通信プロトコル
CN100455085C (zh) * 2006-02-15 2009-01-21 华为技术有限公司 进行点到点的文件传输的用户终端及其传输方法
ES2471415T3 (es) * 2006-07-24 2014-06-26 Agfa Healthcare Procedimiento para establecer una conexión de datos entre aparatos m�dicos y un sistema inform�tico
US9331955B2 (en) 2011-06-29 2016-05-03 Microsoft Technology Licensing, Llc Transporting operations of arbitrary size over remote direct memory access
US20130067095A1 (en) 2011-09-09 2013-03-14 Microsoft Corporation Smb2 scaleout

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6292657B1 (en) * 1998-07-13 2001-09-18 Openwave Systems Inc. Method and architecture for managing a fleet of mobile stations over wireless data networks
US6594762B1 (en) * 1999-05-05 2003-07-15 Ericsson Inc. Methods and devices enabling displays of electronic devices based on separation thereof
AU2001290591A1 (en) * 2000-09-01 2002-03-13 Ikimbo, Inc. System and method for transferring files
US20020078154A1 (en) * 2000-12-19 2002-06-20 Safia Djennane WAP/IRC based instant collaboration tool
US7117266B2 (en) * 2001-07-17 2006-10-03 Bea Systems, Inc. Method for providing user-apparent consistency in a wireless device
AU2002343424A1 (en) * 2001-09-28 2003-04-14 Bluesocket, Inc. Method and system for managing data traffic in wireless networks

Also Published As

Publication number Publication date
EP1680746A4 (fr) 2006-10-25
EP1680746A2 (fr) 2006-07-19
WO2005048025A2 (fr) 2005-05-26
KR20060111492A (ko) 2006-10-27
JP2007512593A (ja) 2007-05-17
WO2005048025A3 (fr) 2006-03-09

Similar Documents

Publication Publication Date Title
US8166193B2 (en) File transfer protocol for mobile computer
US7673020B2 (en) System and method for facilitating communication between a computing device and multiple categories of media devices
JP3574017B2 (ja) サーバ、クライアント、適応同期方法、データ変換方法およびプログラム記憶媒体
US6920455B1 (en) Mechanism and method for managing service-specified data in a profile service
US20060085574A1 (en) Methods for accessing remotely located devices
EP1333378A2 (fr) Système et méthode pour fournir des informations de contexte
JP2008511881A (ja) インスタントメッセージングプラットフォームに基づきオンラインファイルストレージを実現する通信システム及び方法
US20010042212A1 (en) Smart card enabled mobile personal computing environment system
US20100005153A1 (en) Use of wireless devices' external storage
EP1872252A1 (fr) Systeme et procede de synchronisation de fichiers poste a poste
IL170667A (en) System and method for determining target failback and target priority for a distributed file system
JP2004280826A (ja) プロトコル独立型クライアント側キャッシュ（ｐｒｏｔｏｃｏｌ−ｉｎｄｅｐｅｎｄｅｎｔｃｌｉｅｎｔ−ｓｉｄｅｃａｃｈｉｎｇ）システムおよび方法
US7660875B2 (en) Bidirectional remote communication via browser plug-in
JP2004533039A (ja) ネットワークにおけるファイル共有の方法およびシステム
US8627446B1 (en) Federating data between groups of servers
EP2025121A2 (fr) Téléphone mobile utilisé dans un système de serveur client
US8380806B2 (en) System and method for absolute path discovery by a storage virtualization system
EP1680746B1 (fr) Protocole de transfert de fichiers pour ordinateur mobile
JP2000076152A (ja) 分散ファイルシステムならびに同システムにおけるファイル共有方法及び同方法がプログラムされ記録される記録媒体
JP2007317107A (ja) 情報処理システム、及び情報処理装置、並びに制御プログラム
JP3872965B2 (ja) ファイル転送システム、サーバ装置、ファイル転送方法、ファイル転送プログラム
KR20040084372A (ko) 네트워크를 이용한 파일관리 방법
JP2002215497A (ja) インターネット接続装置及びインターネット接続方法及びプログラム
JP2000298612A (ja) オンラインデータ転送装置
KR100492379B1 (ko) 무선단말기를 이용한 데이터의 관리방법 및데이터관리시스템

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060327

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

A4 Supplementary search report drawn up and despatched

Effective date: 20060926

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20070122

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602004020249

Country of ref document: DE

Date of ref document: 20090507

Kind code of ref document: P

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20091229

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20100630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100501

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091102

REG Reference to a national code

Ref country code: GB

Ref legal event code: S28

Free format text: APPLICATION FILED

REG Reference to a national code

Ref country code: FR

Ref legal event code: RN

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20091014

REG Reference to a national code

Ref country code: FR

Ref legal event code: FC

PGRI Patent reinstated in contracting state [announced from national office to epo]

Ref country code: DE

Effective date: 20101124

REG Reference to a national code

Ref country code: GB

Ref legal event code: S28

Free format text: RESTORATION ALLOWED

Effective date: 20110406

PGRI Patent reinstated in contracting state [announced from national office to epo]

Ref country code: FR

Effective date: 20110112

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20141029

Year of fee payment: 11

Ref country code: FR

Payment date: 20141017

Year of fee payment: 11

Ref country code: GB

Payment date: 20141027

Year of fee payment: 11

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602004020249

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20151014

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151014

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20160630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151102

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160503