EP1419626B1 - Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant - Google Patents

Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant Download PDF

Info

Publication number
EP1419626B1
EP1419626B1 EP02760317A EP02760317A EP1419626B1 EP 1419626 B1 EP1419626 B1 EP 1419626B1 EP 02760317 A EP02760317 A EP 02760317A EP 02760317 A EP02760317 A EP 02760317A EP 1419626 B1 EP1419626 B1 EP 1419626B1
Authority
EP
European Patent Office
Prior art keywords
architecture
data
software
network
protocol
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 - Lifetime
Application number
EP02760317A
Other languages
German (de)
English (en)
Other versions
EP1419626A2 (fr
Inventor
Rutger H.J. Van Dalen
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.)
Windmill Microsystems Holding BV
Original Assignee
Windmill Microsystems Holding BV
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 Windmill Microsystems Holding BV filed Critical Windmill Microsystems Holding BV
Priority to EP02760317A priority Critical patent/EP1419626B1/fr
Publication of EP1419626A2 publication Critical patent/EP1419626A2/fr
Application granted granted Critical
Publication of EP1419626B1 publication Critical patent/EP1419626B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/026—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using e-messaging for transporting management information, e.g. email, instant messaging or chat
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/222—Monitoring or handling of messages using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
    • 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the invention relates to a method, client apparatus and computer program for directly transferring generic data acquired at a remote location to a central database through a public or private network based on e-mail communication.
  • the invention further relates to a method for remote configuring and management of said apparatus.
  • the invention relates to a method for generic remote data acquisition, TCP/IP protocol stack architecture, application programming interface, apparatus therefor, and a serial communication architecture for configuration of said apparatus.
  • the present invention relates to a method and apparatus of transferring generic data acquired at a remote location to a central database by:
  • the preferred embodiment of the invention is referred to as bf3RDAQ data acquisition method and bf3RDAQ data acquisition client device.
  • the method and apparatus allow development of any remote data acquisition without any limitation on applications or the nature of the data by providing a transparent database interface and modular design architecture approach for said applications.
  • a second aspect of the invention relates to a scalable and modular TCP/IP protocol stack architecture designed for the client-side internet communication of the bf3RDAQ remote data acquisition application, and other applications, which incorporate Intemet-type communication.
  • Such architecture enables the bf3RDAQ data acquisition client application to communicate directly with the bf3RDAQ server.
  • a third aspect of the invention relates to a communication architecture for configuration and maintenance of the data acquisition client application, and other (embedded) applications.
  • a fourth aspect of the invention relates to an e-mail communication method for remote management of the data acquisition client application by the server.
  • a fifth aspect of the invention relates to an HTML based configuration interface which is accessible through the communications interface of the data acquisition client device.
  • the sixth aspect of the invention relates to FTP-based or HTTP-based updating of the data acquisition client software.
  • the first and second item make development of remote data acquisition applications unnecessary expensive, and both may imply a great development risk.
  • the third item makes developing applications which collect data from scattered locations in large areas (e.g. the global inventory or sales sites of a company) extremely difficult, and expensive.
  • the fourth item increases the overall development time of the application, and the limited reuse possibility results in additional cost to the application.
  • EP 1,045,549 describes a method for monitoring and management of distributed networks.
  • the performance data is gathered by a designated served in each network, which sends the accumulated performance data to one or more central servers.
  • the central servers together constitute the supervisory system for monitoring and management of the distributed networks.
  • EP 964,325 describes a method for managing field devices in industrial process systems.
  • a gateway architecture In the method according to EP 1,045,549, for instance, a designated server in the client network assumes the gateway architecture task: it collets the data from the hosts in the client network and transfers the accumulated data to the central server. In the method according to EP 964,325 field devices submit data to a gateway through proprietary or non-Intemet protocols. The gateway processes and formats the data and forwards this data to a central server on behalf of the field devices, which stores the received data in a database.
  • gateway architecture requires extensive development and testing and involves a time-consuming process.
  • TCP/IP protocol stacks for embedded applications are usually based on a model of stacked protocol layers.
  • This model is derived from conventional design concepts used for high-performance processor environments. As such, it is not well suited for embedded applications which are based on processors with limited processing bandwidth and memory resources.
  • the TCP/IP communication architecture of the present invention provides a modular and scalable concept for the development of embedded systems with Internet connectivity.
  • configuration interfaces for embedded applications are generally developed on a per-application basis. Because developing and testing the underlying communication is a time-consuming task, it increases the development risk.
  • the serial communication architecture of the present invention allows development times of configuration interfaces, which are significantly shortened.
  • management of remote systems from a central location is usually implemented with custom applications.
  • the same architecture which is used for the remote data acquisition application can be used for management of the client data acquisition apparatus.
  • the client-server nature of such architecture enables the data acquisition client application to communicate directly with the server.
  • configuration and management of data acquisition clients from a remote device is usually done with custom hardware, software and protocols.
  • an embedded HTTP server web server
  • the configuration and management interface for access from a remote device can be based on TCP/IP communication and be implemented with a standard HTTP client (web browser), such as Microsoft internet Explorer.
  • the updating of software versions from remote locations is usually performed with proprietary bootloader protocols.
  • the software update can be based on TCP/IP communication and be implemented with any FTP-compliant server.
  • the present invention is a system, method and apparatus (consisting of hardware, firmware and software) for transferring generic data acquired by said apparatus from a remote location to a central database.
  • the system of the present invention consists of a central database server, and a number of bf3RADQ data acquisition clients, which can establish communication connections to the server through any network which is capable of accomodating Internet communication.
  • the data acquisition clients process and store the locally acquired data until it needs to be conveyed to the server application.
  • the server application has access to the database.
  • system, method and apparatus according to the invention are suitable for acquiring generic data, without any limitations for application or the nature of the data.
  • An essential feature of the invention is the fact that the bf3RADQ data acquisition clients can establish direct communication connections to the server by using a client-server architecture.
  • the system, method and apparatus according to the invention do not require the use of gateway architecture.
  • Another essential feature of the invention is the use of electronic mail for the encapsulation of the acquired data, and for transferring the encapsulated acquired data to the central server which hosts or connects to the target database.
  • any network which allows internet communication e.g. LAN, WAN
  • Internet Internet
  • the apparatus provides the following functions:
  • the second aspect of the present invention is the architecture on which the client application Internet communication software is based.
  • the bf3Net Internet communication software is based on a design approach which is used in designing hardware signal routing structures.
  • the bf3Net Internet communication architecture (TCP/IP communication architecture) of the present invention is based on a network of multiplexers and demultiplexers controlled by an embedded protocol engine. This architecture has the following advantages:
  • the third aspect of the present invention is the bf3Scp serial communication architecture with which the bf3RDAQ data acquisition client can be configured through the UART serial interface provided by the apparatus of the invention.
  • the chosen architecture has the following advantages:
  • serial communication architecture of the present invention can be used as well.
  • An essential feature of the invention is the use of a target database which contains all the parameters associated with the target application (e.g. timing parameters and message identifiers). By identifying the target application with the following, globally unique, identifiers:
  • the fourth aspect of the invention is a method for indirect configuration of the data acquisition client by the server application.
  • the bf3RDAQ data acquisition client can be configured to retrieve electronic mail messages from its mailbox at the server by means of the POP3 protocol. These messages contain configuration data, which the POP3 client evaluates to adjust their locally stored configuration settings.
  • the same TCP/IP communication architecture that is used for the remote data acquisition application can be used for management of the client data acquisition apparatus.
  • the fifth aspect of the invention is a method for direct configuration of the bf3RDAQ data acquisition client from a remote location.
  • a person or machine can establish an Internet-based communication session based on the TCP/IP communication architecture with the bf3RDAQ client through the network to which both connect.
  • the configuration and status settings can be monitored or adjusted.
  • the sixth aspect of the invention is a method for updating of the data acquisition client software version by downloading a software image from the central server with the FTP or HTTP protocol.
  • the software update can be based on TCP/IP communication and be implemented with any FTP-compliant server.
  • Figures 1, 2 and 3 respectively are illustrations of embodiments of the first, second and third aspect of the invention.
  • Figure 1.A shows two bf3RDAQ data acquisition clients 101 and 102 of the present invention, and the system in which they operate. Both devices have access to a network 106.
  • the system further consists of a bf3RDAQ data acquisition server 103, which connects to a database 105.
  • a bf3RDAQ data acquisition client 101 establishes a connection 107 through the network 106 to the bf3RDAQ data acquisition server 103.
  • a Remote Access Server 104 may be needed (e.g. for modem/ISDN connections) as a router between the server and the clients.
  • FIG. 1B provides more detailed overview of the elements which constitute the bf3RDAQ remote data acquisition system 201 of the present invention.
  • the system consists of the following building blocks:
  • the bf3RDAQ server software module 202 has access to a database 214.
  • the application developer On the client side, to create a custom data acquisition application 213 , the application developer must design the application-specific data acquisition hardware 210 to retrieve data from the data source 212. On the server side, the application developer must design a database application which interacts with database 214.
  • the bf3RDAQ remote data acquisition system of the present invention can further be enhanced by adding the bf3Scp target software module 209 which interacts with a bf3Scp User-Interface application 211 through the bf3RDAQ communication hardware module 206.
  • FIG. 1C A block diagram of an embodiment of a modem bf3RDAQ data acquisition client communication hardware module, according to the present invention, is shown in Figure 1.C. All data and communication processing is performed by the digital signal processor 301.
  • the digital signal processor has access to data memory 303 and program memory 302, and is clocked by a clock device 304.
  • a real-time clock (RTC) 311 serves as time reference.
  • the communication channel of the modem bf3RDAQ data acquisition client communication hardware module consists of a telecommunications line interface (LIF) 308 together with a Direct Access Arrangement (DAA) 307.
  • the receive path further consists of a low-pass filter (LPF) 309 and an analog-to-digital (A-D) converter 310 .
  • the transmit path further consists of a digital-to-analog (D-A) converter 305 and a low-pass filter (LPF) 306 .
  • the line interface circuitry 308 is able to detect an incoming call, and the identifier of the calling party.
  • the bfSRDAQ data acquisition client can selectively act as a receiver.
  • the line interface circuitry 308 also detects if the telephone line is in use prior to establishing a connection or requested during an active connection by another party.
  • the bf3RDAQ data acquisition client can be configured not to interfere with other equipment and to release the line in case of emergency conditions.
  • a Universal Asynchronous Receiver and Transmitter (UART) interface 313 is provided for serial communication.
  • UART Universal Asynchronous Receiver and Transmitter
  • a data acquisition interface 312 is provided.
  • FIG.D An architecture block diagram of the bf3RDAQ data acquisition client software, according to the present invention, is shown in Figure 1.D.
  • the central element of the architecture is the bf3RDAQ Application Programming Interface (API) software module 407. It interfaces with an embedded database 408, which acts as local storage of the data acquired by the client, and of configuration data which controls the operation of the data acquisition client.
  • API Application Programming Interface
  • the bf3RDAQ Application Programming Interface (API) software module 407 further interfaces with the bf3Net Internet Communication software module 402, according to the present invention, through the following Internet application protocol modules:
  • the Simple Mail Transfer Protocol (SMTP) 403 is used to transfer the data acquired by the bf3RDAQ client, encapsulated in an electronic mail message, from the bf3RDAQ data acquisition client embedded database 408 to the bf3RDAQ central database, according to the present invention.
  • SMTP Simple Mail Transfer Protocol
  • the Post Office Protocol Version 3 (POP3) 404 is used to transfer data (e.g. configuration data), encapsulated in an electronic mail message, from the bf3RDAQ central database to the bf3RDAQ data acquisition client embedded database 408.
  • data e.g. configuration data
  • the HyperText Transfer Protocol (HTTP) server 405 is used to provide HTML configuration interfaces which can be accessed through a compliant web browser (e.g. Microsoft Internet Explorer).
  • a compliant web browser e.g. Microsoft Internet Explorer
  • the File Transfer Protocol (FTP) 406 is used to transfer new software versions from the bf3RDAQ Server, according to the present invention, to the bf3RDAQ data acquisition client.
  • the new software version can then be stored in the program memory of the bf3RDAQ data acquisition client, according to the present invention.
  • the bf3Net Internet Communication software module 402 further interfaces with the physical layer communications driver (PHY) 401 which interacts with the communications hardware 409 (e.g. modem or ISDN interface).
  • PHY physical layer communications driver
  • the bf3RDAQ Application Programming Interface (API) software module 407 further provides programming interface functionality to facilitate the design of the custom data acquisition application software 410.
  • FIG. 1E An architecture block diagram of the bf3RDAQ data acquisition server software, according to the present invention, is shown in Figure 1.E.
  • the central element of the architecture is the bf3RDAQ Server software module 505. It interfaces with the central database 506, which acts as the storage of the data acquired by all clients of the data acquisition application system, according to the present invention.
  • the bf3RDAQ Server software module 505 further interfaces with a standard SMTP-and POP3-compliant Internet Mail Server 504, from which it retrieves the acquired data which is sent to the server by a bf3RDAQ data acquisition client, according to the present invention.
  • the internet Mail Server 504 provides dedicated electronic mailboxes with associated electronic mail addresses for the reception of data messages from the bf3RDAQ data acquisition clients.
  • the Internet Mail Server 504 can also be used to send data from the central database 506 to a bf3RDAQ data acquisition client.
  • each bf3RDAQ client in the bf3RDAQ data acquisition application system must have a POP3 mailbox at the Internet Mail Server 504.
  • the internet Mail Server makes use of the Transmission Control Protocol (TCP) 503, the Internet Protocol (IP) 502, and an Internet-compatible datalink 501 (e.g. Ethernet) for communication through the network, according to the present invention.
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • Ethernet Internet-compatible datalink 501
  • a custom database application 507 is the only component that needs to be provided by the application developer to complete the server-side of the bf3RDAQ-based data acquisition application, according to the present invention.
  • Figure 2.A shows the architecture of the bf3Net Embedded internet Communication software, according to the present invention, as a conceptual network of multiplexers and demultiplexers (or mxDmx network, for short), controlled by a protocol engine (bf3Net Engine) 101.
  • bf3Net Engine protocol engine
  • a node in the mxDmx network is either a multiplexer or a protocol module.
  • Each multiplexer has a number of input ports. By making the number of ports statically configurable for each multiplexer, the topology of the mxDmx network can be customized for the application.
  • the bf3Net architecture is subdivided into a number of functional layers. These layers are defined as follows:
  • Layer 0 of the bf3Net architecture is only discussed in general terms in the context of Figure 2.A. Please refer to one of the description of Figures 2.C.and 2.D for the specific details of the datalink layer implementations.
  • the datalink is conceptually depicted as a datalink multiplexer 104 with a number of datalink protocol modules (DL-Px) 105, together with a frame encapsulation module 103.
  • DL-Px datalink protocol modules
  • Layer 1 of the bf3Net architecture consists of the Internet Protocol multiplexer 105, and the application protocol modules which reside at this layer, such as the Internet Control Message Protocol (ICMP) module 111.
  • ICMP Internet Control Message Protocol
  • Layer 2 of the bf3Net architecture consists of the Universal Datagram Protocol (UDP) multiplexer 107, and the Transmission Protocol (TCP) multiplexer 108. Both multiplexers connect to the bf3Net Socket interface module 109, which is also part of Layer 2 of the bf3Net architecture.
  • UDP Universal Datagram Protocol
  • TCP Transmission Protocol
  • the bf3Net socket interface module 109 acts as a cross-connect between the UDP and TCP multiplexers and the application protocol modules 110 (indicated as APP-Py in Figure 2.A).
  • the bf3Net Socket Interface module 109 is part of the bf3Net Application Programming interface 114.
  • Each multiplexer port is identified by a number which is unique for a multiplexer. Which node is connected to which port can also be (statically) configured.
  • the port identifiers at each layer are used to describe a path through the mxDmx network.
  • Such a path descriptor can be an 8-bit or 16-bit value with a field for each functional layer.
  • the path descriptor format is shown in Figure 2.B. For example, the path 113 from the engine to TCP socket 1 is identified as 7-2-1 (or 0xF1) in an 8-bit configuration (3:2:3 bits).
  • Port 0 of every multiplexer in the mxDmx network of the bf3Net architecture (e.g. port 0 112 of the IP multiplexer 106), according to the present invention is reserved and serves as a data sink for incoming data which must be discarded. The reason for this will be explained below.
  • the central element of the bf3Net architecture is the bf3Net Engine 101. It performs the following tasks:
  • the interface between the bf3Net Engine 101 and the mxDmx network is implemented by the datalink multiplexer 104.
  • the bf3Net Engine also interfaces with the Frame Encapsulation module 103 in a similar way.
  • the bf3Net Engine 101 can be seen as a Central Processing Unit (CPU) of the bf3Net software. As such, the bf3Net Engine 101 requires a clock signal to keep it running. This clock signal must be offered externally as a timer tick or an operating system task. The bf3Net Engine 101 is able to (re)schedule itself in the latter case.
  • CPU Central Processing Unit
  • the bf3Net Engine 101 is able to (re)schedule itself in the latter case.
  • the nodes in the mxDmx network interact with the bf3Net Engine 101 by sending messages to the bf3Net Engine 101 through the mxDmx network.
  • the path descriptor is used to identify the originator of the message. The following messages types are defined:
  • the bf3Net Engine 101 processes the messages and responds accordingly.
  • the bf3Net engine 101 has two types of messages it can send upstream through the mxDmx network: routed messages (using a path descriptor), or broadcast messages. Each node in the network is required to pass broadcast messages to all connected upstream nodes, and to route other messages to the appropriate node.
  • Data is passed through the mxDmx network by means of data buffers (not depicted in Figure 2.A), which are identified by a unique number. These buffers are managed by the bf3Net Engine 101. Before a buffer can be used, a node needs to request access by sending the corresponding message to the bf3Net Engine 101. The same applies for the use of timers.
  • Access to a data buffer is granted on priority and age (first come, first serve).
  • the responses to the nodes are also routed through the mxDmx network based on path descriptors.
  • a node no longer requires access to a buffer it must release the buffer; again, this is done by sending a message to the bf3Net engine 101 through the mxDmx network.
  • the bf3Net Engine 101 When data is received from the physical layer 102, the bf3Net Engine 101 is notified through the bf3Net Physical Layer Interface (PLI) 113.
  • the bf3Net Engine notifies the Frame Encapsulation module 103, which retrieves the data from the physical layer, and stores it in a data buffer (which was requested from and granted by the bf3Net Engine 101).
  • bf3Net Engine 101 is notified by the Frame Encapsulation module 103, and the following three-step procedure is invoked:
  • the first step is based solely on the parameters in the received frame (datalink, IP, and TCP/UDP protocol identifier). Since a protocol is mapped to a port, a demultiplexer needs to do nothing more than fill the appropriate field of the path descriptor and pass the buffer to an upstream multiplexer if applicable, or terminate if the path leads to a protocol module at its layer. If a protocol is not supported or recognized, a value of '0' should be entered. During this step, the data integrity verification is also done (e.g. IP checksum). If this verification fails, the path is also set to '0'.
  • IP checksum e.g. IP checksum
  • the second step is done by the bf3Net Engine 101 to mask the upstream path in case a path is not available (e.g. to avoid processing of an incoming TCP segment when the datalink has not yet been established). All unsupported path fields are set to '0'.
  • the third step is the actual data processing. Because the 'zero port' is reserved as universal sink for data which must be discarded, all erratic data buffers are led to this port, which simply releases the data buffer. If the data is correct in the general sense, it is led to appropriate protocol module, based on the established path descriptor.
  • This procedure is the key to simplifying the design of the multiplexers, as they need to have no knowledge of other protocol layers (apart from the routing information) whatsoever. Also, by choosing this design approach, a protocol module can easily be exchanged, because the demultiplexing and protocol functions are isolated from each other. Another powerful feature of this architecture is the fact that the mxDmx network is used for both the control and data communication. The design of the protocol nodes can all be based on a common design framework.
  • the applicable protocol node When data must be transmitted, the applicable protocol node must fill its part of the requested data buffer (once access is granted), and pass it to the downstream multiplexer node. Please note that this statement implies two things: (a) a multiplexer will never request a data buffer, (b) a protocol node will never pass a buffer to another protocol node. This again simplifies the design of the mxDmx network nodes. Before a node passes a data buffer downstream, it must set the downstream port number in the path descriptor for the buffer. All downstream multiplexers will add their protocol information (e.g. IP header), using the path descriptor. When a completed buffer has been sent by the physical layer, the originating node will be notified.
  • protocol information e.g. IP header
  • a physical layer communication channel needs to be opened (e.g. a modem connection)
  • the bf3Net socket interface module 109 will directly signal the bf3Net Engine 101 to do so.
  • a channel identifier can be passed with this request.
  • the bf3Net Engine 101 will instruct the physical layer to start opening the connection, and notify the mxDmx network once the physical layer indicates it is ready.
  • the bf3Net Engine 101 will then coordinate establishment of the datalink, and manage it afterwards, based on the event notifications it receives from the mxDmx network nodes.
  • the bf3Net Engine 101 can individually or collectively enable and disable multiplexers with the 'enable signals' shown in Figure 2.A. Each multiplexer in the mxDmx network has an MUX_ENABLE input for this purpose. This way, if needed, the bf3Net Engine 101 can selectively stop data processing (e.g. in case the communication link is lost).
  • the bf3Net Engine 101 collects and maintains information, which can be used for profiling and debugging (e.g. buffer usage and error history). This information can be retrieved from the bf3Net Engine 101 with API commands. Also, parameters can be changed through the API, allowing run-time profiling.
  • profiling and debugging e.g. buffer usage and error history
  • Figure 2.B shows the layout of the bf3Net mxDmx network path descriptor, according to the present invention.
  • the functional description of this path descriptor has already been given in the discussion of Figure 2.A.
  • the path descriptor consists of three bitfields (one for each layer of the bf3Net architecture), each with a variable length. Together the lengths of the bitfields for each layer must equal 8 or 16 bits.
  • FIG. 2C shows the datalink architecture for Point-to-Point Protocol (PPP) connections in the bf3Net architecture, according to the present invention.
  • the Frame Encapsulation functionality is implemented by the High Level Datalink Control module 302.
  • the datalink multiplexer is implemented by the Point-to-Point Protocol (PPP) multiplexer 301.
  • PPP Point-to-Point Protocol
  • LCP Link Control Protocol
  • AUTH No authentication
  • CHAP Challenge Handshake Authentication Protocol
  • IPCP internet Protocol Control Protocol
  • FIG.D shows the datalink architecture Ethernet connections in the bf3Net architecture, according to the present invention.
  • the Frame Encapsulation functionality is implemented by the Ethernet Encapsulation module 402.
  • the datalink multiplexer is implemented by the Ethernet multiplexer 401.
  • a number of protocol modules can reside at this layer of the bf3Net architecture, according to the present invention, such as: Address Resolution Protocol (ARP) 403, and Reverse Address Resolution Protocol (RARP) 404.
  • ARP Address Resolution Protocol
  • RARP Reverse Address Resolution Protocol
  • FIG. 3A shows the general architecture of a bf3Scp Serial Communication Protocol session, according to the present invention.
  • bf3Scp both sides of the communication session are referred to as implementations.
  • a communication session consists of the exchange of messages and replies, according to a handshake definition.
  • the host implementation 101 consists of a graphical user-interface (GUI) program 103 that has access to a target database 104, and communicates with the target implementation through the built-in COM port 105 of the Personal Computer on which it runs.
  • GUI graphical user-interface
  • the bf3Scp target implementation 102 consists of the target software 108 which communicates with the host implementation through the serial port 107 of the target processor on which it runs.
  • the RS232-to-TTL signal level conversion 106 is not regarded as part of either implementation, although because of to the bf3Scp signal definitions it must be provided. A cable which has been defined for this purpose will be described in the discussion of Figure 3.F.
  • the target database 104 is provided to minimize the number of communication parameters that need to be configured to establish a communication session. It contains the parameters which are fixed at design-time. These parameters may also be stored in the GUI application, if this is more advantageous.
  • the bf3Scp host protocol engine 202 is an ActiveX object which handles all the protocol-related serial communication through the RS-232 COM port 205. It runs on any Microsoft Windows-compatible platform, and is independent of the host user-interface implementation 209. It comes in two versions: a local server which must run on the same host PC as the user-interface, or a remote server which can interact with the user-interface through a network, making use of Microsoft's DCOM technology.
  • the bf3Scp target serial port driver 203 handles physical layer communication through the Target serial port 207 on the target side. It must be developed for every processor that makes use of bf3Scp. For communication between the PC COM port 205 and the Target Serial Port 207, the RS-232-to-TTL level conversion 206 is required.
  • the bf3Scp target engine 204 is processor-independent; it handles all protocol-related communication on the target side which is not covered by the engine. It passes the received messages to the Custom Target application software 208 which must take appropriate action. With bf3Scp, the development of a custom user-interface for embedded target is limited to the following steps:
  • An application can optionally make use of the target database 210 (discussed in the context of Figure 3.A).
  • FIG.C shows the format 301 of the bf3Scp message, according to the present invention.
  • the bf3Scp message consists of the following fields:
  • the fixed header 302 in combination with the LENGTH field 306, the FCS field 309 , and the fixed trailer 310 make it simple for (embedded) applications to detect the end of a frame: if the accumulated sum of all received bytes equals '0', the last received byte is equal to 0x03, and the number of bytes received equals the value in the LENGTH field, the frame has been completely and correctly received.
  • the MESSAGE field 307 contains the qualification of the payload 308. Odd-numbered values represent messages, even-numbered values are reserved for replies. This also simplifies processing of incoming frames.
  • the SEQ field 303 is used to detect duplicate or out-of-order reception of messages and replies. Its value is incremented with each message sent (modulo-16) for a certain direction (target-host or host-target).
  • the FLAGS field 304 has a fixed value of 0x05. It is reserved for future applications.
  • the sync field S 305 is used for synchronization of the datalink.
  • the bf3Scp message is used for this purpose.
  • Figure 3.D shows the synchronization procedure for a bf3Scp communication session, according to the present invention.
  • the datalink is only (re)synchronized by the host implementation, thus simplifying the design of the target implementation.
  • a synchronization procedure starts by the sending of a SYNCREQ message 401 by the host to the target.
  • the S field is set when this message is sent.
  • the target must respond by sending a SYNCACK reply 402 (again with the S bit set) to the host.
  • the host will acknowledge the reception of the SYNCACK reply 402, by sending an ACKNOWLEDGE 403 message (once more with the S bit set) to the target. This completes the synchronization procedure.
  • Figure 3.E shows the handshake procedure for the exhange of messages and replies in a bf3Scp communication session, according to the present invention.
  • Each implementation can send messages.
  • the receiving implementation must always respond to the reception of a message according to the described handshake procedure.
  • a message transfer starts by the sending of a message 501 by implementation A to the implementation B.
  • the S field is cleared when a normal message is sent.
  • Implementation B must respond by sending a reply 502 (also with the S bit cleared) to implementation A, which will acknowledge the reception of the reply 502, by sending an ACKNOWLEDGE 503 message (once more with the S bit cleared) to the target. This completes the message transfer

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)
  • Burglar Alarm Systems (AREA)
  • Telephonic Communication Services (AREA)

Claims (6)

  1. Procédé permettant de transférer des données génériques acquises au niveau d'un emplacement distant (101, 102) à une base de données centrale (105) sur la base d'une communication de courrier électronique, comprenant les étapes consistant à :
    a. encapsuler les données acquises dans un message de courrier électronique,
    b. envoyer le courrier électronique par l'intermédiaire d'un réseau public ou privé (107) à un serveur de base de données centrale (105),
    c. extraire les données du message de courrier électronique par le serveur de base de données centrale, et
    d. stocker les données extraites dans la base de données centrale,
    - caractérisé en ce que lesdites données acquises sont communiquées sans l'utilisation d'une architecture de passerelle audit serveur de base de données en fournissant une architecture pour un logiciel de communication Internet pour des plateformes incorporées, ladite architecture étant basée sur un réseau de multiplexeurs et démultiplexeurs logiciels, contrôlé par un moteur de protocole intégré, et
    - en outre caractérisé en ce qu'une base de données cible est utilisée qui contient des paramètres associés à une application cible.
  2. Dispositif permettant de transférer des données génériques acquises au niveau d'un emplacement distant (101, 102) à une base de données centrale (105) sur la base d'une communication de courrier électronique, comprenant :
    a. un moyen pour encapsuler les données acquises dans un message de courrier électronique au niveau de l'emplacement distant,
    b. un moyen pour envoyer le courrier électronique par l'intermédiaire d'un réseau public ou privé (107) à un serveur de base de données centrale (105),
    - caractérisé en ce que le dispositif est adapté pour communiquer les données acquises audit serveur de base de données sans l'utilisation d'une architecture de passerelle, le dispositif comprenant une architecture pour un logiciel de communication Internet pour des plateformes incorporées comprenant un réseau de multiplexeurs et démultiplexeurs logiciels, contrôlé par un moteur de protocole intégré, et
    - caractérisé en outre en ce que le dispositif comprend un moyen pour utiliser une base de données cible qui contient des paramètres associés à une application cible.
  3. Programme d'ordinateur adapté pour le transfert de données génériques acquises par un dispositif au niveau d'un emplacement distant (101, 102) à une base de données centrale (105) sur la base d'une communication de courrier électronique, lorsque ledit programme est en exécution sur ledit dispositif, ledit programme étant en outre adapté pour effectuer les étapes consistant à :
    a. extraire les données du message de courrier électronique par le serveur de base de données centrale ; et
    b. stocker les données extraites dans la base de données centrale,
    lorsque ledit programme est en exécution sur ledit serveur de base de données centrale,
    - le programme étant caractérisé en ce qu'il est adapté pour communiquer lesdites données acquises audit serveur de base de données sans l'utilisation d'une architecture de passerelle en fournissant une architecture pour un logiciel de communication Internet pour des plateformes incorporées sur la base d'un réseau de multiplexeurs et démultiplexeurs logiciels, contrôlé par un moteur de protocole intégré, et
    - le programme étant en outre caractérisé en ce qu'il est adapté pour fournir une base de données cible contenant des paramètres associés à une application cible lorsque ledit programme est en exécution sur un ordinateur.
  4. Programme d'ordinateur selon la revendication 3, dans lequel :
    a. les multiplexeurs et modules de protocole constituent des noeuds dans le réseau logiciel,
    b. les noeuds dans le réseau logiciel sont affectés à une structure en couches, sur la base de leurs propriétés fonctionnelles,
    c. chaque port de multiplexeur est identifié par un numéro identificateur de port unique,
    d. les identificateurs de port au niveau de chaque couche sont utilisés pour décrire un trajet à travers le réseau, et
    e. les multiplexeurs et modules de protocole interagissent avec ledit moteur de protocole intégré, en envoyant et en recevant des messages dudit moteur de protocole à travers ledit réseau, en utilisant le descripteur de trajet de l'étape (d) pour acheminer les messages.
  5. Procédé de configuration et de gestion d'un dispositif selon la revendication 2 par un ordinateur personnel comprenant les étapes consistant à :
    a. utiliser une architecture pour fournir une interface utilisateur graphique, en exécution sur un ordinateur personnel qui communique avec ledit dispositif par l'intermédiaire d'une interface série en échangeant des messages avec le logiciel d'application en exécution sur ledit dispositif,
    b. échanger des messages en utilisant un protocole de communications série qui est mis en oeuvre par un moteur de protocole hôte en exécution sur l'ordinateur personnel et un moteur de protocole cible en exécution sur le processeur incorporé dudit dispositif,
    c. le moteur de protocole hôte est un objet qui prend en charge la communication série liée au protocole par l'intermédiaire de l'interface série, et
    d. le moteur de protocole cible est un module logiciel indépendant du processeur qui passe un message reçu du moteur de protocole hôte à un logiciel d'application cible pour un autre traitement,
    caractérisé en ce que le procédé comprend les étapes consistant à :
    - configurer le dispositif,
    - communiquer des données acquises à un serveur de base de données sans l'utilisation d'une architecture de passerelle, en fournissant une architecture pour un logiciel de communication Internet pour des plateformes incorporées, ladite architecture étant basée sur un réseau de multiplexeurs et démultiplexeurs logiciels, contrôlé par un moteur de protocole intégré,
    - configurer un client d'acquisition de données et le serveur de base de données pour échanger des messages de courrier électronique,
    - fournir une base de données cible qui contient des paramètres associés à une application cible,
    le procédé étant en outre caractérisé en ce que ladite interface est une interface RS-232 et en ce que ledit objet prenant en charge la communication série est un objet ActiveX.
  6. Procédé de configuration et de gestion d'un dispositif selon la revendication 2 par un serveur de base de données, comprenant :
    a. la configuration du dispositif pour recevoir des messages de courrier électronique d'une boîte aux lettres au niveau du serveur au moyen du protocole POP3, dans lequel lesdits messages contiennent des données de configuration, et
    b. l'évaluation desdits messages par ledit dispositif, et l'ajustement des paramètres de configuration stockés localement,
    le procédé étant caractérisé en ce qu'il comprend les étapes consistant à :
    - communiquer lesdits messages sans l'utilisation d'une architecture de passerelle audit dispositif en fournissant une architecture pour un logiciel de communication Internet pour des plateformes incorporées, ladite architecture étant basée sur un réseau de multiplexeurs et démultiplexeurs logiciels, contrôlé par un moteur de protocole intégré, et
    - configurer le dispositif pour utiliser une base de données cible contenant des paramètres associés à une application cible.
EP02760317A 2001-08-24 2002-08-13 Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant Expired - Lifetime EP1419626B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP02760317A EP1419626B1 (fr) 2001-08-24 2002-08-13 Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP01870183 2001-08-24
EP01870183 2001-08-24
EP02760317A EP1419626B1 (fr) 2001-08-24 2002-08-13 Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant
PCT/EP2002/009035 WO2003019883A2 (fr) 2001-08-24 2002-08-13 Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives

Publications (2)

Publication Number Publication Date
EP1419626A2 EP1419626A2 (fr) 2004-05-19
EP1419626B1 true EP1419626B1 (fr) 2006-04-12

Family

ID=8185011

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02760317A Expired - Lifetime EP1419626B1 (fr) 2001-08-24 2002-08-13 Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant

Country Status (8)

Country Link
US (1) US7624148B2 (fr)
EP (1) EP1419626B1 (fr)
AT (1) ATE323364T1 (fr)
AU (1) AU2002325941B2 (fr)
CA (1) CA2458341A1 (fr)
DE (1) DE60210630T2 (fr)
ES (1) ES2262828T3 (fr)
WO (1) WO2003019883A2 (fr)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070067403A1 (en) * 2005-07-20 2007-03-22 Grant Holmes Data Delivery System
US20070027955A1 (en) * 2005-07-28 2007-02-01 Jwj Software, Llc. Systems, methods and apparatus of an email client
US20080086640A1 (en) * 2005-07-28 2008-04-10 Jmj Software, Llc Systems, methods and apparatus of an email client
JP4477599B2 (ja) * 2006-04-28 2010-06-09 ブラザー工業株式会社 原稿読取装置、画像形成装置及び原稿読取システム
US8306883B2 (en) 2007-04-30 2012-11-06 Textura Corporation Construction payment management systems and methods with specified billing features
US10171392B1 (en) 2010-07-09 2019-01-01 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10158590B1 (en) 2010-07-09 2018-12-18 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10212112B1 (en) 2010-07-09 2019-02-19 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10419374B1 (en) 2010-07-09 2019-09-17 Gummarus, Llc Methods, systems, and computer program products for processing a request for a resource in a communication
US10015122B1 (en) 2012-10-18 2018-07-03 Sitting Man, Llc Methods and computer program products for processing a search
DE102011078030A1 (de) * 2011-06-24 2012-12-27 Endress + Hauser Flowtec Ag Verfahren zum Betreiben eines Feldgerätes
US10013158B1 (en) 2012-09-22 2018-07-03 Sitting Man, Llc Methods, systems, and computer program products for sharing a data object in a data store via a communication
US10021052B1 (en) 2012-09-22 2018-07-10 Sitting Man, Llc Methods, systems, and computer program products for processing a data object identification request in a communication
US20140089420A1 (en) * 2012-09-23 2014-03-27 Deep River Ventures, Llc Methods, Systems, and Program Products for Processing a Reference in a Communication to a Remote Data Object
US20140172999A1 (en) * 2012-12-16 2014-06-19 Deep River Ventures, Llc Methods, Systems, and Computer Program Products for Accessing a Service Via a Proxy Communications Agent
US10033672B1 (en) 2012-10-18 2018-07-24 Sitting Man, Llc Methods and computer program products for browsing using a communicant identifier
US10019135B1 (en) 2012-10-18 2018-07-10 Sitting Man, Llc Methods, and computer program products for constraining a communication exchange
CN111935793B (zh) * 2020-08-18 2024-11-01 国网江苏省电力有限公司 基于数据采集业务的双模4g公专网在线切换装置和方法
CN112202798B (zh) * 2020-10-09 2022-07-15 平安科技（深圳）有限公司 数据的协议转化方法、系统、电子设备及存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI114745B (fi) * 1998-06-01 2004-12-15 Metso Automation Oy Kenttälaitteiden hallintajärjestelmä
WO2000019681A2 (fr) * 1998-09-30 2000-04-06 Xbind, Inc. Systeme de construction et de reconfiguration dynamique de piles de protocoles
US6112246A (en) * 1998-10-22 2000-08-29 Horbal; Mark T. System and method for accessing information from a remote device and providing the information to a client workstation
FR2790629A1 (fr) * 1999-02-19 2000-09-08 Bull Cp8 Procede d'activation d'applications localisees dans une carte a puce par un navigateur du type dit "web"
FR2791159B1 (fr) * 1999-03-15 2001-05-04 Bull Cp8 Procede d'acces a un objet a l'aide d'un navigateur de type "web" cooperant avec une carte a puce et architecture pour la mise en oeuvre du procede
EP1045549A1 (fr) * 1999-04-15 2000-10-18 International Business Machines Corporation Système et méthode non intrusif pour la surveillance et la gestion des réseaux informatiques distribués
US6446192B1 (en) * 1999-06-04 2002-09-03 Embrace Networks, Inc. Remote monitoring and control of equipment over computer networks using a single web interfacing chip

Also Published As

Publication number Publication date
EP1419626A2 (fr) 2004-05-19
ES2262828T3 (es) 2006-12-01
US20050021640A1 (en) 2005-01-27
DE60210630D1 (de) 2006-05-24
US7624148B2 (en) 2009-11-24
AU2002325941B2 (en) 2007-10-04
CA2458341A1 (fr) 2003-03-06
ATE323364T1 (de) 2006-04-15
DE60210630T2 (de) 2007-05-03
WO2003019883A2 (fr) 2003-03-06
WO2003019883A3 (fr) 2003-10-23

Similar Documents

Publication Publication Date Title
EP1419626B1 (fr) Systeme pour l'acquisition de donnees a distance, sur la base d'une communication de messages electroniques sur des reseaux publics et prives, et procédé et logiciel correspondant
AU2002325941A1 (en) System for remote data acquisition based on e-mail message communication through public and private networks
US5894557A (en) Flexible point-to-point protocol framework
US7149817B2 (en) Infiniband TM work queue to TCP/IP translation
US6091737A (en) Remote communications server system
US5289468A (en) Permanent adapter having modulation and demodulation means for connecting networks
US7882254B2 (en) Common protocol layer architecture and methods for transmitting data between different network protocols and a common protocol packet
KR20010042443A (ko) 무선 패킷 데이터 통신 장치 및 방법
CN1247659A (zh) 因特网－ss7网关
WO2002035313A2 (fr) Procede et dispositif d'interreseautage optique utilisant des composants modulaires pour reseaux etendus, reseaux metropolitains et reseaux locaux
US7529840B2 (en) HTTP use for bidirectional communication
EP1518354A2 (fr) Fournisseur de depot synchronise d'instrument de gestion de fenetres
US20060280174A1 (en) Method and system for establishing a data link layer protocol on a physical layer port connection
US20080259932A1 (en) Method and System for Facilitating a First and Second Protocol Between a Data Processing System and an ISP
JP2000099428A (ja) ネットワーク間における情報の収集方法及びこれに用いるネットワーク管理装置
JPH09331325A (ja) ネットワーク管理方式
Cisco Cisco 3600 Series - Cisco IOS Release 12.2 XB
CN100375464C (zh) 网络互连时各终端的数据通信方法
KR100423634B1 (ko) 씨오알비에이-에스엔엠피 트랩 서버
US20090052446A1 (en) Communications Interface
KR20040001291A (ko) 망 요소 관리 시스템에서 장치 연동 서버 및 방법
US20060195555A1 (en) Updating of software stored in a computer of a data communication system
JP2001127792A (ja) 逐次処理によるネットワーク通信
Ray et al. Service Access Procedure (SAP) for a transport layer protocol
JP5121789B2 (ja) データ伝送システム及びコンピュータ

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: 20040310

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 IE IT LI LU MC NL PT SE SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

17Q First examination report despatched

Effective date: 20040914

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RTI1 Title (correction)

Free format text: SYSTEM FOR REMOTE DATA ACQUISITION BASED ON E-MAIL MESSAGE COMMUNICATION THROUGH PUBLIC AND PRIVATE NETWORKS AND CORRESPO

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): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

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

Ref country code: CH

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: LI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REF Corresponds to:

Ref document number: 60210630

Country of ref document: DE

Date of ref document: 20060524

Kind code of ref document: P

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

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

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060712

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060712

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

Ref country code: IE

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

Effective date: 20060814

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

Ref country code: MC

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

Effective date: 20060831

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

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060912

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2262828

Country of ref document: ES

Kind code of ref document: T3

ET Fr: translation filed
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: 20070115

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

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060713

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

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060712

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

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

Ref country code: LU

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

Effective date: 20060813

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

Ref country code: DE

Payment date: 20080822

Year of fee payment: 7

Ref country code: ES

Payment date: 20080828

Year of fee payment: 7

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

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20060412

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

Ref country code: FR

Payment date: 20080813

Year of fee payment: 7

Ref country code: IT

Payment date: 20080822

Year of fee payment: 7

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

Ref country code: GB

Payment date: 20080821

Year of fee payment: 7

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

Effective date: 20090813

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20100430

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: 20090831

Ref country code: DE

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

Effective date: 20100302

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20090814

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: 20090813

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

Ref country code: IT

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

Effective date: 20090813

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

Ref country code: ES

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

Effective date: 20090814

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

Ref country code: NL

Payment date: 20130830

Year of fee payment: 12

REG Reference to a national code

Ref country code: NL

Ref legal event code: V1

Effective date: 20150301

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

Ref country code: NL

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

Effective date: 20150301