EP3140741A1 - Procédé et dispositif de transformation d'un concept de transaction pour le protocole opc ua au moyen d'un mécanisme de délai imparti écoulé - Google Patents

Procédé et dispositif de transformation d'un concept de transaction pour le protocole opc ua au moyen d'un mécanisme de délai imparti écoulé

Info

Publication number
EP3140741A1
EP3140741A1 EP14735499.7A EP14735499A EP3140741A1 EP 3140741 A1 EP3140741 A1 EP 3140741A1 EP 14735499 A EP14735499 A EP 14735499A EP 3140741 A1 EP3140741 A1 EP 3140741A1
Authority
EP
European Patent Office
Prior art keywords
opc
server
call
client
open
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.)
Withdrawn
Application number
EP14735499.7A
Other languages
German (de)
English (en)
Inventor
Karl-Heinz Deiretsbacher
Markus Erlmann
Sven Kerschbaum
Frank Volkmann
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.)
Siemens AG
Original Assignee
Siemens AG
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 Siemens AG filed Critical Siemens AG
Publication of EP3140741A1 publication Critical patent/EP3140741A1/fr
Withdrawn legal-status Critical Current

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
    • 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
    • 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

Dans l'en-tête de demande d'un protocole OPC UA, il existe le champ « TimeoutHint » avec lequel le client peut indiquer quand il n'est plus intéressé par le résultat d'une opération. Lorsque ce temps est écoulé, le serveur envoie une réponse précisant que l'exécution de l'opération a été interrompue. Selon l'invention, la sémantique du champ « TimeoutHint » dans l'en-tête de demande du protocole OPC UA est employée de manière différente. La signification du champ « TimeoutHint » est modifiée de sorte qu'il n'indique plus l'instant le plus tardif auquel une opération doit être exécutée, mais au contraire l'instant le plus précoce.
EP14735499.7A 2014-06-25 2014-06-25 Procédé et dispositif de transformation d'un concept de transaction pour le protocole opc ua au moyen d'un mécanisme de délai imparti écoulé Withdrawn EP3140741A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2014/063376 WO2015197115A1 (fr) 2014-06-25 2014-06-25 Procédé et dispositif de transformation d'un concept de transaction pour le protocole opc ua au moyen d'un mécanisme de délai imparti écoulé

Publications (1)

Publication Number Publication Date
EP3140741A1 true EP3140741A1 (fr) 2017-03-15

Family

ID=51063412

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14735499.7A Withdrawn EP3140741A1 (fr) 2014-06-25 2014-06-25 Procédé et dispositif de transformation d'un concept de transaction pour le protocole opc ua au moyen d'un mécanisme de délai imparti écoulé

Country Status (5)

Country Link
US (1) US20170161122A1 (fr)
EP (1) EP3140741A1 (fr)
CN (1) CN106462473A (fr)
RU (1) RU2676423C2 (fr)
WO (1) WO2015197115A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017092879A1 (fr) 2015-11-30 2017-06-08 Siemens Aktiengesellschaft Procédé de communication industrielle par protocole tsn
CN107920120A (zh) * 2017-11-22 2018-04-17 北京小米移动软件有限公司 业务处理方法、装置及计算机可读存储介质
DE102018101203A1 (de) * 2018-01-19 2019-07-25 Wago Verwaltungsgesellschaft Mbh Automatisierungsgerät und Verfahren zum optimierten Zugriff auf eine Variable

Family Cites Families (17)

* Cited by examiner, † Cited by third party
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 (fr) * 2001-06-22 2003-01-03 Wonderware Corporation Application de systeme d'information de fabrication et de commande de processus de supervision, a modele de composant extensible
JP2005531826A (ja) * 2002-03-01 2005-10-20 フィッシャー−ローズマウント システムズ， インコーポレイテッド プロセス・プラントにおける統合警告発生方法
DE60205729T8 (de) * 2002-06-04 2007-04-12 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 (fr) * 2005-07-06 2007-01-11 Luke19 Co., Ltd. Système de gestion de fourniture d’échantillons gratuits, serveur de gestion de fourniture d’échantillons gratuits, et procédé de gestion de fourniture d’échantillons gratuits
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
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
DE102007062986B4 (de) * 2007-12-21 2013-12-24 Abb Research Ltd. Verfahren und Einrichtung zur Client-Server-Kommunikation gemäß dem Standardprotokoll OPC UA
US9106678B2 (en) * 2010-05-25 2015-08-11 Siemens Aktiengesellschaft Method and apparatus for interchanging data between two devices in an automation network
EP2559221B1 (fr) * 2010-05-25 2015-04-01 Siemens Aktiengesellschaft Procédé et dispositif d'échange de données ainsi que réseau
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

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO2015197115A1 *

Also Published As

Publication number Publication date
US20170161122A1 (en) 2017-06-08
RU2017102174A3 (fr) 2018-07-25
RU2676423C2 (ru) 2018-12-28
RU2017102174A (ru) 2018-07-25
WO2015197115A1 (fr) 2015-12-30
CN106462473A (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
DE102007062986B4 (de) Verfahren und Einrichtung zur Client-Server-Kommunikation gemäß dem Standardprotokoll OPC UA
EP3137999B1 (fr) Procédé et dispositif d'extension de transaction pour une session opc ua
EP1430369B1 (fr) Acces dynamique a des ressources d'automatisation
DE102008014153B4 (de) Verfahren, Steuergerät und Steuerungssystem zur Steuerung eines Automatisierungssystems
WO2015197115A1 (fr) Procédé et dispositif de transformation d'un concept de transaction pour le protocole opc ua au moyen d'un mécanisme de délai imparti écoulé
DE102006028309A1 (de) Mehrseitiges, gemeinschaftliches Verwenden von dynamischen Daten in einer drahtlosen Testumgebung
EP2226693A1 (fr) Appareil de programmation destiné à la projection d'une liaison de communication entre des composants d'automatisation dans un agencement d'automatisation industriel
WO2016188731A1 (fr) Entretien de machines dans l'industrie des boissons
WO2015169355A1 (fr) Procédé et dispositif pour des opérations ensemblistes cohérentes d'appels opc ua à données changeantes
DE102013211080A1 (de) Verfahren zur Steuerung eines Kraftfahrzeuggetriebes
EP2283426A1 (fr) Procédé et dispositif permettant de corriger des informations transmises sous forme numérique
WO2010149440A1 (fr) Procédé de détermination d'une longueur de données d'un message télégraphique transmissible
EP2645630B1 (fr) Protocole de service à distance adaptatif
DE10246895B3 (de) Verfahren zur Änderung eines Parameters für den Betrieb eines Netzwerks sowie Teilnehmer zur Durchführung des Verfahrens
EP3800864B1 (fr) Procédé de configuration d'un participant opc ua pubsub, système d'automatisation, programme informatique et support lisible par ordinateur
WO2007118642A2 (fr) Procédé permettant de contrôler la conformité, l'interopérabilité et les performances de dispositifs aux normes bacnet
EP3836489B1 (fr) Attribution dynamique d'unités d'automatisation aux serveurs d'automatisation
EP1703667A1 (fr) Gestion de réseau en utilisant une méthode de type maître-réplique
DE102021210453A1 (de) Steuergerät, system und verfahren zum konfigurieren von geräten eines feldbusnetzwerks
EP1435026A2 (fr) Systeme et procede d'emission de donnees d'un appareil, en particulier d'un appareil d'automatisation, par l'intermediaire d'une interface normalisee avec remplacement de variables par l'intermediaire d'un serveur echo
EP4216489A1 (fr) Procédé de modification d'une clé d'accès réelle dans un appareil de terrain de la technique d'automatisation
DE10353532A1 (de) Verfahren und Vorrichtung zur Übertragung von Daten
DE102006062093B4 (de) Automatisierungsanlage und Verfahren für exklusive Verbindungen zu Clientrechnern
DE102017108506A1 (de) MIB-orientiertes Protokoll für hochwirksame http-Verwaltungsprozeduren
DE10036686A1 (de) Verfahren zum Konfigurieren einer Netzschnittstelle sowie Netzelement

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20200212

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200519

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20200930