WO2015197115A1 - Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus - Google Patents
Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus Download PDFInfo
- Publication number
- WO2015197115A1 WO2015197115A1 PCT/EP2014/063376 EP2014063376W WO2015197115A1 WO 2015197115 A1 WO2015197115 A1 WO 2015197115A1 EP 2014063376 W EP2014063376 W EP 2014063376W WO 2015197115 A1 WO2015197115 A1 WO 2015197115A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- opc
- server
- call
- client
- open
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1881—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with schedule organisation, e.g. priority, sequence management
-
- 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
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/34—Director, elements to supervisory
- G05B2219/34263—OLE object linking and embedding, OPC ole for process control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/541—Client-server
Definitions
- OPC UA OPC Unified Architecture
- OPC Foundation OPC Foundation for vendor-independent communication for the exchange of machine data, especially in process automation.
- OPC UA is a relatively new standard, where the original focus was not on the control of an industrial plant, but rather on the standardized exchange of information, especially between devices from different manufacturers.
- OPC UA is also integrated directly into automation devices, creating the need for consistent data writing.
- process information such as process values, measured values, parameters, control commands
- process information such as process values, measured values, parameters, control commands
- variables are considered individually (even within a write call, a so-called WRITE call, with several variables);
- the server informs the client about individual status codes (per variable).
- Other options are not provided in the specification.
- the information model specified by OPC UA is no longer just a hierarchy of folders, items, and properties. It is a so-called full mesh network of nodes that, in addition to the payload of a node, also represents meta and diagnostic information.
- a node is similar to an object from object-oriented programming.
- a node can have attributes that can be read (Data Access DA, Historical Data Access HDA). It is possible to define and call methods.
- a method has call arguments and return values. It is called by a command.
- events that can be sent (AE, DA DataChange) are supported in order to exchange certain information between devices. An event has among other things a time of reception, a message and a severity level.
- AE DA DataChange
- Nodes are used for both payload and all other types of metadata.
- the modeled OPC address space now includes a type model that specifies all data types.
- a client and a server could agree that the server perceives a write call as just one consistent write and only accepts or rejects this call as a whole.
- client and server are tailored to each other.
- Client and server must exchange the information that they are tailored to each other, d. H. this information must be z. B. in the log.
- a method for communication between an OPC UA client and an OPC UA server is required
- Client / server system using the OPC-UA communication protocol calls being used to interact with the client with the OPC-UA server.
- the execution of the OPC-UA calls is thereby to be carried out transaction-based, wherein the OPC-UA calls contain an indication of an earliest time of execution of the OPC-UA call on the server and the at least one OPC-UA call is received by the server and initially saved.
- the "TimeoutHint" field exists in the OPC UA request header, with which the client can specify when it is no longer interested in the result of an operation or the duration after which the server is allowed to delete a message (presumably "circulating").
- the server sends a response that the operation was aborted.
- the semantics of the "TimeoutHint" field in the OPC UA request header are used differently than originally provided in the standard.
- the meaning of the "TimeoutHint” is changed so that it no longer specifies the latest time at which an operation is executed should be, but the earliest.
- This mechanism allows multiple operations to be stored in the server, which are then executed concurrently upon the arrival of the trigger.
- the information provided by the client in the "TimeoutHints" and timestamps must correlate to define an exact execution time.
- a first advantageous embodiment operates in a "delayed response" mode.
- the server keeps the requests until the trigger arrives and only gives the client an answer when either the time period specified in "TimeoutHint" has expired or when a suitable trigger is sent by the client.
- the client has the client its own status code for each item that it modifies.
- the response to the trigger that goes from the server to the client contains the overall result of the operation.
- the responses with the detail information are also sent to the previously collected requests to the client.
- the operations are formally checked when they arrive on the server (for example, the desired network nodes exist).
- the client In the event of an error, the client immediately receives a response with the information about the formal errors that have occurred.
- the preview mode is presented as a second advantageous embodiment.
- the client receives for each stored operation immediately, d. H. not only after the arrival of the trigger, a response from the server about the expected outcome of the operation, irrespective of whether the operation is successful or not. So he gets a preview of what would happen if the operations were done.
- the client determines that one of the operations performed would not produce the desired result, it can discard the operations by not sending a trigger. If the client wants the operations to be executed, it sends the trigger. In response to the trigger, the client receives the information about the overall result of all executed operations. In an advantageous embodiment, the actual detailed results of the executed operations can be sent by the server via the event mechanism.
- the client can prematurely abort the operation via an abort message. He does not have to wait for the timeout.
- the execution time may advantageously be set either over a time notified by means of the trigger operation or over the timeout time of the preceding operations.
- time-out mechanism is an easy way to implement and manage operations in a single transaction.
- the complex management of a transaction by transaction contexts, etc. is eliminated, since the cohesion of operations is synchronized over a time.
- the OPC UA protocol does not have to be changed.
- the client and server must have the same understanding of how to use the TimeoutHint field. on this can z. B. be replaced in the connection setup.
- FIG. 1 shows an exemplary application of the invention in the automation environment
- FIG. 2 shows an exemplary communication between client and server according to the first exemplary embodiment
- Figure 3 shows an exemplary communication between client and server according to the second embodiment
- FIG. 4 shows another exemplary communication with simulated intermediate results.
- the exemplary task which the automation system is to perform is the mixing of green color from yellow and blue liquids, see FIG. 1.
- valves VI, V2 must be opened simultaneously from the yellow and blue tanks. Now, if the following error occurs that one of the valves VI, V2 can not be properly opened or closed, V3, V4, first all open inlet valves VI, V2 must be closed again, and then open the mixing tank G, the valve V4 in the direction of disposal R. to dispose of the collected liquid.
- the control of the servers UA-Sl, UA-S2 and UA-S3 is performed by the client UA-C.
- FIGS. 1-10 Exemplary communication processes between client UA-C and servers UA-Sl, UA-S2, UA-S3 according to the invention are now shown in FIGS.
- Figure 2 shows a communication in which the execution of the operations is triggered by a trigger.
- a client UA-C sends a first operation "open valve blue",
- the server UA-S first formally checks the validity of the operation. In the event of an error, a corresponding message is sent to the client. Otherwise, the operation is stored in the server.
- Client UA-C sends a second operation "Open Valve Yellow", 02 (OPEN_V2, T) to server UA-S at the same timeout point T.
- the validity of the operation 02 is formally checked again after reception of the second operation 02 by the server. In the event of an error, a corresponding message is sent to the client. Otherwise, the operation is also stored in the server.
- the client UA-C If the client UA-C now wants to perform the two operations, it sends the trigger message TRIGGER (T) to the server UA-S.
- the server carries out the operations and sends a response RESULT (01, 02) to the client for confirmation back.
- FIG. 3 initially shows the same procedure:
- Figure 4 shows yet another embodiment.
- the server UA-S After receiving the first operation 01 (OPEN_Vl, T), the server UA-S optionally checks formally the validity of the operation and then simulates the requested operation.
- the client UA-C receives in response to the operation the result of this simulation as a preview, SIM_RESULT (Ol).
- SIM_RESULT The actual result of the operation can not be delivered to the client later because it has already received the response to the request.
- the server UA-S After receiving the second operation 02 (OPEN_V2, T), the server UA-S formally checks the validity of the operation and "simulates" the operation 02.
- the client UA-C receives in response to the operation the result of this simulation as a preview, SIM_RESULT (FIG. 02) It is no longer possible to deliver the actual result of the operation to the client UA-C since it has already received the response to the request.
- the client UA-C may abort the overall operation by elapsing the timeout period.
- the execution time can be set by the client UA-C either by the timeout time or by a time T delivered with the trigger.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14735499.7A EP3140741A1 (de) | 2014-06-25 | 2014-06-25 | Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus |
RU2017102174A RU2676423C2 (ru) | 2014-06-25 | 2014-06-25 | Способ и устройство для реализации концепции транзакций в opc ua посредством механизма таймаута |
PCT/EP2014/063376 WO2015197115A1 (de) | 2014-06-25 | 2014-06-25 | Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus |
CN201480080128.1A CN106462473A (zh) | 2014-06-25 | 2014-06-25 | 用于借助超时机制在opc ua中转换事务概念的装置和方法 |
US15/322,019 US20170161122A1 (en) | 2014-06-25 | 2014-06-25 | Method and device for implementing a transaction concept in opc ua by means of a timeout mechanism |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2014/063376 WO2015197115A1 (de) | 2014-06-25 | 2014-06-25 | Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015197115A1 true WO2015197115A1 (de) | 2015-12-30 |
Family
ID=51063412
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2014/063376 WO2015197115A1 (de) | 2014-06-25 | 2014-06-25 | Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus |
Country Status (5)
Country | Link |
---|---|
US (1) | US20170161122A1 (de) |
EP (1) | EP3140741A1 (de) |
CN (1) | CN106462473A (de) |
RU (1) | RU2676423C2 (de) |
WO (1) | WO2015197115A1 (de) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017092879A1 (de) | 2015-11-30 | 2017-06-08 | Siemens Aktiengesellschaft | Verfahren zur industriellen kommunikation über tsn |
CN107920120A (zh) * | 2017-11-22 | 2018-04-17 | 北京小米移动软件有限公司 | 业务处理方法、装置及计算机可读存储介质 |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6122673A (en) * | 1998-07-22 | 2000-09-19 | Fore Systems, Inc. | Port scheduler and method for scheduling service providing guarantees, hierarchical rate limiting with/without overbooking capability |
WO2003001343A2 (en) * | 2001-06-22 | 2003-01-03 | Wonderware Corporation | Supervisory process control and manufacturing information system application having an extensible component model |
JP2005531826A (ja) * | 2002-03-01 | 2005-10-20 | フィッシャー−ローズマウント システムズ, インコーポレイテッド | プロセス・プラントにおける統合警告発生方法 |
EP1372346B8 (de) * | 2002-06-04 | 2006-06-14 | Telefonaktiebolaget LM Ericsson (publ) | Betrieb eines Vermittlungsknotens in einem Kommunikationsnetz mit sowohl einer geschichteten als auch einer nicht-geschichteten Architekturumgebung |
US7496668B2 (en) * | 2002-06-28 | 2009-02-24 | Honeywell International Inc. | OPC server redirection manager |
US7152111B2 (en) * | 2002-08-15 | 2006-12-19 | Digi International Inc. | Method and apparatus for a client connection manager |
US8942834B2 (en) * | 2005-06-27 | 2015-01-27 | Rockwell Automation Technologies, Inc. | Method and apparatus for communicating transactions between an industrial controller and a programming interface |
WO2007004310A1 (ja) * | 2005-07-06 | 2007-01-11 | Luke19 Co., Ltd. | 試供品提供管理システム及び、試供品提供管理サーバ、試供品提供管理方法 |
US20070027913A1 (en) * | 2005-07-26 | 2007-02-01 | Invensys Systems, Inc. | System and method for retrieving information from a supervisory control manufacturing/production database |
US8782249B1 (en) * | 2006-09-28 | 2014-07-15 | Rockwell Automation Technologies, Inc. | Message engine |
US8195581B2 (en) * | 2007-05-21 | 2012-06-05 | Honeywell Asca Inc. | Apparatus and method for simulating multi-dimensional non-linear multivariable processes |
DE102007062986B4 (de) * | 2007-12-21 | 2013-12-24 | Abb Research Ltd. | Verfahren und Einrichtung zur Client-Server-Kommunikation gemäß dem Standardprotokoll OPC UA |
DE102007062985B4 (de) * | 2007-12-21 | 2014-01-02 | Abb Research Ltd. | Verfahren und Einrichtung zur Kommunikation gemäß dem Standardprotokoll OPC UA in einem Client-Server-System |
CN102907070B (zh) * | 2010-05-25 | 2015-06-17 | 西门子公司 | 用于交换数据的方法和装置,以及网络 |
US9106678B2 (en) * | 2010-05-25 | 2015-08-11 | Siemens Aktiengesellschaft | Method and apparatus for interchanging data between two devices in an automation network |
US20140095658A1 (en) * | 2012-10-02 | 2014-04-03 | Transocean Sedco Forex Ventures Limited | Information Aggregation on a Mobile Offshore Drilling Unit |
US9842134B2 (en) * | 2014-12-12 | 2017-12-12 | Schneider Electric Software, Llc | Data query interface system in an event historian |
-
2014
- 2014-06-25 CN CN201480080128.1A patent/CN106462473A/zh active Pending
- 2014-06-25 RU RU2017102174A patent/RU2676423C2/ru not_active IP Right Cessation
- 2014-06-25 WO PCT/EP2014/063376 patent/WO2015197115A1/de active Application Filing
- 2014-06-25 EP EP14735499.7A patent/EP3140741A1/de not_active Withdrawn
- 2014-06-25 US US15/322,019 patent/US20170161122A1/en not_active Abandoned
Non-Patent Citations (3)
Title |
---|
OPC FOUNDATION: "OPC Unified Architecture Specification - Part 4: Services - Release Candidate 1.01.30", 10 March 2008 (2008-03-10), XP002728532, Retrieved from the Internet <URL:http://web24267.5udns.cn/attachment.aspx?attachmentid=658> [retrieved on 20140815] * |
WIKIPEDIA: "OPC Unified Architecture", 12 October 2013 (2013-10-12), XP002728079, Retrieved from the Internet <URL:http://de.wikipedia.org/wiki/OPC_Unified_Architecture> [retrieved on 20140731] * |
WOLFGANG MAHNKE, STEFAN-HELMUT LEITNER, MATTHIAS DAMM: "OPC Unified Architecture", 19 March 2009, SPRINGER VERLAG, Berlin Heidelberg, ISBN: 978-3-540-68898-3, XP002728533 * |
Also Published As
Publication number | Publication date |
---|---|
EP3140741A1 (de) | 2017-03-15 |
CN106462473A (zh) | 2017-02-22 |
RU2676423C2 (ru) | 2018-12-28 |
RU2017102174A3 (de) | 2018-07-25 |
RU2017102174A (ru) | 2018-07-25 |
US20170161122A1 (en) | 2017-06-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE102007062986B4 (de) | Verfahren und Einrichtung zur Client-Server-Kommunikation gemäß dem Standardprotokoll OPC UA | |
EP3137999B1 (de) | Verfahren und vorrichtung zur transaktionserweiterung bei opc ua | |
DE102008014153B4 (de) | Verfahren, Steuergerät und Steuerungssystem zur Steuerung eines Automatisierungssystems | |
EP1430369B1 (de) | Dynamischer zugriff auf automatisierungsressourcen | |
DE102006028309A1 (de) | Mehrseitiges, gemeinschaftliches Verwenden von dynamischen Daten in einer drahtlosen Testumgebung | |
DE102004017529A1 (de) | Automatisierungsnetzwerk sowie Automatisierungsgerät, Netzwerkkomponente und Feldgerät für ein derartiges Netzwerk | |
WO2015197115A1 (de) | Verfahren und vorrichtung zur umsetzung eines transaktionskonzepts bei opc ua mittels time-out mechanismus | |
WO2016188731A1 (de) | Maschinenwartung in der getränkemittelindustrie | |
EP3200034A1 (de) | Verfahren und vorrichtung zum zugriff auf daten oder funktionen einer speicherprogrammierbaren steuerung mittels eines webdientes | |
DE112013003240B4 (de) | Verfahren zur Steuerung eines Kraftfahrzeuggetriebes | |
WO2015169355A1 (de) | Verfahren und vorrichtung für konsistente mengenoperationen datenverändernder opc ua aufrufe | |
EP2226693A1 (de) | Programmiergerät zur Projektierung einer Kommunikationsverbindung zwischen Automatisierungskomponenten in einer industriellen Automatisierungsanordnung | |
DE602005000715T2 (de) | System und Verfahren zur Auswahl einer aktiven Verbindung | |
CH686540A5 (de) | Verfahren zum Steuern und Verwalten von Netzwerkelementen. | |
EP2283426A1 (de) | Verfahren und vorrichtung zur korrektur von digital übertragenen informationen | |
WO2010149440A1 (de) | Verfahren zum ermitteln einer übermittelbaren telegramm-datenlänge | |
DE10246895B3 (de) | Verfahren zur Änderung eines Parameters für den Betrieb eines Netzwerks sowie Teilnehmer zur Durchführung des Verfahrens | |
WO2007118642A2 (de) | Verfahren zur prüfung von bacnet-einrichtungen auf konformität, interoperabilität und performance | |
EP3836489B1 (de) | Dynamische zuordnung von automatisierungseinheiten zu automatisierungsservern | |
EP1703667A1 (de) | Netzwerkmanagement unter Verwendung eines Master-Replica-Verfahrens | |
EP1435026A2 (de) | System und verfahren zur datenausgabe eines geräts, insbesondere eines automatisierungsgerät über eine standardisierte schnittstelle mit variablenersetzung über einen echoserver | |
EP4216489A1 (de) | Verfahren zur änderung eines ist-zugangsschlüssels in einem feldgerät der automatisierungstechnik | |
WO2023156060A1 (de) | Verfahren zur automatisierten verifizierung von anforderungsspezifikationen eines technischen prozesses | |
DE10353532A1 (de) | Verfahren und Vorrichtung zur Übertragung von Daten | |
WO2021063596A1 (de) | Verfahren zum konfigurieren eines opc ua pubsub teilnehmers, automatisierungssystem, computerprogramm und computerlesbares medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14735499 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2014735499 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014735499 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15322019 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2017102174 Country of ref document: RU Kind code of ref document: A |