[go: up one dir, main page]

EP1499999A2 - Directory service in an automation system - Google Patents

Directory service in an automation system

Info

Publication number
EP1499999A2
EP1499999A2 EP03727204A EP03727204A EP1499999A2 EP 1499999 A2 EP1499999 A2 EP 1499999A2 EP 03727204 A EP03727204 A EP 03727204A EP 03727204 A EP03727204 A EP 03727204A EP 1499999 A2 EP1499999 A2 EP 1499999A2
Authority
EP
European Patent Office
Prior art keywords
directory service
automation
service
automation system
components
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.)
Ceased
Application number
EP03727204A
Other languages
German (de)
French (fr)
Inventor
Rainer Heller
Thomas Jachmann
Norbert Portner
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
Siemens Corp
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
Priority claimed from DE10229877A external-priority patent/DE10229877A1/en
Application filed by Siemens AG, Siemens Corp filed Critical Siemens AG
Publication of EP1499999A2 publication Critical patent/EP1499999A2/en
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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/31—From computer integrated manufacturing till monitoring
    • G05B2219/31327—Directory service for database
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the invention relates to an automation system, in particular an automation system with distributed components, each of which has its own functionality.
  • Automation systems are usually parameterized manually by a project engineer.
  • the project engineer needs to know the individual automation devices of the automation system with their properties and functionalities. Interface descriptions of the automation devices are often only available in paper form or in the form of online help.
  • the object of the invention is to simplify the provision of information within an automation system.
  • a directory service in an automation system for providing information about access options, functionalities, interfaces and topologies of components of the automation system, the directory service being web service-based.
  • the proposed invention offers a directory service which has knowledge of the components of an automation system and their functionality has.
  • clients are implemented in such a way that they can operate less generically. They are usually programmed and configured precisely against the existing devices.
  • the directory service according to the invention has the advantage that the usual 1: 1 relationship (direct linking) between a client and the automation components used by this client is no longer necessary.
  • the directory service is based on WebService.
  • such a directory service can be designed as a central directory service on a server, e.g. B. in the form of a central XML-based information service based on UDDI (Universal Discovery Description and Integration) in the web server vice environment, here adapted to the needs of automation technology.
  • a server e.g. B. in the form of a central XML-based information service based on UDDI (Universal Discovery Description and Integration) in the web server vice environment, here adapted to the needs of automation technology.
  • UDDI Universal Discovery Description and Integration
  • search service a search service used within the directory service to search for components and / or functionalities of the automation system is provided.
  • the directory service has means for self-registration of components and / or functionalities of the automation system.
  • Automation devices or components can thus register themselves with the central directory service.
  • self-registration of web services provided by the automation device can also be entered in the directory service.
  • the directory service is not necessarily implemented as a central instance, but can e.g. B. to increase redundancy, run as a distributed service (e.g. as a cluster, web farm, decentralized database, etc.).
  • a distributed service e.g. as a cluster, web farm, decentralized database, etc.
  • the figure shows a schematic representation of the principle of using a directory service in a distributed automation system.
  • the distributed system contains various operator control and monitoring systems 51 to 53, distributed automation systems 54 to 57 and a central directory service 58. Communication between operator control and monitoring systems 51 to 53 and automation systems 54 to 57 takes place via an Internet and / or intranet 50 Different automation systems 54 to 57 can be spatially spaced apart from one another. Access to components 70 through 78 of the auto Automation systems 54 to 57 are carried out via web services 60 to 68.
  • the operating and monitoring systems 51, 52 and 53 are designed as part of a control room or as a mobile personal digital assistant (PDA) of a service technician.
  • PDA mobile personal digital assistant
  • communication via the Internet and / or intranet 50 takes place not only between the operating and monitoring systems 51 to 53 and the automation systems 54 to 57 but also between the individual automation systems 54 to 57 or between the components 70 to 78 of the automation systems.
  • Components 70 to 78 of the automation system each have at least one interface for message and port-based access to at least one application provided by the respective components 70 to 78.
  • these applications are implemented as web services 60 to 68.
  • Such a WebService 60 to 68 provides a certain functionality, uses Internet mechanisms and is stateless.
  • the interfaces of the components of the automation system are described by meta information.
  • An interface can, for example, be designed as an XML interface.
  • an “Automation Directory Discovery and Integration” (ADDI) is defined as the central directory service 58.
  • UDDI does not meet the requirements of automation technology, since it is optimized for e-business services Automation specifics are specifically taken into account.
  • UDDI schemas and functionalities are expanded for the ADDI directory service 58 and thus enable the use of the UDDI mechanisms / clients in the automation environment as well from UDDI.
  • the service Descriptions of the automation devices, components 70 to 78 and applications 60 to 68 can be stored.
  • system data is made available via a uniform mechanism enables generic applications to be created.
  • These can use the directory service 58 (ADDI) to browse, for example, a plant structure, to find components and interfaces and / or to provide services.
  • ADPI directory service
  • generic applications (not possible today), in particular for standardized functionalities such as diagnosis, download, parameterization, etc. can be created. Due to the plant structure stored in the directory service 58, this can serve as a central information instance for devices present in a plant, in an automation system. This enables a wide range of information to be provided, from browsing through the existing system to requests for firmware versions on individual devices.
  • the applications (services) offered by automation devices are described in a uniform manner (e.g.
  • the implementation of services in automation devices can be memory-optimized because metal information about (automation) devices, applications and / or web services is stored and managed centrally.
  • the proposed directory service 58 also serves as the basis for the establishment of consolidation services. Additional services are possible on the basis of the data available in the directory service 58. Data is available or can be stored for totals, maintenance analysis, efficiency analyzes on the automation system, on levels or cells.
  • search service query service
  • questions can be answered such as: B.:, Which Services does the automation device 4711 offer in hall 3? ' or, search for all devices that offer the standard diagnostic service! '.
  • the automation device or the automation component provides the directory service 58 with information about all offered web services 60 to 68 as part of a discovery process (UPNP - Universal Plug and Play).
  • the directory service 58 uses a standardized service to query the web services 60 to 68 provided by the automation system after the discovery phase of the respective automation device 70 to 78. This can be done, for example, via standardized web service interfaces of the automation devices 70 to 78.
  • the discovery phase can also consist in the fact that the addressing of the respective device is entered manually / partially automatically in the directory service 58 and the directory service 58 then automatically asks the device about its services. So not only the existence of automation devices 70 to 78, but above all their functionality is registered.
  • the registration can also be carried out conventionally, in that the data from a configuration or an engineering system is transferred directly to the directory service 58.
  • This technology allows both direct communication between applications (the so-called services) as well as the construction of applications from distributed components (again services), ie loosely connected web services can work together to fulfill a task.
  • standards such as XML and SOAP
  • the WebService technology scales from local communication to communication via the intra- net / Internet. It is the basis for distributed and integrated Internet applications, using existing standards (e.g. W3C, IETF standards such as HTTP, XML, XML Schema, XML Data Types, etc.) or new ones, together with W3C, IETF defines standards such as SOAP, WSDL, UDDI.
  • Web service interfaces are described by meta information (methods, parameters (names and types)), usually in WSDL (Web Service Description Language). This complete interface description is sufficient to call up the web services. It describes the end point (port) at which the respective web service can be called and is particularly useful for automatic communication with web services.
  • WebServices are easy to access, blurring the lines between local APIs and WebServices ("Web APIs"). Access is just as easy as when creating and using a local object.
  • WebService technology is the basis for loosely coupled applications. It is characterized by message-based communication and scalability through statelessness. The loose coupling (e.g. with SOAP) offers the advantages of good compatibility with changes in the implementation of the client and server and robust communication (port-based, message-based, asynchronous).
  • a client packs messages into self-describing packets (messages) and sends them over the respective communication connection.
  • the sender and receiver only have an agreement with regard to the message format used on the line. The only assumption is that the recipient understands the message. No assumptions are made about what happens after the message is received or between the sender and recipient.
  • Common web services have the following properties: They are accessible via a communication network such as the Internet / intranet and have an XML interface. Information about WebServices is stored in a registry so that the WebServices can be localized via it. They communicate using XML messages Web protocols and support loosely coupled connections between systems.
  • the invention thus relates to a directory service 58 which simplifies the provision of information within an automation system.
  • the directory service 58 is used to provide information about access options, functionalities, interfaces and topologies of components of the automation system and is web service-based.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention relates to a directory service (58) that simplifies the provision of information within an automation system. The directory service (58) serves to provide information regarding access possibilities, functionalities, interfaces and topologies of components of the automation system and is Web service-based.

Description

Beschreibungdescription

Verzeichnisdienst in einem AutomatisierungssystemDirectory service in an automation system

Die Erfindung betrifft ein Automatisierungssystem, insbesondere ein Automatisierungssystem mit verteilten Komponenten, welche jeweils eigene Funktionalität aufweisen.The invention relates to an automation system, in particular an automation system with distributed components, each of which has its own functionality.

Automatisierungssysteme werden üblicherweise durch einen Pro- jekteur manuell para etriert . Der Projekteur uss dafür die einzelnen Automatisierungsgeräte des Automatisierungssystems mit ihren Eigenschaften und Funktionalitäten genau kennen. Schnittstellenbeschreibungen der Automatisierungsgeräte liegen häufig nur in Papierfόrm oder in Form von Online-Hilfen vor.Automation systems are usually parameterized manually by a project engineer. The project engineer needs to know the individual automation devices of the automation system with their properties and functionalities. Interface descriptions of the automation devices are often only available in paper form or in the form of online help.

Der Erfindung liegt die Aufgabe zugrunde, die Bereitstellung von Informationen innerhalb eines Automatisierungssystems zu vereinfachen .The object of the invention is to simplify the provision of information within an automation system.

Diese Aufgabe wird gelöst durch einen Verzeichnisdienst in einem Automatisierungssystem zur Bereitstellung von Informationen über Zugriffsmöglichkeiten, Funktionalitäten, Schnittstellen und Topologien von Komponenten des Automatisierungssystems, wobei der Verzeichnisdienst WebService-basiert ist.This object is achieved by a directory service in an automation system for providing information about access options, functionalities, interfaces and topologies of components of the automation system, the directory service being web service-based.

Für den Projekteur und für den Nutzer eines Automatisierungssystems ist gleichermaßen interessant, welche Komponenten ein Automatisierungssystem aufweist, welche Funktionalität diese Komponenten besitzen und welche Zugriffsmöglichkeiten auf die Komponenten existieren. Im Allgemeinen stellt sich die Frage nach der Verfügbarkeit eines bestimmten Dienstes innerhalb des Automatisierungssystems. In bisherigen Automatisierungssystemen ist keine Instanz vorhanden, die einen derartigen Service bieten könnte. Die vorgeschlagene Erfindung bietet einen Verzeichnisdienst, welcher Kenntnis über die Komponenten eines Automatisierungssystems und deren Funktionalität besitzt. Clients werden heute so realisiert, dass sie wenig generisch operieren können. Sie werden üblicherweise genau gegen die vorhandenen Geräte programmiert und projektiert. Der erfindungsgemäße Verzeichnisdienst bietet den Vorteil, dass die übliche 1 : 1-Beziehung (direkte Verlinkung) zwischen einem Client und den von diesem Client benutzten Automatisierungskomponenten nicht mehr erforderlich ist. Der Verzeichnisdienst ist WebService-basiert . Im Internet existieren Technologien, Standards und De-facto-Standards wie TCP/IP, HTTP, SMTP (Simple Mail Transfer Protocol) , XML (Extension Markup Language) , SSL (Secure Socket Layer) . Im WebService- U feld entstehen und verbreiten sich neuere Standards wie SOAP (Simple Object Access Protocol), SDL (Web Service Desc- ription Language) , UDDI (Universal Discovery Description and Integration) zunehmend. Diese Internet-Technologien können für die Automatisierungstechnik adaptiert werden. Da es sich um offene Standards handelt, ist ihre Nutzung (ggf. erweitert um automatisierungstechnische Beschreibungsmerkmale) zur Beschreibung von Automatisierungssystemen möglich. Hierüber lassen sich sowohl die (Software-) Schnittstellen einzelner Automatisierungsgeräte, als auch deren strukturelle Topologie innerhalb einer Automatisierungsanlage bzw. eines Automatisierungssystems beschreiben. Diese Informationen können direkt von Programmen sowie von Applikationen weiterverwendet werden. Hiermit lassen sich Applikationen generischer realisieren als dies heute möglich ist. Die Erfindung ermöglicht so die Nutzung von Standard-Internettechniken, insbesondere aus dem WebService-Umfeld, angewendet auf Automatisierungsstrukturen, wie z. B. Automatisierungssysteme bzw. -anlagen, Automatisierungszellen, Automatisierungskomponenten und/oder Automatisierungsgeräte .For the configuration engineer and for the user of an automation system it is equally interesting which components an automation system has, which functionality these components have and which access options to the components exist. In general, the question arises of the availability of a certain service within the automation system. In previous automation systems, there is no instance that could offer such a service. The proposed invention offers a directory service which has knowledge of the components of an automation system and their functionality has. Today, clients are implemented in such a way that they can operate less generically. They are usually programmed and configured precisely against the existing devices. The directory service according to the invention has the advantage that the usual 1: 1 relationship (direct linking) between a client and the automation components used by this client is no longer necessary. The directory service is based on WebService. Technologies, standards and de facto standards such as TCP / IP, HTTP, SMTP (Simple Mail Transfer Protocol), XML (Extension Markup Language), SSL (Secure Socket Layer) exist on the Internet. Newer standards such as SOAP (Simple Object Access Protocol), SDL (Web Service Description Language), UDDI (Universal Discovery Description and Integration) are increasingly emerging and spreading in the WebService field. These Internet technologies can be adapted for automation technology. Since these are open standards, they can be used (possibly expanded to include technical description features) to describe automation systems. This can be used to describe the (software) interfaces of individual automation devices as well as their structural topology within an automation system or an automation system. This information can be used directly by programs and applications. This allows applications to be implemented more generically than is possible today. The invention thus enables the use of standard Internet technologies, in particular from the web service environment, applied to automation structures, such as, for. B. automation systems or systems, automation cells, automation components and / or automation devices.

Ein solcher Verzeichnisdienst kann gemäß einer vorteilhaften Ausgestaltung der Erfindung als zentraler Verzeichnisdienst auf einem Server ausgebildet sein, z. B. in Form eines zentralen XML-basierten Informationsdienstes in Anlehnung an UDDI (Universal Discovery Description and Integration) im WebSer- vice-Umfeld, hier adaptiert auf die Belange der Automatisierungstechnik.According to an advantageous embodiment of the invention, such a directory service can be designed as a central directory service on a server, e.g. B. in the form of a central XML-based information service based on UDDI (Universal Discovery Description and Integration) in the web server vice environment, here adapted to the needs of automation technology.

Um in Anlagenstrukturen zu browsen, bestimmte Geräte (-typen) zu suchen und insbesondere auch Services, die von Geräten bereitgestellt werden zu finden, wird vorgeschlagen, dass innerhalb des Verzeichnisdienstes ein Suchdienst (Query Service) zur Suche von Komponenten und/oder Funktionalitäten des Automatisierungssystems vorgesehen ist.In order to browse system structures, to search for certain devices (types) and in particular to find services that are provided by devices, it is proposed that a search service (query service) be used within the directory service to search for components and / or functionalities of the automation system is provided.

Gemäß einer weiteren vorteilhaften Ausgestaltung der Erfindung weist der Verzeichnisdienst Mittel zur Selbstregistrierung von Komponenten und/oder Funktionalitäten des Automatisierungssystems auf. Automatisierungsgeräte bzw. -komponenten können sich so selbst beim zentralen Verzeichnisdienst registrieren. Hierbei kann insbesondere auch eine Selbstregistrierung von WebServices, die vom Automatisierungsgerät bereitgestellt werden, im Verzeichnisdienst eingetragen werden.According to a further advantageous embodiment of the invention, the directory service has means for self-registration of components and / or functionalities of the automation system. Automation devices or components can thus register themselves with the central directory service. In particular, self-registration of web services provided by the automation device can also be entered in the directory service.

Der Verzeichnisdienst ist nicht notwendig als zentrale Instanz realisiert, sondern kann, z. B. um die Redundanz zu erhöhen, als verteilter Dienst ausgeführt sein (z. B. als Cluster, Webfarm, dezentrale Datenbank etc.).The directory service is not necessarily implemented as a central instance, but can e.g. B. to increase redundancy, run as a distributed service (e.g. as a cluster, web farm, decentralized database, etc.).

Nachfolgend wird die Erfindung anhand der in der Figur dargestellten Ausführungsbeispiele näher beschrieben und erläutert. Die Figur zeigt eine schematische Darstellung des Prinzips der Nutzung eines Verzeichnisdienstes in einem verteilten Automatisierungssystem. Das verteilte System enthält verschiedene Bedien- und Beobachtungssysteme 51 bis 53, verteilte Automatisierungsanlagen 54 bis 57 und einen zentralen Verzeichnisdienst 58. Die Kommunikation zwischen Bedien- und Beobachtungssystemen 51 bis 53 und Automatisierungsanlagen 54 bis 57 erfolgt über ein Internet und/oder Intranet 50. Die unterschiedlichen Automatisierungsanlagen 54 bis 57 können räumlich beliebig weit voneinander entfernt verteilt angeordnet sein. Der Zugriff auf die Komponenten 70 bis 78 der Auto- matisierungsanlagen 54 bis 57 erfolgt über WebServices 60 bis 68. Die Bedien- und Beobachtungssysteme 51, 52 und 53 sind im Ausführungsbeispiel als Teil einer Warte bzw. als ein mobiler Personal Digital Assistant (PDA) eines Servicetechnikers ausgeführt. Die Kommunikation über das Internet und/oder Intranet 50 erfolgt jedoch nicht nur zwischen den Bedien- und Beobachtungssystemen 51 bis 53 und den Automatisierungsanlagen 54 bis 57 sondern auch zwischen den einzelnen Automatisierungsanlagen 54 bis 57 bzw. zwischen den Komponenten 70 bis 78 der Automatisierungsanlagen.The invention is described and explained in more detail below with reference to the exemplary embodiments shown in the figure. The figure shows a schematic representation of the principle of using a directory service in a distributed automation system. The distributed system contains various operator control and monitoring systems 51 to 53, distributed automation systems 54 to 57 and a central directory service 58. Communication between operator control and monitoring systems 51 to 53 and automation systems 54 to 57 takes place via an Internet and / or intranet 50 Different automation systems 54 to 57 can be spatially spaced apart from one another. Access to components 70 through 78 of the auto Automation systems 54 to 57 are carried out via web services 60 to 68. In the exemplary embodiment, the operating and monitoring systems 51, 52 and 53 are designed as part of a control room or as a mobile personal digital assistant (PDA) of a service technician. However, communication via the Internet and / or intranet 50 takes place not only between the operating and monitoring systems 51 to 53 and the automation systems 54 to 57 but also between the individual automation systems 54 to 57 or between the components 70 to 78 of the automation systems.

Im Folgenden soll anhand der Figur das Prinzip der Nutzung des Verzeichnisdienstes 58 in einem verteilten Automatisierungssystem erläutert werden. Die Komponenten 70 bis 78 des Automatisierungssystems weisen jeweils mindestens eine Schnittstelle zum nachrichten- und portbasierten Zugriff auf mindestens eine von der jeweiligen Komponente 70 bis 78 bereitgestellte Applikation auf. Diese Applikationen sind im Ausführungsbeispiel als WebServices 60 bis 68 realisiert. Ein solcher WebService 60 bis 68 stellt eine gewisse Funktionalität zur Verfügung, nutzt Internet-Mechanismen und ist zustandslos. Die Schnittstellen der Komponenten des Automatisierungssystems sind durch Meta-Informationen beschrieben. Eine Schnittstelle kann beispielsweise als XML-Schnittstelle ausgeführt sein. Als zentraler Verzeichnisdienst 58 wird im Ausführungsbeispiel ein „Automation Directory Discovery and Integration" (ADDI) definiert. Der oben genannte Verzeichnisdienst UDDI genügt nicht den Anforderungen der Automatisierungstechnik, da er für E-Business-Services optimiert ist. Daher werden für die ADDI-Definition Automatisierungsspezifi- kas speziell berücksichtigt. UDDI-Schematas und Funktionalitäten werden für den ADDI-Verzeichnisdienst 58 erweitert und ermöglichen so die Nutzung der UDDI-Mechanismen/Clients auch im Automatisierungsumfeld. Im Verzeichnisdienst 58 ADDI können Anlagenstrukturen abgebildet werden in Analogie zu den White und Yellow Pages von UDDI. Auf unterster Ebene, entsprechend den Green Pages von UDDI, können die Service- Beschreibungen der Automatisierungsgeräte, Komponenten 70 bis 78 und Applikationen 60 bis 68 abgelegt werden.The principle of using directory service 58 in a distributed automation system will be explained below with reference to the figure. Components 70 to 78 of the automation system each have at least one interface for message and port-based access to at least one application provided by the respective components 70 to 78. In the exemplary embodiment, these applications are implemented as web services 60 to 68. Such a WebService 60 to 68 provides a certain functionality, uses Internet mechanisms and is stateless. The interfaces of the components of the automation system are described by meta information. An interface can, for example, be designed as an XML interface. In the exemplary embodiment, an “Automation Directory Discovery and Integration” (ADDI) is defined as the central directory service 58. The above-mentioned directory service UDDI does not meet the requirements of automation technology, since it is optimized for e-business services Automation specifics are specifically taken into account. UDDI schemas and functionalities are expanded for the ADDI directory service 58 and thus enable the use of the UDDI mechanisms / clients in the automation environment as well from UDDI. At the lowest level, according to the Green Pages of UDDI, the service Descriptions of the automation devices, components 70 to 78 and applications 60 to 68 can be stored.

Im Folgenden werden weitere Vorteile der Erfindung und ihrer Ausgestaltungen dargestellt. Dadurch, dass Anlagendaten über einen einheitlichen Mechanismus zur Verfügung gestellt werden, wird das Erstellen generischer Applikationen ermöglicht. Diese können den Verzeichnisdienst 58 (ADDI) verwenden um beispielsweise über eine Anlagenstruktur zu browsen, um Komponenten und Schnittstellen zu finden und/oder um Service- Leistungen zu erbringen. So können (heute nicht mögliche) ge- nerische Applikationen, insbesondere für standardisierte Funktionalitäten wie Diagnose, Download, Parametrierung etc. erstellt werden. Aufgrund der im Verzeichnisdienst 58 abgelegten Anlagenstruktur kann diese als zentrale Auskunftsinstanz für in einer Anlage, in einem Automatisierungssystem vorhandene Geräte dienen. Hierdurch werden verschiedenste Auskunftsinformationen ermöglicht, vom Browsen über die vorhandene Anlage bis hin zu Anfragen nach Versionsständen von Firmware auf einzelnen Geräten. Die von Automatisierungsgeräten angebotenen Applikationen (Services) werden einheitlich beschrieben (z. B. mit WSDL Files bei WebServices). Für die Gerätebeschreibung ist ein Typ/Instanz-Konzept auf WSDL-Ebene realisiert. Dies vermindert redundante Speicherung von gleichartigen Daten. Die Implementierung von Services in Automatisierungsgeräten kann speicheroptimiert erfolgen, da Me- tainformationen über (Automatisierungs-) Geräte, Applikationen und/oder WebServices zentral abgelegt und verwaltet werden. Der vorgeschlagene Verzeichnisdienst 58 dient außerdem als Basis für die Etablierung von Konsolidierungsservices. Aufgrund der im Verzeichnisdienst 58 vorhandenen Daten sind zusätzliche Services möglich. So sind Daten vorhanden bzw. ablegbar für Summenbildung, Wartungsanalyse, Effizienzanalysen auf dem Automatisierungssystem, auf Ebenen oder Zellen. Mit Hilfe des Suchdienstes (Query Service) zur Suche von Komponenten und/oder Funktionalitäten des Automatisierungssystems können Fragen beantwortet werden wie z. B. : ,Welche Services bietet das Automatisierungsgerät 4711 in Halle 3?' oder , Suche alle Geräte, die den Standard-Diagnose-Service anbieten ! ' .Further advantages of the invention and its configurations are presented below. The fact that system data is made available via a uniform mechanism enables generic applications to be created. These can use the directory service 58 (ADDI) to browse, for example, a plant structure, to find components and interfaces and / or to provide services. In this way, generic applications (not possible today), in particular for standardized functionalities such as diagnosis, download, parameterization, etc. can be created. Due to the plant structure stored in the directory service 58, this can serve as a central information instance for devices present in a plant, in an automation system. This enables a wide range of information to be provided, from browsing through the existing system to requests for firmware versions on individual devices. The applications (services) offered by automation devices are described in a uniform manner (e.g. with WSDL files for WebServices). A type / instance concept at the WSDL level is implemented for the device description. This reduces redundant storage of similar data. The implementation of services in automation devices can be memory-optimized because metal information about (automation) devices, applications and / or web services is stored and managed centrally. The proposed directory service 58 also serves as the basis for the establishment of consolidation services. Additional services are possible on the basis of the data available in the directory service 58. Data is available or can be stored for totals, maintenance analysis, efficiency analyzes on the automation system, on levels or cells. With the help of the search service (query service) to search for components and / or functionalities of the automation system, questions can be answered such as: B.:, Which Services does the automation device 4711 offer in hall 3? ' or, search for all devices that offer the standard diagnostic service! '.

Die vorgeschlagenen Mittel zur Selbstregistrierung von Komponenten und/oder Funktionalitäten des Automatisierungssystems können wie im Folgenden beschrieben ausgebildet sein. In einer ersten Ausgestaltung stellt das Automatisierungsgerät bzw. die Automatisierungskomponente im Rahmen eines Discovery-Prozesses (UPNP - Universal Plug and Play) dem Verzeichnisdienst 58 Informationen zu allen angebotenen WebServices 60 bis 68 zur Verfügung. In einer zweiten Ausgestaltung erfragt der Verzeichnisdienst 58 über einen standardisierten Service die vom Automatisierungssystem bereitgestellten WebServices 60 bis 68 nach der Discovery-Phase des jeweiligen Automatisierungsgeräts 70 bis 78 ab. Dies kann beispielsweise über standardisierte WebService-Schnittstellen der Automatisierungsgeräte 70 bis 78 erfolgen. Die Discovery-Phase kann dabei auch darin bestehen, dass manuell/teilautomatisch die Adressierung des jeweiligen Geräts im Verzeichnisdienst 58 eingetragen wird und der Verzeichnisdienst 58 das Gerät danach automatisch nach seinen Services fragt. Es wird also nicht nur die Existenz von Automatisierungsgeräten 70 bis 78, sondern vor allem deren Funktionalität registriert. Die Registrierung kann auch konventionell erfolgen, indem die Daten aus einer Projektierung bzw. einem Engineering System direkt in den Verzeichnisdienst 58 übernommen werden.The proposed means for self-registration of components and / or functionalities of the automation system can be designed as described below. In a first embodiment, the automation device or the automation component provides the directory service 58 with information about all offered web services 60 to 68 as part of a discovery process (UPNP - Universal Plug and Play). In a second embodiment, the directory service 58 uses a standardized service to query the web services 60 to 68 provided by the automation system after the discovery phase of the respective automation device 70 to 78. This can be done, for example, via standardized web service interfaces of the automation devices 70 to 78. The discovery phase can also consist in the fact that the addressing of the respective device is entered manually / partially automatically in the directory service 58 and the directory service 58 then automatically asks the device about its services. So not only the existence of automation devices 70 to 78, but above all their functionality is registered. The registration can also be carried out conventionally, in that the data from a configuration or an engineering system is transferred directly to the directory service 58.

Zur weiteren Erläuterung der Erfindung wird im Folgenden ein Überblick über die WebService-Technologie gegeben. Diese Technologie erlaubt sowohl die direkte Kommunikation zwischen Applikationen (den sogenannten Services) als auch den Aufbau von Applikationen aus verteilten Komponenten (wiederum Services) , d. h. lose verbundene WebServices können zur Erfüllung einer Aufgabe zusammenarbeiten. Die WebService-Technologie skaliert mit Hilfe von Standards wie XML und SOAP von lokaler Kommunikation bis zur Kommunikation über das Intra- net/Internet. Sie ist die Basis für verteilte und integrierte Internet-Applikationen, verwendet dabei existierende Standards (z. B. W3C-, IETF-Standards wie HTTP, XML, XML Schema, XML Data Types, etc.) bzw. neue, zusammen mit W3C, IETF definierte Standards wie SOAP, WSDL, UDDI. Schnittstellen von WebServices sind durch Meta-Information (Methoden, Parameter (Namen und Typen) ) beschrieben, üblicherweise in WSDL (Web Service Description Language) . Diese vollständige Schnittstellenbeschreibung ist ausreichend zum Aufruf der WebServices. Sie beschreibt den End-Point (Port), unter dem der jeweilige WebService aufgerufen werden kann und ist insbesondere nützlich zur automatischen Kommunikation mit WebServices. WebServices zeichnen sich durch einen einfachen Zugriff aus, wobei die Grenzen zwischen lokalen APIs und WebServices ("Web-APIs") verwischen. Der Zugriff ist ähnlich einfach wie beim Erzeugen und Nutzen eines lokalen Objektes. Die WebService-Technologie ist somit die Basis für lose gekoppelte Applikationen. Sie ist gekennzeichnet durch nachrichtenbasierte Kommunikation und Skalierbarkeit durch Zustandslosigkeit . Die lose Kopplung (z. B. mit SOAP) bietet insbesondere die Vorteile der guten Verträglichkeit gegenüber Änderungen der Implementierung bei Client und Server und der robusten Kommunikation (portbasiert, messagebasiert, asynchron) . In message- bzw. nachrichtenbasierten Systemen verpackt ein Client Nachrichten in selbstbeschreibende Pakete (Messages) und schickt sie so über die jeweilige Kommunikationsverbindung. Eine Vereinbarung zwischen Sender und Empfänger besteht nur bezüglich dem verwendeten Message-Format auf der Leitung. Die einzige Annahme besteht darin, dass der Empfänger die Message versteht. Es werden keine Annahmen darüber getroffen, was nach Empfang der Message bzw. zwischen Sender und Empfänger passiert. Übliche WebServices besitzen die folgenden Eigenschaften: Sie sind über ein Kommunikationsnetz wie Internet/Intranet zugreifbar und besitzen eine XML-Schnittstelle. Informationen über WebServices werden in einer Registry gespeichert, so dass die WebServices über diese lokalisierbar sind. Sie kommunizieren mit Hilfe von XML-Nachrichten über Web-Protokolle und unterstützen lose gekoppelte Verbindungen zwischen Systemen.To further explain the invention, an overview of the web service technology is given below. This technology allows both direct communication between applications (the so-called services) as well as the construction of applications from distributed components (again services), ie loosely connected web services can work together to fulfill a task. With the help of standards such as XML and SOAP, the WebService technology scales from local communication to communication via the intra- net / Internet. It is the basis for distributed and integrated Internet applications, using existing standards (e.g. W3C, IETF standards such as HTTP, XML, XML Schema, XML Data Types, etc.) or new ones, together with W3C, IETF defines standards such as SOAP, WSDL, UDDI. Web service interfaces are described by meta information (methods, parameters (names and types)), usually in WSDL (Web Service Description Language). This complete interface description is sufficient to call up the web services. It describes the end point (port) at which the respective web service can be called and is particularly useful for automatic communication with web services. WebServices are easy to access, blurring the lines between local APIs and WebServices ("Web APIs"). Access is just as easy as when creating and using a local object. The WebService technology is the basis for loosely coupled applications. It is characterized by message-based communication and scalability through statelessness. The loose coupling (e.g. with SOAP) offers the advantages of good compatibility with changes in the implementation of the client and server and robust communication (port-based, message-based, asynchronous). In message or message-based systems, a client packs messages into self-describing packets (messages) and sends them over the respective communication connection. The sender and receiver only have an agreement with regard to the message format used on the line. The only assumption is that the recipient understands the message. No assumptions are made about what happens after the message is received or between the sender and recipient. Common web services have the following properties: They are accessible via a communication network such as the Internet / intranet and have an XML interface. Information about WebServices is stored in a registry so that the WebServices can be localized via it. They communicate using XML messages Web protocols and support loosely coupled connections between systems.

Zusammenfassend betrifft die Erfindung somit einen Verzeichnisdienst 58, welcher die Bereitstellung von Informationen innerhalb eines Automatisierungssystems vereinfacht. Der Verzeichnisdienst 58 dient zur Bereitstellung von Informationen über Zugriffsmöglichkeiten, Funktionalitäten, Schnittstellen und Topologien von Komponenten des Automatisierungssystems und ist WebService-basiert . In summary, the invention thus relates to a directory service 58 which simplifies the provision of information within an automation system. The directory service 58 is used to provide information about access options, functionalities, interfaces and topologies of components of the automation system and is web service-based.

Claims

Patentansprüche claims 1. Verzeichnisdienst (58) in einem Automatisierungssystem zur Bereitstellung von Informationen über Zugriffsmöglichkeiten, Funktionalitäten, Schnittstellen und Topologien von Komponenten des Automatisierungssystems, wobei der Verzeichnisdienst (58) WebService-basiert ist.1. Directory service (58) in an automation system for providing information about access options, functionalities, interfaces and topologies of components of the automation system, the directory service (58) being web service-based. 2. Verzeichnisdienst nach Anspruch 1, d a d u r c h g e k e n n z e i c h n e t , dass der Verzeichnisdienst (58) als zentraler Verzeichnisdienst auf einem Server ausgebildet ist.2. Directory service according to claim 1, so that the directory service (58) is designed as a central directory service on a server. 3. Verzeichnisdienst nach Anspruch 1 oder 2, d a d u r c h g e k e n n z e i c h n e t , dass ein Suchdienst zur Suche von Komponenten und/oder Funktionalitäten des Automatisierungssystems vorgesehen ist.3. Directory service according to claim 1 or 2, so that a search service for searching components and / or functionalities of the automation system is provided. 4. Verzeichnisdienst nach einem der vorhergehenden Ansprüche, d a d u r c h g e k e n n z e i c h n e t , dass Mittel zur Selbstregistrierung von Komponenten und/oder Funktionalitäten des Automatisierungssystems vorgesehen sind.4. Directory service according to one of the preceding claims, that a means for self-registration of components and / or functionalities of the automation system are provided. 5. Verzeichnisdienst nach einem der vorhergehenden Ansprüche, d a d u r c h g e k e n n z e i c h n e t , dass der Verzeichnisdienst (58) als verteilter Dienst ausgeführt ist. 5. Directory service according to one of the preceding claims, that the directory service (58) is designed as a distributed service.
EP03727204A 2002-04-29 2003-04-16 Directory service in an automation system Ceased EP1499999A2 (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
DE10219093 2002-04-29
DE10219093 2002-04-29
DE10229877 2002-07-03
DE10229877A DE10229877A1 (en) 2002-04-29 2002-07-03 Directory service in an automation system
PCT/DE2003/001290 WO2003094046A2 (en) 2002-04-29 2003-04-16 Directory service in an automation system

Publications (1)

Publication Number Publication Date
EP1499999A2 true EP1499999A2 (en) 2005-01-26

Family

ID=29403563

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03727204A Ceased EP1499999A2 (en) 2002-04-29 2003-04-16 Directory service in an automation system

Country Status (3)

Country Link
US (1) US7693972B2 (en)
EP (1) EP1499999A2 (en)
WO (1) WO2003094046A2 (en)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IL166717A0 (en) * 2002-08-26 2006-01-15 Computer Ass Think Inc Web services apparatus and methods
US8677118B1 (en) * 2005-02-01 2014-03-18 Trend Micro, Inc. Automated kernel hook module building
US7587464B2 (en) 2006-03-16 2009-09-08 Exceptional Innovation, Llc Device automation using networked device control having a web services for devices stack
US7509402B2 (en) 2006-03-16 2009-03-24 Exceptional Innovation, Llc Automation control system having a configuration tool and two-way ethernet communication for web service messaging, discovery, description, and eventing that is controllable with a touch-screen display
US8725845B2 (en) 2006-03-16 2014-05-13 Exceptional Innovation Llc Automation control system having a configuration tool
US8155142B2 (en) * 2006-03-16 2012-04-10 Exceptional Innovation Llc Network based digital access point device
US7966083B2 (en) 2006-03-16 2011-06-21 Exceptional Innovation Llc Automation control system having device scripting
US8001219B2 (en) 2006-03-16 2011-08-16 Exceptional Innovation, Llc User control interface for convergence and automation system
US8209398B2 (en) * 2006-03-16 2012-06-26 Exceptional Innovation Llc Internet protocol based media streaming solution
WO2007126781A2 (en) 2006-03-27 2007-11-08 Exceptional Innovation Llc Set top box for convergence and automation system
WO2007124453A2 (en) 2006-04-20 2007-11-01 Exceptional Innovation Llc Touch screen for convergence and automation system
US7667968B2 (en) 2006-05-19 2010-02-23 Exceptional Innovation, Llc Air-cooling system configuration for touch screen
US7962130B2 (en) 2006-11-09 2011-06-14 Exceptional Innovation Portable device for convergence and automation solution
WO2008143881A1 (en) * 2007-05-14 2008-11-27 Exceptional Innovation, Llc Customizable media device
WO2008148096A1 (en) * 2007-05-25 2008-12-04 Exceptional Innovation, Llc Customizable remote control device
CN101635774B (en) * 2009-08-21 2012-07-18 中兴通讯股份有限公司 CTIEX, system and method for realizing transmission of channel associated data of seat and automatic service
US9009281B2 (en) * 2011-07-01 2015-04-14 Hewlett-Packard Development Company, L.P. Composition of services

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5021997A (en) * 1986-09-29 1991-06-04 At&T Bell Laboratories Test automation system
JP3064469B2 (en) 1991-04-19 2000-07-12 株式会社日立製作所 CAD parts management system
CA2373511C (en) 1999-05-19 2014-07-08 Digimarc Corporation Methods and systems for controlling computers or linking to internet resources from physical and electronic objects
FR2813471B1 (en) * 2000-08-31 2002-12-20 Schneider Automation COMMUNICATION SYSTEM FOR AUTOMATED EQUIPMENT BASED ON THE SOAP PROTOCOL
US6879806B2 (en) * 2001-06-01 2005-04-12 Zensys A/S System and a method for building routing tables and for routing signals in an automation system
US20030191802A1 (en) * 2002-04-03 2003-10-09 Koninklijke Philips Electronics N.V. Reshaped UDDI for intranet use
US7725590B2 (en) * 2002-04-19 2010-05-25 Computer Associates Think, Inc. Web services broker

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO03094046A2 *

Also Published As

Publication number Publication date
WO2003094046A2 (en) 2003-11-13
WO2003094046A3 (en) 2004-02-12
US20050262227A1 (en) 2005-11-24
US7693972B2 (en) 2010-04-06

Similar Documents

Publication Publication Date Title
WO2003094046A2 (en) Directory service in an automation system
EP2724494B1 (en) Method for operating a field device, and field device
DE60029321T2 (en) METHOD AND DEVICE FOR REMOTE CONTROL OF A HOME NETWORK FROM AN EXTERNAL COMMUNICATION NETWORK
EP1305930B1 (en) System and method for transmitting opc data via data networks, in particular the internet using an asynchronous data connection
WO2004014022A2 (en) Computer network with diagnosis computer nodes
EP1430369B1 (en) Dynamic access to automation resources
DE102012112225B3 (en) Method for exchanging device-specific data between devices and / or systems of different network systems and bus system for carrying out the method
EP1362304A2 (en) System and method for saving and generating web pages, which optimises storage space
EP1611730B1 (en) Method and arrangement for configuring a device in a data network
DE69920502T2 (en) POINT-TO-POINT CONNECTION VIA A BROADCASTING NETWORK
EP1401170B1 (en) Electronic apparatus for a bussystem
EP1494434A1 (en) Method for the configuration of an apparatus in a data network
DE10336648A1 (en) System and method for web-based monitoring and control of several spatially distributed installations
DE10229878A1 (en) Automation device with interface for message and port-based access to an application
DE10229877A1 (en) Directory service in an automation system
EP1521486B1 (en) Device and method for controlling communication connections
EP1665651A1 (en) Use of services within a communication network comprising internet mechanisms and within an automation system
EP2645630B1 (en) Adaptive remote service protocol
DE10229879A1 (en) Data processing system with services for the provision of functionalities
EP2469821B1 (en) Method for automatic transmission of information regarding the start-up of a communication terminal suitable for text communication to a communication terminal suitable for speech communication
WO2002103959A2 (en) Method and system for network configuration management and network inventory management
EP1518386B1 (en) System and method for direct communication between automation appliances
EP1499963A2 (en) Automation device comprising an interface for the message-based and port-based access to an application
DE102007053916A1 (en) Method for managing network components in a network and network component
EP1305929A1 (en) System and method for transmitting data via data networks with data conversion by a com automatic marshaller

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

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

17Q First examination report despatched

Effective date: 20090817

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

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

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20161028