EP2250557A1 - Procédé de commande d'une interaction entre des modules d'un composant orienté service et composant orienté service - Google Patents

Procédé de commande d'une interaction entre des modules d'un composant orienté service et composant orienté service

Info

Publication number
EP2250557A1
EP2250557A1 EP09713697A EP09713697A EP2250557A1 EP 2250557 A1 EP2250557 A1 EP 2250557A1 EP 09713697 A EP09713697 A EP 09713697A EP 09713697 A EP09713697 A EP 09713697A EP 2250557 A1 EP2250557 A1 EP 2250557A1
Authority
EP
European Patent Office
Prior art keywords
mod
service
modules
event
oriented
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
EP09713697A
Other languages
German (de)
English (en)
Inventor
Armando Walter Colombo
Joao Marco Mendes
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.)
Schneider Electric Automation GmbH
Original Assignee
Schneider Electric Automation GmbH
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 Schneider Electric Automation GmbH filed Critical Schneider Electric Automation GmbH
Publication of EP2250557A1 publication Critical patent/EP2250557A1/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
    • G06F9/546—Message passing systems or structures, e.g. queues

Definitions

  • the invention relates to a method for controlling an interaction between modules such as communication module, control module, device-interface module of a service-oriented component, a service-oriented component such as an automation device and a software component.
  • IMS Intelligent Manufacturing Systems
  • SOA Service Oriented Architecture
  • service-oriented component Each participant in the system is referred to as a service-oriented component, and in some extensions as a service-oriented automation component, if the component has automatic controllers.
  • Components can have various tasks, such as Production, transport or monitoring and autonomous operation. As services take the lead, these components should have the ability to request services and, conversely, support the request for services from other members of the community. Services themselves are a way of providing resources and actions that may be shared, much like services in real life.
  • a set of equipment and other components of the system may under some circumstances be compared to a "living entity.”
  • a component its internal mechatronic Organizations are compared with functional organs that are responsible for specific tasks that provide "living" characteristics capable of meeting those requirements, a central question is how these functional modules or "organs" are integrated and controlled and are able to exchange events between them, thereby forming complex and effective structures.
  • Service-oriented systems are an approach to specify the environment for heterogeneous "organisms” that require interaction
  • Service business systems are known in the business world and electronic commerce in the field of industrial automation and production systems (especially regarding distributed devices) however, it is a relatively new field of research with promising prospects, and a major starting point was the EU research project SIRENA, which aimed to develop a service infrastructure for embedded real-time network applications.
  • Device Profile Forward Services (DPWS) designed to enable communication between resource-dependent embedded devices.
  • a single service-oriented control device should be ready for a variety of activities;
  • this requires a specially adapted internal frame structure or a programming framework, referred to below as a framework, which can handle the different and competing processes.
  • the object of the present invention is to further develop a method and a service-oriented component and a software component of the type mentioned at the outset in such a way that the interaction between modules is simplified in the case of different and competing processes.
  • the object is achieved according to the invention in that the interaction between the modules is event-based, wherein the event-based interaction between the modules and the synchronization of the modules is controlled via an event flow control module (Event Router Scheduler).
  • Event Router Scheduler Event Router Scheduler
  • an event sequence control module For the event-based connection and synchronization of functional modules in service-oriented components, devices and supporting applications, an event sequence control module is provided.
  • the application particularly relates to automation devices for production facilities and supporting software applications.
  • a service-oriented component is a modular structure composed of various functional modules, including the central event flow control and the required service-oriented communication module, which has the ability to communicate with other components. Because the component is a multi-threaded environment and requires data protection, there must be a mechanism for these tasks that provides each module with an interaction environment.
  • the invention ensures that the communication of automation control component modules takes place only in the case of events. This is useful for controlling the real-time synchronization of these modules and data overwrite protection.
  • each module becomes independent but complementary.
  • the approach allows the developers to program each module independently and to easily know how to process the received information.
  • the "heart" of the puzzle is the Event Router Scheduler module, which provides the following key features:
  • the event router scheduler provides an internal event-driven architecture framework that controls the flow of information for interconnected functional modules.
  • Each module can be programmed independently. This means that it is possible to remove, replace, upgrade (upgrade), add new modules, or just check how information is sent and read.
  • the event router scheduler can be applied and integrated into any software component based on the modular and functional architecture. Several areas of application are noted:
  • the present invention thus addresses an anatomy-like structure for the development of functional and reusable modules of a component as part of a service-oriented automation system.
  • the central focus is on its internal structure, and in particular on the mechanism that binds together the functional modules, referred to as Event Flow Schedulers or Event Router Schedulers.
  • the event flow control can be compared with the nervous system of a living being in the sense of transport / processing of pulses from and to different organs and thus to maintain the dynamic flow of information.
  • Intelligent behavior can be achieved by connecting these nerves to the "brain,” which provides static control based on "work-flow” processes and is also autonomous to respond to unforeseen events, undocumented situations, or internal objectives.
  • Incorporated into a service-oriented environment communication with other components can only be achieved by providing and requesting services to achieve local and global goals.
  • Figure 1 is a schematic representation of a service-oriented automation component of a service-oriented automation and production system.
  • FIG. 2 shows a schematic representation of a modular structure of a service-oriented component
  • FIG. 3 a schematic representation of the composition of a service-oriented component with event sequence control
  • FIG. 5a, b schematic representation of the reading of an event at "locked” module or "open” module
  • Fig. 6 is a schematic representation of a service-oriented component of a mechanical arm and its function.
  • FIG. 1 shows a schematic representation of a service-oriented component SOK and its integration into an automation and production environment of a production facility FS.
  • the illustrated component SOK represents a physical conveyor F and takes over the transport function (task: transport). Communication to the outside world is through services (service orientation) that are able to request or provide services as needed. Integration into the IT environment is also achieved via service orientation.
  • the component includes a set of functions (tasks: transport, monitoring, etc.) that can be used as services provided by the components.
  • service-oriented components may be considered software agents.
  • multi-agent systems are of particular interest as these systems evoke the idea of the collaborative agent community in which each of them can take autonomous actions about their environment or about the system they represent.
  • agent concepts unlike the agent concepts, the true meaning of service orientation is centered on the nature of providing services and the need to request services through a component in the system.
  • the real architecture, environment and objectives of the system are open to the user and thus the system can be adapted to different strategies to meet the requirements.
  • FIG. 2 shows the schematic structure of a component SOK in an anatomical form, comprising a plurality of "organs” (functional modules) responsible for individual tasks, as shown in FIG.
  • the event flow control EAS and the communication modules KOM-MOD are the "kernel" modules for developing a service-oriented component SOK based on the proposed anatomy, which are responsible for both the main framework of the Component (event-based inter-module interaction and integration) and external communication with other components (service-oriented inter-component communication)
  • Other modules MOD can be added to the structure according to the component requirements.
  • the communication module K0M-M0D provides the necessary functions to offer services from the associated components and to request services from other components. Other functions include, but is not limited to, discovery (discovery) and negotiation (negotiation) mechanisms.
  • the remaining modules of the component may use the communication module K0M-M0D to access these functions through pulses (events) provided by the event flow control module EAS-MOD.
  • a conveyor may provide the service "transfer” to effect the movement of pallets controlled by the logic controller module LC-MOD and invoked by the device interface module GI-MOD. Transfer "can be used by other components, but the component itself can also call external services when they are needed (eg for connection with other conveyor belts this calls the service "transfer" of another conveyor belt).
  • a suitable technological solution for implementing the service-oriented communication modules is the use of the web technology and in particular web services.
  • web service technology is quite simple and was developed to move XML (eXtended Markup Language) documents between service processes using standard Internet protocols. This simplicity helps web services achieve the higher goal of interoperability while also requiring the addition of other technologies to realize complex distributed applications.
  • DPWS Device Profiles for Web Service
  • the further modules MOD are briefly described in FIG.
  • the aim is to include the further modules to provide a service-oriented automation component SOK which is a "mediator" for any physical equipment with controllability
  • the resulting component SOK of Figure 2 represents a "smart controller" of the conveyor F, by providing several features such as control and access via the physical device, the ability to make decisions in unforeseen and undocumented situations, and also the possibility of service-oriented communication with other components.
  • a service-oriented PLC-like controller that can interpret control models (e.g., in IEC61131-3 languages) and give other commands necessary calls to these services provided.
  • device interface modules are not necessary because they do not directly instruct the devices.
  • the "nervous system" of the "anatomy” shown in Fig. 2 is managed by the event flow controller EAS (Event Router Scheduler).
  • Event Router Scheduler the event flow controller
  • Components and devices that implement several of the illustrated aspects of service orientation require a consistent anatomy to act on the various functional modules (organs) to meet the necessary requirements.
  • Other problems may arise from the asynchronously powered modules, possibly data inconsistencies and competing processes / threads.
  • a mechanism is proposed that provides an impulse (event) transfer and control feature to direct the "impulses" to different modules, thus enabling a synchronized interaction between them Event Flow Control Module (Event Router Scheduler) EAS-MOD.
  • the EAS-MOD fulfills the following goals:
  • EAS-MOD The function of EAS-MOD is comparable in some parameters to the nervous system of living things, including human beings.
  • the "environment" is detected by specific modules such as communication and device interface modules and mani- puliert.
  • the natural balance of impulses (events) of the individual modules and their integration is achieved with the aid of the event sequence control module EAS-MOD.
  • the event flow control EAS is an event handler for real-time modules SM, GIM, KM of the same application (see FIG. 3). It's like the central piece of a simple puzzle, with the puzzle pieces being the different software modules of the same program. For the most part, it is intended to handle communication between modules during other activity ("on the fly"), which means that each module can send and receive events from all others without the need for synchronization, information loss, data overwriting LC-MOD, GI-MOD To take care of KOM-MOD and other things.
  • component K is implemented in the corresponding device SOK, SOG or the software application after the necessary modules have been connected.
  • component K consists of two required modules, namely event flow control module (EAS) and communication module KOM-MOD, but also a device interface module capable of GI-MOD. To read information from the VO of the associated module or to write to the VO.
  • EAS event flow control module
  • KOM-MOD communication module
  • the main feature is the provision of an event-based interaction between the functional modules and the corresponding scheduling of events (see control and flow of events according to Fig. 4).
  • the internal pulses (events) of the component between its functional modules are managed internally by the event scheduler.
  • the event flow control allows synchronous and asynchronous event calls between all modules, which is very important for real-time applications. It also provides several additional methods for implementing more complex operations, such as events generated by other events and timed events.
  • a transmitter module only needs to send one event to a specific destination (another module), and this event scheduler routes it to its destination.
  • An event is a structure that contains all the information a module needs to identify different possible situations.
  • the structure may request a response for providing information or have an error message receiver, or an event receiver may check if it is a response. It can also be seen when an event has been sent more than once due to an error.
  • the event handler uses lists as means for transmitting and sorting events between the modules so that the number of events awaiting processing is limited only by the available memory.
  • the event flow control uses some techniques to avoid memory fragmentation, since data generation and deletion is a very common function in the modules. In some cases, when the number of events is high, the event flow control provides the opportunity to give the events different priorities. An event sent to a particular module will always be passed by all waiting events of that module which have a lower priority than the priority of the sent event.
  • the system is capable of performing both synchronous and asynchronous operations, with asynchronous operations being managed by threads.
  • the synchronous operations may be either “frozen” or “not frozen” for the recipient.
  • the operation may or may not be a "freeze module.”
  • the module will freeze until a new event arrives for that module. Subsequently, the module continues the normal process, as shown in Fig. 5a.
  • This is a process with very low CPU resource utilization, which is particularly suitable for embedded devices. However, it does not make sense for real-time multi-tasking modules because these types of modules should not be "frozen.”
  • the "non-solidified" event readers always receive an event. However, this can be an invalid event.
  • An invalid Event means that there are no events for the module so that it can continue working with other tasks. If it is a valid event, the module should continue with this. This is shown in Fig. 5b.
  • Asynchronous event triggering is also possible.
  • callbacks are used to execute this operation type because it must occur when it is called.
  • MUTEX Mutual Exclusion
  • Each module has a MUTEX for this case.
  • the remaining blocks according to FIG. 4 are responsible for adjacent tasks of the control (scheduling) and the routing of events, in particular for the management of the own module and the further modules.
  • the hardware / software abstraction allows system architecture functional transparency that can be accessed by all modules. Since the event flow control module and other modules are in a multi-functional and concurrent environment, a special EAS block TDK performs simple thread manipulation and data protection. The block is referred to as threading and data consistency block TDK.
  • the "Template / Interface for Event-based Modules" block provides T / I with a basis for creating functional modules and links them to the event flow control, each module can be independently programmed, which means that it is possible removing, exchanging, extending or adding new modules makes this very flexible, a program that uses EAS, the module ID, is the identification of the module and unique for each module, which must be known by the other modules sending an event to a specific module, which is similar to the code that the nerves carry to reach certain organs, but it is also possible to do a module based on it of its type such as "controller” or "user interface", since this way is much more convenient for a developer to achieve a module without much information.
  • Fig. 6 shows by way of example the service-oriented component of a mechanical arm and its operation.
  • the functions provided by the framework for developing and operating the component are shown.
  • the framework consists of the EAS and three modules, the logic controller LC-MOD, the device interface GI-MOD and the communication module KOM-MOD.
  • the invention provides a framework for the development of service-oriented automation systems, particularly suitable for the mechanism of transmission of events between different functional modules forming the component.
  • the adaptation of this "biologically inspired” modular structure allows the design and development of modules with unique and independent functions, but these are complementary to each other to enable the formation of complex, intelligent and “social” components.
  • the resulting component structure is characterized by a shortened development time and low integration effort into a system.
  • the invention discloses an anatomical structure for the development of functional and reusable modules of service-oriented automation components.
  • the central focus is on the internal structure and mechanism that connects the modules together and is called Event Router Scheduler.
  • the resulting software automation components are custom designed for various applications due to the inclusion and management of the specialized functional modules and provide the ability to operate in a service-oriented automation and production environment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un procédé de commande d'une interaction entre des modules tels qu'un module de communication (KOM-MOD), un module de commande (LC-MOD), un module d'interface d'appareils (GI-MOD) d'un composant orienté service (SOK). L'invention vise à simplifier l'interaction entre des modules lors de processus différents et concurrents. A cet effet, l'interaction entre les modules (KOM-MOD; LC-MOD; GI-MOD) est basée sur les événements, les modules (KOM-MOD; LC-MOD; GI-MOD) étant couplés par un module de commande de déroulement d'événement (EAS-MOD) pour fournir une commande de déroulement d'événement afin de relier et de synchroniser les modules (KOM-MOD; LC-MOD; GI-MOD) sur la base d'événements.
EP09713697A 2008-02-29 2009-02-27 Procédé de commande d'une interaction entre des modules d'un composant orienté service et composant orienté service Withdrawn EP2250557A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102008002785A DE102008002785A1 (de) 2008-02-29 2008-02-29 Event-Router-Scheduler-Modul für die eventbasierte Verbindung und Synchronisation funktioneller Module in serviceorientierten Komponenten, Geräten und unterstützenden Anwendungen
PCT/EP2009/052421 WO2009106638A1 (fr) 2008-02-29 2009-02-27 Procédé de commande d'une interaction entre des modules d'un composant orienté service et composant orienté service

Publications (1)

Publication Number Publication Date
EP2250557A1 true EP2250557A1 (fr) 2010-11-17

Family

ID=40790894

Family Applications (1)

Application Number Title Priority Date Filing Date
EP09713697A Withdrawn EP2250557A1 (fr) 2008-02-29 2009-02-27 Procédé de commande d'une interaction entre des modules d'un composant orienté service et composant orienté service

Country Status (6)

Country Link
US (1) US20110055849A1 (fr)
EP (1) EP2250557A1 (fr)
JP (1) JP2011513822A (fr)
CN (1) CN102265260B (fr)
DE (1) DE102008002785A1 (fr)
WO (1) WO2009106638A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CH705456A1 (de) * 2011-08-31 2013-03-15 Ferag Ag Computerisiertes Maschinensteuerungssystem.
JP7087402B2 (ja) 2018-01-19 2022-06-21 富士フイルムビジネスイノベーション株式会社 処理装置、処理システム、及びプログラム

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6470386B1 (en) * 1997-09-26 2002-10-22 Worldcom, Inc. Integrated proxy interface for web based telecommunications management tools
US6691302B1 (en) * 2000-05-31 2004-02-10 Siemens Information & Communications Networks, Inc. Interfacing a service component to a native API
US7035944B2 (en) * 2001-09-19 2006-04-25 International Business Machines Corporation Programmatic management of software resources in a content framework environment
US20040177335A1 (en) * 2003-03-04 2004-09-09 International Business Machines Corporation Enterprise services application program development model
US7581205B1 (en) * 2003-09-30 2009-08-25 Nextaxiom Technology, Inc. System and method of implementing a customizable software platform
CN101208649B (zh) * 2005-04-25 2010-12-08 因文西斯系统公司 用于处理制造环境所引起的生产事件的系统和方法
JP4868799B2 (ja) * 2005-08-31 2012-02-01 キヤノン株式会社 サーバ装置及びイベント通知方法
CN100476649C (zh) * 2006-08-16 2009-04-08 中山大学 一种车载智能控制装置和方法
CN1975778A (zh) * 2006-11-03 2007-06-06 中山大学 一种数字家庭物品查找装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
EDWARD CURRY ED - ED : QUSAY H MAHMOUD: "CHAPTER 1: Message-Oriented Middleware", 1 January 2004, MIDDLEWARE FOR COMMUNICATIONS, JOHN WILEY & SONS, LTD, PAGE(S) 1 - 28, ISBN: 978-0-470-86206-3, XP007911233 *

Also Published As

Publication number Publication date
US20110055849A1 (en) 2011-03-03
JP2011513822A (ja) 2011-04-28
CN102265260B (zh) 2015-08-19
CN102265260A (zh) 2011-11-30
WO2009106638A1 (fr) 2009-09-03
DE102008002785A1 (de) 2009-10-15

Similar Documents

Publication Publication Date Title
DE60038705T2 (de) Verfahren und vorrichtung für die aktivitäts-basierte zusammenarbeit eines rechnersystems, ausgestattet mit einem kommunikations-manager
DE112016006786T5 (de) Ressourcenorchestrierungsbrokerage für Internet-Der-Dinge-Netzwerke
WO2003050680A2 (fr) Systeme et procede de communication entre des applications logicielles, en particulier des applications mes
DE10206902A1 (de) Engineeringverfahren und Engineeringsystem für industrielle Automatisierungssysteme
DE102006051189A1 (de) Verfahren und System zum Ausführen und Konfigurieren von Applikationen abhängig von einer Einsatzumgebung
EP2342607A1 (fr) Procédé pour développer un système multi-agents, ainsi que système multi-agents
EP2100198A1 (fr) Système de commande ainsi que procédé pour la configuration d'un système de commande
LU93299B1 (de) Ablaufsteuerung von Programmmodulen
WO2007012499A2 (fr) Architecture ai generique d'un systeme multi-agent
WO2009101212A1 (fr) Procédé et système pour intégrer des composants d'automatisation orientés sur les services d'un atelier de montage dans une architecture informatique d'entreprise flexible
EP2250557A1 (fr) Procédé de commande d'une interaction entre des modules d'un composant orienté service et composant orienté service
WO2024046817A1 (fr) Dispositif de commande à fonction dds
EP1442340A1 (fr) Chargement de donnees dans un systeme d'automatisation
DE102006051188A1 (de) Flexibles Verschaltungssystem
Grolik et al. Dispositive Supply-Web-Koordination durch Multiagentensysteme
EP2090948B1 (fr) Procédé de fonctionnement d'un système d'automatisation
DE112007002327T5 (de) Persistente Sperren auf Ressourcen zur Steuerung der Nebenläufigkeit
DE102004011201A1 (de) Verfahren zum Management und zur Überwachung des Betriebs mehrerer in wenigstens ein Kommunikationsnetz eingebundener verteilter Hard- und/oder Softwaresysteme sowie System zur Durchführung des Verfahrens
Mordinyi Managing complex and dynamic software systems with space-based computing
DE102016121542A1 (de) Ablaufsteuerung von Programmmodulen
Kenzler et al. Segment Routing v6 (SRv6) Network Programming
DE60308325T2 (de) Informationswegeleitung
DE102019203874A1 (de) Verfahren und Vorrichtungen für eine Lastzuweisung und Überwachung für eine zuzuweisende versorgungssicherheitskritische Ressource in einem Netzwerk
EP4390581A1 (fr) Procédé et système d'ingénierie pour la conception et la programmation d'un agencement d'automatisation industriel doté d'un certain nombre de composants d'automatisation
DE3301282A1 (de) Verfahren und vorrichtung zur uebertragung von nachrichten zwischen automatisierungsmitteln

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): 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 SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA RS

RIN1 Information on inventor provided before grant (corrected)

Inventor name: MENDES, JOAO MARCO

Inventor name: COLOMBO, ARMANDO WALTER

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

Effective date: 20141201

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