EP0667693B1 - Netzwerkeinrichtung für ein System zur Herstellung von Glasgegenständen - Google Patents

Netzwerkeinrichtung für ein System zur Herstellung von Glasgegenständen Download PDF

Info

Publication number
EP0667693B1
EP0667693B1 EP95300912A EP95300912A EP0667693B1 EP 0667693 B1 EP0667693 B1 EP 0667693B1 EP 95300912 A EP95300912 A EP 95300912A EP 95300912 A EP95300912 A EP 95300912A EP 0667693 B1 EP0667693 B1 EP 0667693B1
Authority
EP
European Patent Office
Prior art keywords
gateway
library
socket
task
database
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
EP95300912A
Other languages
English (en)
French (fr)
Other versions
EP0667693A2 (de
EP0667693A3 (de
Inventor
David K. Hwang
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.)
Emhart Glass SA
Original Assignee
Emhart Glass SA
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 Emhart Glass SA filed Critical Emhart Glass SA
Publication of EP0667693A2 publication Critical patent/EP0667693A2/de
Publication of EP0667693A3 publication Critical patent/EP0667693A3/de
Application granted granted Critical
Publication of EP0667693B1 publication Critical patent/EP0667693B1/de
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • C—CHEMISTRY; METALLURGY
    • C03—GLASS; MINERAL OR SLAG WOOL
    • C03B—MANUFACTURE, SHAPING, OR SUPPLEMENTARY PROCESSES
    • C03B9/00—Blowing glass; Production of hollow glass articles
    • C03B9/30—Details of blowing glass; Use of materials for the moulds
    • C03B9/40—Gearing or controlling mechanisms specially adapted for glass-blowing machines
    • C03B9/41—Electric or electronic systems
    • 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/08—Protocols for interworking; Protocol conversion
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99944—Object-oriented database structure
    • Y10S707/99945—Object-oriented database structure processing

Definitions

  • a glassware factory has a number of computer controlled machines, which together, define the glassware forming process.
  • These machines may include, for example, an I.S. machine, such as disclosed in US-A-4,641,269, which includes a plurality of sections, each controlled by an independent controller. Archive data for these controllers is centralized at a control room console. Formed bottles are inspected by inspection equipment which may comprise one or more discrete machines each having its own independent controller.
  • Such I.S. machines and inspection equipment sold by the present applicant operate on the non-standard QNX platform (a multi-tasking, multiuser, real-time operating system for microcomputer systems marketed by Quantum Software Systems, Ltd).
  • a non-standard platform can not be accessed by outside computers operating on standard platforms such as UNIX, VAX/VMS and Novell's Netware in the standard ETHERNET TCP/IP (Transmission Control Protocol/Internet Protocol) network environment, and accordingly, such user workstations in the glassware factory can not access the databases of these I.S. machines or the inspection equipment.
  • the invention is directed to a system generally of the type disclosed in EP-A-O 381 365, comprising at least one event driven database operating on one protocol, at least one workstation operating on a second protocol including a library of API (Applications Programming Interface) calls in said one protocol, a socket library for sending call packets in said second protocol, and a gateway library for translating an API call in said one protocol to a call packet in said second protocol.
  • the system also comprises a network gateway including a socket library for receiving call packets in said second protocol, and a gateway service for translating a call packet received by said network gateway socket library in said second protocol to an API call in said first protocol and for delivering said translation call to said event driven data base.
  • the system disclosed in the above EP-A comprises a network gateway operating on a first platform and a work station operating on a second platform, said network gateway including a first BSD (Berkeley Socket Distribution) socket library, and said work station including application means for making and receiving API (Application Programming Interface) calls, and a second BSD (Berkeley Socket Distribution) socket library, and said BSD socket libraries being adapted to communicate bidirectionally via TCP/IP (Transmission Control Protocol/Internet Protocol) packets.
  • BSD Application Programming Interface
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • said work station further comprises an event driven data base library, and a gateway library, said event driven data base library being adapted to bidirectionally interconnect said application means and said gateway library, and said gateway library being adapted to bidirectionally interconnect said event driven data base library and said second BSD socket library, and said network gateway further comprises an event driven database, and a gateway service adapted to bidirectionally interconnect said network gateway first BSD socket library and said event driven database.
  • a glassware forming I.S. machine has a number of Production Line Consoles - Each console contains an event driven database that supports all this supervisory control information for that I.S. machine. Archive Data for all of these event driven databases of multiple machines is centralized at a Control Room Console hard drive (disk) database. Also available on the QNX network are the cold-end production consoles running Inspection Connection Software that accesses the Inspection Equipment database via ARCnet. It is the goal of this invention to allow user application access to these QNX-based databases from workstations running either UNIX, VAX/VMS or Novell's Netware in the standard Ethernet TCP/IP network environment through the Network Gateway.
  • the Network Gateway is an IBM PC compatible computer that consists of the following hardware and software components: 486/33 MHz IBM-PC with 8 MB memory (no hard drive); QNX operating system V2.15F or later; QNXnet board; Fastech's TCP/IP Connectivity for QNX Device Driver, including the Berkeley Socket Library and the CMC-640 Ethernet interface card; and Gateway Server Software for accessing the databases.
  • the gateway traffic is two-way, however, meaning that the Network Gateway can also initiate the data transfer to reach the workstations. In implementation, the initiated events are limited to only the database item changes defined and requested by the workstation.
  • the Network Gateway Software supports multiple user "ports" which can reside in multiple processes within a single user workstation or in a single or multiple process among multiple users' workstations.
  • the Network Gateway Software itself can also reside in a single CPU or multiple PC's, each with a different name.
  • the cold-end production line console is another IBM-PC compatible computer interfacing with both the ARCnet and QNX network.
  • the ARCnet interface collects data from all of the Inspection Equipment while QNXnet makes the cold-end PLC a node on the QNX network.
  • the Inspection Connection software is running under QNX on the cold-end PLC.
  • the Gateway software is partitioned into client (workstation) and server (Gateway) parts.
  • the client software will include a set of API library files in "C" source code format so that the user can compile and link it with his application code and TCP/IP socket library.
  • Running on the Gateway under QNX is the server software that services the data acquisition requests (from the user to the databases) as well as database change events (from the database to user application).
  • the server software supports multiple client connections as well as multiple sessions.
  • EDDB Event Driven Database
  • Figure 2 the application task can issue EDDB API calls from the local EDDB Library to open (locate) a local or remote EDDB database and access data from it thereafter.
  • the user does not need to know the location of the database.
  • the geographical locations of the EDDB databases are resolved transparently by the QNX networking facility.
  • the Gateway design extends the EDDB/IC (Inspection Connection) Library API's across the network to enable developers to write user application programs on UNIX, VAX/VMS/Novell workstations using the same EDDB/IC programming interface.
  • the EDDB/IC Library on the user's node must be enhanced by adding a layer of software below it to support packet transfer between the user and the Gateway. A corresponding set of software must also exist on the Gateway node to service the request.
  • FIG. 3 depicts the distributed software design of this approach: Part of the software -- Gateway Library -- is distributed upon user's platform while the other part -- Gateway Service -- resides on the Gateway, both of them use the Berkeley Sockets Library (BSD 4.3) to perform low-level TCP socket setup, session connection and packet transfer tasks.
  • BSD 4.3 Berkeley Sockets Library
  • the UNIX/VMS/Novell application program can now access the remote databases as if they were available locally.
  • the user applications make EDDB/IC API calls, but the Gateway Library converts the "name locate,” “send” and “vc release” system calls that are unique for the QNX environment to TCP/IP command packets and sends the packets to Gateway.
  • the Gateway Service running under QNX will then provide the real "name locate,” “send” and "vc release” calls to access EDDB databases information and send the data and status back to user application program over the same pair of network sockets. All of the packet transfer mechanism is transparent to the developer, thus it is as if the data were available to him locally on his machine.
  • the Gateway Library is written in ANSI "C" and requires minimum porting work to make it available to the developer's target system. No change will be necessary in the Gateway Service, which is available only in the executable form and will run forever in the Gateway memory as long as Gateway PC is running. From the software point of view, the Gateway is a nonstandard TCP/IP protocol application in a distributed environment.
  • the user is the third party application who initiates the request for communication and waits for a response from server.
  • the user "lives" in a user machine.
  • a server resides in the Gateway (forever) and waits for incoming communication requests from a user. When it receives a user request, the server performs the necessary database access and returns the result to the client.
  • the server "lives" in the Gateway and acts like a universal database engine.
  • the Gateway provides dynamic event driven data updates from a database to the user as long as the data items are being attached by the user application.
  • the user program is, accordingly, notified by the server (which was first notified by the EDDB/IC database) only when there was a real change in the selected database item.
  • This additional requirement calls for a pair of dedicated sockets on the Gateway and user's node to communicate with each other (connecting from Gateway to user).
  • the TCP transport protocol is used.
  • the Gateway provides services that will connect multiple user nodes to the EDDB databases. Each connection has its own unique socket established with the user throughout the session. A session is defined as user making connection with the Gateway to request information. When a session is over, the socket is released to the system for use in the future. The number of sockets available is only limited by what the TCP/QNX device driver can provide.
  • the top-level context diagram shown in Figure 4 depicts the Gateway Software as a whole, supporting the connection between Production Line Consoles (PLC's) and user's UNIX/VMX/Novell workstations.
  • PLC Production Line Consoles
  • the user application makes the EDDB/IC API calls to locate and read the EDDB/IC database.
  • the function calls return with database handle and item contents for user's applications.
  • the Gateway also supports EDDB/IC exceptions that came in from PLC's or Inspection Connection as signals to user's task for asynchronous event update. For example, these external events could be Event Angle change or Inspection results packets.
  • the Gateway handles all the detail session connection and data packet transfers between two different operating systems (UNIX/VMS/Novell and QNX) and networking environments (TCP/IP on Ethernet and QNXnet on ARCnet).
  • the Gateway design is implemented in two parts as depicted in Figure 5.
  • the Gateway Library (user application library) is the part that "lives" on client's node. It interfaces with user's applications and converses with Gateway Service (Server Application Software) in the Gateway via TCP packets on the Ethernet network.
  • the Gateway Service consists of a set of user application tasks to locate and access an EDDB database in the QNX environment.
  • the Server Application gives the results back to the Client Application via TCP packets. The results could be due to either database inquiry or EDDB exception.
  • the Gateway Library is the layer of software for the user application programmer to link with in order to access the database.
  • Figure 6 depicts the data flow among the various modules of the Gateway Library as used by the application.
  • the functions for user interface are contained in the following modules: Name Locate, Send, and PrepareForEvents.
  • the Client Call Module handles TCP packet transfer by making "send” and "recv” calls in the Berkeley Sockets Library.
  • the PrepareForEvents function initializes the socket for data transfer on user's node and sets up the user event signal handling mechanism by establishing a separate event queing socket. After the client has made connection with the Gateway Service, the Gateway Service, besides fulfilling other responsibilities, will attempt to set up its own event queing socket and make a connection to the client's event queing socket. If this connection is established, any attached database item changes in EDDB/IC will be sent back to the user via event queing socket.
  • the message is packaged locally and sent from the client to the Gateway Server where the packets are unpacked and decoded before doing the QNX "send" message passing.
  • the received packets will then be sent back to the client application task buffer space in the EDDB/CI Library, and ultimately transferred to client's application.
  • FIG. 7 depicts intertask communication within the Gateway Service as well as data interfaces between the Gateway Service and its outside resources.
  • the Gateway Server functions as a universal, session-oriented database server, and its design consists of the following coordinating tasks:
  • the task wakes up because "coms" sent over a message, it first decodes the operation code (name locate, send or vc release) and performs the QNX operation accordingly. The task will then reply to the sender task "coms" with the results.
  • the operation code name locate, send or vc release
  • the task If the task receives an EDDB/IC database exception signal, it will send a QNX message immediately to the task "rush" to notify the event source.
  • Figure 8 illustrates the program structure diagram for the Main Program that first sets up the socket in "listening mode" for client connection request. Once the task gets into the do-forever-loop to accept () for more connections, each connection that comes in will result in a different socket id and child task extension number. These two parameters are then used for spawning off a set of child tasks: "coms” and "data” to service a particular session. Since multiple sessions can be opened in the Gateway, several copies of "coms" or "data” might exist on the task table at the same time. Task-to-task communications must therefore be handled according to the task registration name not the task name.
  • Figure 9 shows the program structure diagram for the task "coms” designed as a separate task to process packets from the client and replies over the same open channel.
  • the Register Task Name section consists of a QNX system call "name attach” to attach itself with the local clearinghouse so the "data” task can be communicated with.
  • "coms” would also try to locate the corresponding "data” task name by calling "name-locate.” Both the task name registration and location use the same command line parameters, consisting of socket id and child task number.
  • Receiving Packets are supposed to go on forever until the socket connection is disrupted, due to, for example, client application exiting, in which case the "coms” task must send a message to the "data” task to force it to exit before the task itself died. This provision is designed to avoid “zombie” processes remained in the system when a session is terminated.
  • the task After receiving a packet, the task "coms” first decodes the op-code to decide if it's "name locate,” “send,” or “vc-receive.” The send message and reply packet sizes are different and must be specified accordingly. The program will then forward the message to the "data" task for processing, get the result back, and return it to the client application over the network.
  • Figure 10 illustrates the program structure diagram for the task "data” to process either the messages from “coms” task or database (EDDB or CI) exceptions.
  • the Get Events routine is receive-blocked until either a Database Event comes in from the attached database item (s) or it gets a message from task "coms.”

Claims (1)

  1. Formungsmaschine für Glasgegenstände, umfassend ein Netzwerk-Gateway, das auf einer ersten Plattform betrieben wird, und eine Arbeitsstation, die auf einer zweiten Plattform betrieben wird,
       wobei das Netzwerk-Gateway eine erste BSD- (Berkeley Socket Distribution) Socket-Bibliothek umfasst und
       wobei die Arbeitsstation eine Applikation zum Erstellen und Empfangen von API- (Application Programming Interface) Aufrufen umfasst sowie eine zweite BSD- (Berkeley Socket Distribution) Socket-Bibliothek und
       wobei die ersten und zweiten BSD-Socket-Bibliotheken dahingehend angepasst sind, dass sie bidirektional über TCP/IP- (Transmission Control Protocol/Internet Protocol) Pakete kommunizieren,
       dadurch gekennzeichnet, dass die Arbeitsstation weiterhin
       eine ereignisbetriebene Datenbankbibliothek umfasst sowie
       eine Gateway-Bibliothek,
       wobei die ereignisbetriebene Datenbankbibliothek dahingehend angepasst ist, dass sie bidirektional die Applikation und die Gateway-Bibliothek miteinander verbindet, und
       wobei die Gateway-Bibliothek dahingehend angepasst ist, dass sie bidirektional die ereignisbetriebene Datenbankbibliothek und die zweite BSD-Socket-Bibliothek miteinander verbindet,
       wobei das Netzwerk-Gateway weiterhin
       eine ereignisbetriebene Datenbank umfasst sowie
       einen Gateway-Service, der dahingehend angepasst ist, dass er bidirektional die erste BSD-Socket-Bibliothek und die ereignisbetriebene Datenbank miteinander verbindet.
EP95300912A 1994-02-15 1995-02-14 Netzwerkeinrichtung für ein System zur Herstellung von Glasgegenständen Expired - Lifetime EP0667693B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US196307 1994-02-15
US08/196,307 US5475601A (en) 1994-02-15 1994-02-15 Control for glassware forming system including bidirectional network gateway

Publications (3)

Publication Number Publication Date
EP0667693A2 EP0667693A2 (de) 1995-08-16
EP0667693A3 EP0667693A3 (de) 1995-11-29
EP0667693B1 true EP0667693B1 (de) 2003-06-04

Family

ID=22724851

Family Applications (1)

Application Number Title Priority Date Filing Date
EP95300912A Expired - Lifetime EP0667693B1 (de) 1994-02-15 1995-02-14 Netzwerkeinrichtung für ein System zur Herstellung von Glasgegenständen

Country Status (4)

Country Link
US (1) US5475601A (de)
EP (1) EP0667693B1 (de)
JP (1) JPH07267653A (de)
DE (1) DE69530947T2 (de)

Families Citing this family (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2699305B1 (fr) * 1992-12-11 1995-01-13 Bull Sa Dispositif d'utilisation de fonctions de pseudo point de communication déportées (pseudo sockets).
KR100387207B1 (ko) * 1994-03-15 2003-10-04 디지 인터내셔날 인크. 원격네트워크장치에의한통신시스템및통신방법
US5721876A (en) * 1995-03-30 1998-02-24 Bull Hn Information Systems Inc. Sockets application program mechanism for proprietary based application programs running in an emulation environment
GB2307625B (en) * 1995-11-23 1999-11-24 Motorola Israel Ltd Method and system for communication over a wireless modem
ES2136467T3 (es) 1996-01-17 1999-11-16 Siemens Ag Aparato de automatizacion.
BR9712194A (pt) * 1996-10-04 1999-08-31 Fisher Controls Int Interface entre uma rede de comunicações e um sistema de controle de processo, programa de software que implementa uma interface entre uma rede de comunicações e um sistema de controle de processo para execução em um processador, artigo de fabricação implementando uma interface de programa de software entre uma rede de comunicações e um sistema de controle de processo para execução em um processador, e, interface adaptada a fim de ser acoplada entre uma rede de comunicações remota e um sistema de controle de processo.
JPH10161707A (ja) * 1996-11-29 1998-06-19 Sukiyan Technol:Kk Ｆａシステムの制御方法
AUPO446997A0 (en) * 1997-01-06 1997-01-30 Crown Limited Table gaming management system
EP1013047A1 (de) * 1997-05-19 2000-06-28 Coactive Networks, Inc. Serversystem und verfahren zur netzverbindung von steuernetzwerken und eingangs/ausgangselementen mit dem world-wide-web
US6014699A (en) * 1997-08-29 2000-01-11 International Business Machines Corporation Internet protocol assists for high performance LAN connections
US6006261A (en) * 1997-08-29 1999-12-21 International Business Machines Corporation Internet protocol assists using multi-path channel protocol
US5974049A (en) * 1997-08-29 1999-10-26 International Business Machines Corporation Internet protocol assists for high performance LAN connections
US5999974A (en) * 1997-08-29 1999-12-07 International Business Machines Corporation Internet protocol assists for high performance LAN connections
US6084859A (en) * 1997-08-29 2000-07-04 International Business Machines Corporation Internet protocol assists using multi-path channel protocol
US6185218B1 (en) 1997-08-29 2001-02-06 International Business Machines Corporation Communication method and apparatus for use in a computing network environment having high performance LAN connections
US6078964A (en) * 1997-08-29 2000-06-20 International Business Machines Corporation Establishing direct communications between two hosts without using a high performance LAN connection
US6009467A (en) * 1997-08-29 1999-12-28 International Business Machines Corporation System for checking status of supported functions of communication platforms at preselected intervals in order to allow hosts to obtain updated list of all supported functions
US6003080A (en) * 1997-08-29 1999-12-14 International Business Machines Corporation Internet protocol assists using multi-path channel protocol
US6003088A (en) * 1997-08-29 1999-12-14 International Business Machines Corporation Blocking IP datagrams in a multi-path channel point-to-point environment
US6023734A (en) * 1997-08-29 2000-02-08 International Business Corporation Establishing direct communications between two hosts without using a high performance LAN connection
US5987515A (en) * 1997-08-29 1999-11-16 International Business Machines Corporation Internet protocol assists using multi-path channel protocol
US6321272B1 (en) * 1997-09-10 2001-11-20 Schneider Automation, Inc. Apparatus for controlling internetwork communications
US6963905B1 (en) * 1997-09-29 2005-11-08 Emc Corporation System and method including a communication interface for transferring information between at least two processes
US6349341B1 (en) * 1998-07-30 2002-02-19 Advanced Micro Devices, Inc. Method and system for providing inter-tier application control in a multi-tiered computing environment
US6600743B1 (en) 1998-08-25 2003-07-29 International Business Machines Corporation IP multicast interface
US6490285B2 (en) 1998-08-25 2002-12-03 International Business Machines Corporation IP multicast interface
US6327621B1 (en) 1998-08-25 2001-12-04 International Business Machines Corporation Method for shared multicast interface in a multi-partition environment
US6757731B1 (en) * 1999-02-25 2004-06-29 Nortel Networks Limited Apparatus and method for interfacing multiple protocol stacks in a communication network
US6269662B1 (en) * 1999-03-05 2001-08-07 Emhart Glass S.A. Pneumatic machine control unit for an I.S. machine
CN1095556C (zh) * 2000-01-25 2002-12-04 清华大学 全方位一体化的集成化pc数控系统
US6822970B1 (en) * 2000-01-31 2004-11-23 Owens-Brockway Glass Container Inc. Glassware forming system with star network communication configuration
US6883019B1 (en) * 2000-05-08 2005-04-19 Intel Corporation Providing information to a communications device
JP2002063240A (ja) * 2000-06-06 2002-02-28 Mori Seiki Co Ltd 生産管理システム
DE10030525A1 (de) * 2000-06-28 2002-01-24 Harman Becker Automotive Sys Verfahren zur Kommunikation zwischen zwei Netzwerken sowie Netzwerk
US7200666B1 (en) * 2000-07-07 2007-04-03 International Business Machines Corporation Live connection enhancement for data source interface
US6760782B1 (en) 2000-08-04 2004-07-06 Schneider Automation Inc. Apparatus for controlling internetwork communications
GB0031206D0 (en) * 2000-12-21 2001-01-31 Ibm Multi-platform command line interpretation
DE10140271A1 (de) * 2001-08-16 2003-03-06 Hermann Heye I I Elektronische Steuerung für Glasformmaschinen
JP2003150672A (ja) * 2001-11-09 2003-05-23 Fujitsu Ltd 工場監査方法及び工場監査システム
US7017373B2 (en) * 2002-09-03 2006-03-28 Owens-Brockway Glass Container Inc. Glassware forming machine control system
KR20050079730A (ko) * 2004-02-06 2005-08-11 삼성전자주식회사 이종 프로토콜 노드들을 연결하는 방법 및 장치
FR2875357B1 (fr) * 2004-09-13 2008-04-18 Stephane Pomies Systeme de gestion et de mise en relation de machines avec des utilisateurs, ou autres machines, distants
US8812466B2 (en) 2012-02-10 2014-08-19 International Business Machines Corporation Detecting and combating attack in protection system of an industrial control system
US20130212668A1 (en) * 2012-02-13 2013-08-15 International Business Machines Corporation Suspension of Processes in Industrial Control System When an Anomaly Occurs
KR20140147583A (ko) * 2013-06-20 2014-12-30 한국전자통신연구원 산업제어 시스템의 부정 접근을 방지하기 위한 장치 및 그 방법

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4457772A (en) * 1981-07-08 1984-07-03 Ball Corporation Management control system for forming glassware
JPS60500443A (ja) * 1983-01-26 1985-04-04 エムハ−ト・インダストリ−ズ・インコ−ポレ−テッド ガラス器成形機用プログラム可能制御システム
US4641269A (en) * 1983-01-26 1987-02-03 Emhart Industries, Inc. Programmable control system for glassware forming machines
US5349678A (en) * 1991-08-21 1994-09-20 Norand Corporation Versatile RF data capture system
US5142622A (en) * 1989-01-31 1992-08-25 International Business Machines Corporation System for interconnecting applications across different networks of data processing systems by mapping protocols across different network domains
US5218697A (en) * 1990-04-18 1993-06-08 Microsoft Corporation Method and system for networking computers having varying file architectures
US5247450A (en) * 1991-02-12 1993-09-21 Vhc Ltd. Electronic timing system for glassware-forming machines
US5097528A (en) * 1991-02-25 1992-03-17 International Business Machines Corporation System for integrating telephony data with data processing systems
US5224098A (en) * 1991-07-17 1993-06-29 International Business Machines Corporation Compensation for mismatched transport protocols in a data communications network
US5345389A (en) * 1992-04-21 1994-09-06 Vhc, Ltd. Electronic controller for a glassware forming machine
US5537417A (en) * 1993-01-29 1996-07-16 International Business Machines Corporation Kernel socket structure for concurrent multiple protocol access

Also Published As

Publication number Publication date
JPH07267653A (ja) 1995-10-17
DE69530947D1 (de) 2003-07-10
US5475601A (en) 1995-12-12
EP0667693A2 (de) 1995-08-16
DE69530947T2 (de) 2003-12-24
EP0667693A3 (de) 1995-11-29

Similar Documents

Publication Publication Date Title
EP0667693B1 (de) Netzwerkeinrichtung für ein System zur Herstellung von Glasgegenständen
CA2308782C (en) Distributed web application server
EP0724803B1 (de) Anwendungsprogrammierungs-schnittstelle und -technik
EP1027794B1 (de) Verfahren und system zur unterstützung verteilter software- entwicklung ohne bewusstsein der verteilten charakteristik der software
US5396630A (en) Method and system for object management across process boundries in a data processing system
US5699523A (en) Method and apparatus for communication between at least one client and at least one server
US6047324A (en) Scalable distributed network controller
US4893307A (en) Method and apparatus for linking SNA terminals to an SNA host over a packet switched communications network
EP0330834B1 (de) Verfahren und Vorrichtung zur Verbindung eines SNA-Hostrechners mit einem entfernten SNA-Hostrechner über ein paketvermitteltes Nachrichtennetz
EP0485252A2 (de) Gerät und Verfahren zur Entkupplung von Datenaustauschdetails zur Beschaffung einer Hochleistungskommunikation zwischen Softwareprozessen
CA2245963C (en) Distributed kernel operating system
EP1088422B1 (de) Benachrichtigungssystem in einer telekommunikationssteuereinrichtung
US6920143B1 (en) Computer telephony system using multiple hardware platforms to provide telephony services
US6490623B1 (en) System, method and computer readable code for encapsulating system, language and device independent communications socket functionality in a lightweight uniform communications object model
EP1229470A2 (de) Verfolgen von Daten bezüglich computergstützte Lehrgängen
KR100218681B1 (ko) 메시지 큐 루팅 테이블을 이용한 메시지 정합 방법
Kamb Extending Fluke IPC for transparent remote communication
JP2000151739A (ja) 情報処理装置、分散処理装置およびネットワークシステム
Martins et al. A Unix distributed application support suitable for mini and microcomputer based systems
Sathe et al. Client server design and implementation issues in the accelerator control system environment
Parr Data Transport Subsystem: The SFOC Glue
Hartman et al. Janus/Ada implementation of a star cluster network of personal computers with interface to an EHTERNET LAN allowing access to DDN resources
Racine Transparent Ada rendezvous in a fault tolerant distributed system
Westall et al. An Architectural and Owner's Manual
Westall et al. MicroCIM: An Architectural and Owner's Manual.

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

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR GB IT

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): DE FR GB IT

17P Request for examination filed

Effective date: 19960229

17Q First examination report despatched

Effective date: 20000126

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: EMHART GLASS S.A.

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Designated state(s): DE FR GB IT

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: EMHART GLASS S.A.

REF Corresponds to:

Ref document number: 69530947

Country of ref document: DE

Date of ref document: 20030710

Kind code of ref document: P

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

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

Ref country code: IT

Payment date: 20080228

Year of fee payment: 14

Ref country code: GB

Payment date: 20080227

Year of fee payment: 14

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

Ref country code: FR

Payment date: 20080218

Year of fee payment: 14

Ref country code: DE

Payment date: 20080331

Year of fee payment: 14

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

Effective date: 20090214

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20091030

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

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

Ref country code: FR

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

Effective date: 20090302

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