WO2007137531A1 - Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé - Google Patents

Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé Download PDF

Info

Publication number
WO2007137531A1
WO2007137531A1 PCT/DE2006/000910 DE2006000910W WO2007137531A1 WO 2007137531 A1 WO2007137531 A1 WO 2007137531A1 DE 2006000910 W DE2006000910 W DE 2006000910W WO 2007137531 A1 WO2007137531 A1 WO 2007137531A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
communication
remote communication
identifier
ipv4
Prior art date
Application number
PCT/DE2006/000910
Other languages
German (de)
English (en)
Inventor
Markus Erlmann
Thomas Talanis
Original Assignee
Siemens Aktiengesellschaft
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 Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Priority to DE112006003973T priority Critical patent/DE112006003973A5/de
Priority to EP06742387A priority patent/EP2022241A1/fr
Priority to PCT/DE2006/000910 priority patent/WO2007137531A1/fr
Publication of WO2007137531A1 publication Critical patent/WO2007137531A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6

Definitions

  • the invention relates to a method for operating an automation device, which is for communicating with at least one other remote communication subscriber, e.g. other automation devices, suitable or intended.
  • the communication between the automation device and the remote communication subscriber takes place in a manner known per se on the basis of at least one address identifying the or each remote communication subscriber.
  • an address which identifies the automation device is additionally used in the communication.
  • IPv4 This address format is commonly and also referred to below as IPv4.
  • IPv4 address A corresponding address is referred to below as the IPv4 address.
  • IPv ⁇ address format To increase the address space, a generally and also referred to as IPv ⁇ address format is proposed, with the 2 128 unique addresses are possible.
  • IPv4 to IPv6 or more generally in the transition from a common addressing standard to a subsequent addressing standard, the problem is that existing applications provide for standard-address addressing, whereas it would be desirable for actual communication to be addressed after that future standard.
  • the identifier identifying the respective remote communication user is, for example, another address, ie, for example, an address according to a common standard, which, however, should no longer be used for the actual communication if possible.
  • the identifier can also be any other unique or at least locally unique referencing of the remote communication user.
  • an address actually to be used for communication is determined. Once such an address is determined, it is used in or for communication with the remote communication subscriber.
  • the identifier identifying the or each remote communication user is either stored in the automation device or kept in a further device communicatively connected to the automation device.
  • data belong to so-called configuration data, in which the automation devices required for this purpose and thus far involved are entered for a specific automation solution, such entries comprising at least one identifier of the respective automation devices.
  • configuration data can also be understood as a locally unique referencing of the participating automation devices or other communication users in which, for example, it suffices to number the participating devices starting from a predetermined or predefinable start value.
  • the determination of the address which can be used for communication with the respective remote communication user preferably includes calling a conversion device, the conversion device being transmitted the identifier, and the conversion device determining and returning the address on the basis of the identifier.
  • a conversion device is a so-called DNS server or the local implementation of the known functionality of such a DNS server.
  • IPv6 address that is, an address for a future one Standard usable, although applications running on the automation device for controlling and / or monitoring a technical process may not currently be provided for using these addresses and instead provide addresses according to the currently used standard, ie IPv4.
  • the identifier transmitted to the conversion device can also be a so-called hash value generated to an IPv4 address or associated with the IPv4 address.
  • Hash values and their use are known per se and are used for the unique referencing of a large number of elements in a superordinate set, in the present case for the unique referencing of a large number of IPv4 addresses in the address space according to IPv4.
  • a check of the remote communication subscriber is then carried out, whether a communication based on the identifier, ie in particular the IPv4 address possible is if the translator does not return an IPv6 address. In this case, it is also possible to start the communication with the remote communication subscriber if an IPv6 address is not available to the remote communication subscriber.
  • the invention also relates to a computer program with computer executable program code instructions for implementing the method described above when the computer program is executed on a computer.
  • the invention also relates to a computer program product, in particular a storage medium, such as a computer-readable data carrier, e.g. a floppy disk or a semiconductor memory, with one by a computer, e.g. the automation device or a processing unit, such as one
  • Microprocessor of the automation device executable such computer program.
  • the invention also relates to an automation device with means, in particular program code means, namely in particular such a computer program, for carrying out the method described above.
  • 1 shows an automation system for implementing an automation solution with an automation device
  • FIG. 2 shows a database comprising a configuration data
  • FIG. 3 shows an approach according to the invention in a flow chart.
  • FIG. 1 shows, in a schematically simplified manner, an automation system provided for implementing an automation solution.
  • System 10 with an automation device 12 and other automation devices 14, 16, 18, one of which is referred to below as a remote communication participant 20 for distinction.
  • the automation devices 12- 18 are generally also referred to as communication subscribers and are communicatively connected to one another via a bus 22, for example a so-called field bus, in particular a PROFINET field bus.
  • a bus 22 for communication between the communication subscribers, an address 24, 26, 28, 30 assigned to each communication subscriber is provided in a manner known per se, the respective communication subscriber then receiving data transmitted via the bus 22 if a respective message at least addresses its address 24-30 and the telegram insofar as it is certainly distinguished for the respective communication subscriber.
  • a communicative connection to further communication participants 32, 34, 36 may also be provided in which these are e.g. can be reached via an intranet or the Internet 38.
  • the configuration data 42 designate, for example, the automation devices 12-18 combined in the automation system 10 (FIG. 1) so that each automation device 12-18 belonging to the automation system 10 can receive information about which other automation devices 12-18 are involved in the automation system 10 ,
  • the configuration data 42 include at least one identifier that references the respective automation devices 12-18.
  • the configuration data 42 for such a referencing comprise the addresses 24-30 of the respective automation devices 12-18.
  • a first automation device 12 which in the following is referred to as the automation device 12 for short, intends to record a communication with another communication user, eg another automation device 14-18, eg the remote communication user 20, then Configuration data 42 whose address 30 are looked up and the data provided for transmission are given to bus 22 with this address 30.
  • the configuration data 42 have a predefined layout and, to that extent, refer to the respective automation devices 12-18, e.g. the deposit of an address 24-30 of the respective programmable controller 12-18, which corresponds to a specific address format, e.g. IPv4, equivalent. If the automation device 12 wants to communicate with the remote communication user 20, then only the address in the customary format is available via the configuration data 42.
  • a specific address format e.g. IPv4, equivalent.
  • a first block 46 represents a user program, for example, on the automation device 12 (FIG 1) for controlling and / or monitoring a not closer provided technical process or sub-process is provided.
  • the user program calls a communication routine provided for this purpose and in particular likewise implemented on the automation device 12, for example a so-called IP stack, which is illustrated in FIG. 3 by a second block 48.
  • the user program of the communication routine transmits the respective data to be transferred and an identifier for the communication user to whom these data are to be sent, ie usually an address or the like, eg an address 24-30 based on the configuration data 42 (FIG.
  • a communication with the remote communication user 20 ie, for example, its address 30.
  • the transmitted identifier is an address in the format to be used for the communication, eg an IPv6 address. If this is the case, the transferred identifier is used as the address for the communication via a direct branch 52 (third block 54) and the communication with the remote communication subscriber 20 (FIG. 1) is established (fourth block 56).
  • the result is a second branch 58 as a result of the first case distinction 50 branched.
  • a second case distinction 60 it is first checked whether a hash value is required for the transmitted identifier. If this is the case, a hash value for the transmitted identifier is generated in a third branch 62 or a hash value associated with the transmitted identifier is looked up (fifth block 64).
  • the result of the second case distinction 60 is continued in the second branch 58 and the transmitted identifier for the determination in the second branch 58 of a is used as the basis for communication with the remote communication subscriber 20 (sixth block 66).
  • the address to be used for the communication is determined in a seventh block 68 either on the basis of the identifier (sixth block 66) or on the basis of the hash value (fifth block 64) generated for the identifier.
  • This determination of an address to be used for the communication comprises access to a conversion device 70, which can be implemented, for example, as a DNS server or, in the case of a local implementation with a manageable set of identifiers, as a look-up table or the like and the input receives the identifier or the hash value assigned to the identifier and returns the address to be used for the communication as the output.
  • a conversion device 70 which can be implemented, for example, as a DNS server or, in the case of a local implementation with a manageable set of identifiers, as a look-up table or the like and the input receives the identifier or the hash value assigned to the identifier and returns the address to be used for the communication as the output.
  • a third case decision 72 it is checked whether the address returned by the conversion device 70 corresponds to an expected format, that is to say, for example, whether it is an address in IPv6 format. If this is the case, in continuation of the second branch 58, the received address is used as the address
  • a fourth case distinction 74 checks whether the remote communication user 20 is also addressable with or based on the identifier. This is the case, in particular, when the remote communication subscriber 20 is a communication subscriber who is provided for a so-called dual-stack processing, that is, for example, data in both an addressing in an IPv4 format and in an addressing in an IPv6 format.
  • the original identifier eg, the IPv4 address used as the identifier, is used for communication (third block 54) and the connection is established (fourth block 56).
  • the invention relates to a method for operating an automation device 12, in which, in connection with or prior to the establishment of a communication to a remote communication user 20, an address which can be used for communication with this remote communication user 20 is determined on the basis of an identifier identifying the respective remote communication participant 20
  • the identifier is in particular an address in an IPv4 format
  • the address which can be used for communication with the remote communication subscriber 20 is in particular an address in an IPv6 format, so that also transparent for automation devices and Applications that were previously provided only for the processing of address data in a previously common format, ie in particular the IPv4 format, a transparent migration to a future address format, ie in particular IPv ⁇ , is possible.

Abstract

L'invention concerne un procédé de fonctionnement d'un appareil d'automatisation (12), dans lequel, en lien avec ou avant l'établissement d'une communication vers un abonné de communication (20) éloigné, une adresse utilisable pour la communication avec cet abonné de communication éloigné (20) est déterminée au moyen d'un code identifiant l'abonné de communication (20) éloigné respectif. Selon ce procédé, il s'agit, pour le code, en particulier d'une adresse au format IPv4 et pour l'adresse utilisable pour la communication avec l'abonné de communication (20) éloigné, d'une adresse au format IPv6, de sorte qu'une migration transparente dans un futur format d'adresse, donc en particulier le format IPv6, est possible de manière transparente également pour les appareils d'automatisation et les applications qui sont prévues jusqu'à présent uniquement pour le traitement des données d'adresse dans un format jusqu'à présent usuel, donc en particulier le format IPv4.
PCT/DE2006/000910 2006-05-26 2006-05-26 Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé WO2007137531A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
DE112006003973T DE112006003973A5 (de) 2006-05-26 2006-05-26 Verfahren zum Betrieb eines Automatisierungsgerätes sowie korrespondierendes Computerprogramm, Computerprogrammprodukt und Automatisierungsgerät
EP06742387A EP2022241A1 (fr) 2006-05-26 2006-05-26 Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé
PCT/DE2006/000910 WO2007137531A1 (fr) 2006-05-26 2006-05-26 Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/DE2006/000910 WO2007137531A1 (fr) 2006-05-26 2006-05-26 Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé

Publications (1)

Publication Number Publication Date
WO2007137531A1 true WO2007137531A1 (fr) 2007-12-06

Family

ID=37668274

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2006/000910 WO2007137531A1 (fr) 2006-05-26 2006-05-26 Procédé permettant de faire fonctionner un appareil d'automatisation, et programme informatique correspondant, programme informatique et appareil d'automatisation associé

Country Status (3)

Country Link
EP (1) EP2022241A1 (fr)
DE (1) DE112006003973A5 (fr)
WO (1) WO2007137531A1 (fr)

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
COX R ET AL: "Serving DNS Using a Peer-to-Peer Lookup Service", LECTURE NOTES IN COMPUTER SCIENCE; PEER-TO-PEER SYSTEMS: FIRST INTERNATIONALWORKSHOP, IPTPS 2002 CAMBRIDGE, MA, USA, MARCH 7-8, 2002, vol. 2429/2002, 7 March 2002 (2002-03-07), Springer Berlin / Heidelberg, pages 155 - 165, XP002417171, Retrieved from the Internet <URL:http://www.springerlink.com/content/ba8e6p26wbxq8gbc/fulltext.pdf> [retrieved on 20070129] *
CRAWFORD FERMILAB B HABERMAN M ET AL: "IPv6 Node Information Queries", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, vol. ipngwg, no. 15, 13 February 2006 (2006-02-13), XP015043778, ISSN: 0000-0004 *
GILLIGAN INTRANSA R ET AL: "Basic Socket Interface Extensions for IPv6", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, February 2003 (2003-02-01), XP015009276, ISSN: 0000-0003 *
M-K SHIN ET AL: "Application Aspects of IPv6 Transition", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, March 2005 (2005-03-01), XP015041961, ISSN: 0000-0003 *
TSIRTSIS BT P SRISURESH CAMPIO COMMUNICATIONS G: "Network Address Translation - Protocol Translation (NAT-PT)", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, February 2000 (2000-02-01), XP015008549, ISSN: 0000-0003 *

Also Published As

Publication number Publication date
DE112006003973A5 (de) 2009-04-30
EP2022241A1 (fr) 2009-02-11

Similar Documents

Publication Publication Date Title
EP1309920B1 (fr) Procede d&#39;adressage pour au moins un dispositif de bus nouvellement raccorde a un systeme de bus
DE602004000617T2 (de) Verfahren zum Einrichten von Netzwerkadressen
DE69921446T2 (de) Übertragungsstruktur für industrielle prozesssteuerungssysteme
EP3679691B1 (fr) Procédé de transmission de données et réseau de communication
DE102006027683A1 (de) Verfahren und Vorrichtung zur Vernetzung einer automatisierten Anlage
EP1430369B1 (fr) Acces dynamique a des ressources d&#39;automatisation
EP2733910B1 (fr) Système bus, procédé de fonctionnement d&#39;un système bus et système fluidique doté d&#39;un système bus
DE60206780T2 (de) Netzwerkverbindungsvorrichtung, verbindungssystem und netzwerkverbindungsverfahren
DE102019114303B3 (de) Verfahren zum Erfassen von Netzwerkteilnehmer in einem Automatisierungsnetzwerk und Automatisierungsnetzwerk
EP2587772B1 (fr) Procédé de fabrication d&#39;une liaison communicative entre un appareil de programmation et un appareil de terrain technique d&#39;automatisation
DE60311682T2 (de) Verfahren zur Ausführung einer symmetrischen Adressenumsetzung
EP2503760B1 (fr) Procédé de réglage d&#39;un réseau de communication à partir d&#39;appareils d&#39;une installation d&#39;automatisation
EP0725516A2 (fr) Procédé de détermination de position d&#39;un participant dans un réseau
EP2839623B1 (fr) Procédé et dispositifs pour l&#39;accès en écriture à une variable dans un serveur
DE602005000715T2 (de) System und Verfahren zur Auswahl einer aktiven Verbindung
WO2011072958A1 (fr) Procédé d&#39;attribution d&#39;une adresse d&#39;interrogation à un appareil de terrain
EP3614642B1 (fr) Procédé de réglage d&#39;un flux, procédé de fourniture des informations d&#39;identification du flux, utilisation d&#39;un serveur de service nommé, appareil, programme informatique et support lisible par ordinateur
WO2007137531A1 (fr) Procédé permettant de faire fonctionner un appareil d&#39;automatisation, et programme informatique correspondant, programme informatique et appareil d&#39;automatisation associé
EP1642207A1 (fr) Attribution d&#39;adresses de station a des abonnes de communication dans un systeme de bus
EP2933985B1 (fr) Utilisation de multidiffusion DNS
EP1103022B1 (fr) Procede de communication
EP3163389B1 (fr) Procede de configuration d&#39;appareils de terrain et appareil de terrain ayant une configuration pour deux systemes de bus
EP1331794B1 (fr) Procédé d&#39;attribution d&#39;adresses dans un réseau et ses composants
DE10339051B3 (de) Verfahren zum Zuordnen von über mehrere Subnetze verteilten Clients zu einen Server und Client zur Ankopplung an einen Server
EP2988465A1 (fr) Procédé de transmission d&#39;un paquet de données IP entre des modules d&#39;automatisation

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2006742387

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1120060039733

Country of ref document: DE

REF Corresponds to

Ref document number: 112006003973

Country of ref document: DE

Date of ref document: 20090430

Kind code of ref document: P