[go: up one dir, main page]

EP2430810A1 - Procédé permettant d'assurer la communication entre un certain nombre de premiers services et un certain nombre de deuxièmes services - Google Patents

Procédé permettant d'assurer la communication entre un certain nombre de premiers services et un certain nombre de deuxièmes services

Info

Publication number
EP2430810A1
EP2430810A1 EP10719933A EP10719933A EP2430810A1 EP 2430810 A1 EP2430810 A1 EP 2430810A1 EP 10719933 A EP10719933 A EP 10719933A EP 10719933 A EP10719933 A EP 10719933A EP 2430810 A1 EP2430810 A1 EP 2430810A1
Authority
EP
European Patent Office
Prior art keywords
service
services
data
sei
converter
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
EP10719933A
Other languages
German (de)
English (en)
Inventor
Christian Buckl
Jörg Heuer
Anton Schmitt
Andreas Scholz
Martin Winter
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
Application filed by Siemens AG, Siemens Corp filed Critical Siemens AG
Publication of EP2430810A1 publication Critical patent/EP2430810A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • 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/08—Protocols for interworking; Protocol conversion
    • 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
    • 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/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching

Definitions

  • the invention relates to a method for communication between a number of first services and a number of second services.
  • Services are also performed in a data-driven architecture, which is used for example in so-called embedded networks.
  • a data-driven architecture which is used for example in so-called embedded networks.
  • an input with a corresponding data input and an output with a corresponding data output are specified for a service, wherein a data input generates a corresponding data output.
  • Several services can be interconnected to a service chaining, with the help of a suitable protocol, the corresponding data inputs and data outputs of the services and the forwarding of the data between the services can be set.
  • the service chainings can be easily changed without having to adjust the services themselves. In this way, in a data-driven architecture, a flexible and quickly feasible adaptation of service chainings can be achieved.
  • the different service architectures are used side by side, and so far there is no interface that converts the services of one architecture into corresponding services of the other architecture.
  • the object of the invention is therefore to provide a method for communication between a number of first services and a number of second services, with which different service architectures can communicate with each other.
  • the method according to the invention serves for communication between a number of first services and a number of second services, the number of first services belonging to a service-oriented architecture, in which a respective first service is based on messages based on a request-response Mechanism is provided by means of a first protocol, and wherein the number of second services belongs to a data-driven architecture in which the second services are connectable by means of a second protocol, the second protocol data inputs and data outputs of the second services and the forwarding of data specified between the second services.
  • the term of the request-response mechanism is to be understood broadly and includes not only the receipt of a request and an immediately sent out response, but possibly also subscriptions, according to which corresponding notifications of a first service are sent out due to the subscription. In this sense, a request is then represented by a subscription, which corresponding
  • Responses generated in the form of notifications Under data input or data output is the reception of data to understand an input of the service or the output of data at an output of the service.
  • the second protocol specifies a corresponding message for data input or data output, which contains the entered or output data and determines whether it is a data input or a data output.
  • the message contains an identifier or identifier for the service at which the data input or data output takes place.
  • a message of a first service arriving in a service converter is converted into a data input of a second service assigned to the first service and / or a data output of a second service entering into the service converter is transferred to one of the service providers.
  • Converter outgoing message of the second service associated with the first service converted.
  • the number of first services comprises one or more web services which are well known in the art.
  • SOAP Simple Object Access Protocol
  • the second services are preferably services distributed in a network, wherein the network is in particular a so-called embedded network. Embedded networks are well known in the art and allow the embedding of services in suitable network nodes, for example Sensors, actuators or other electronic units.
  • the second services are interconnected in the network at least partially by means of one or more service chainings specified via the second protocol.
  • a message arriving in the service converter of a first service in the form of a requesting entity is converted to the first service into a data input of a second service associated with the first service, and then a data output is issued the second service or another second service, which is also associated with the first service and is connected to the second service, converted to a message originating from the service converter of the first service in the form of a response message to the request message.
  • the first service is a service implemented in the service converter.
  • one or more data outputs of one or more second services are stored in a buffer and provided to the service converter via the buffer, wherein the data output or outputs are preferably generated periodically.
  • data outputs from second services can be retrieved via a first service without the data output having to be triggered by an event.
  • the buffer is implemented as a separate second service in which data entries stored, for example via data inputs which represent converted query messages to a first service, can be used to call up buffered data outputs which are data outputs that are converted into corresponding response messages of a first service.
  • WSDL Web Service Description Language
  • a data output of a second service arriving in the service converter is converted into the first service in the form of a request message in a first service assigned to the second service by the service converter.
  • a first service can be addressed via a data output of a second service.
  • the response message of the first service which is based on the request message is preferably converted by the service converter into a data input of the second service.
  • a first service subscribes or subscribes to predetermined data outputs of a second service, wherein a predetermined data output of the second service in the service converter in the service converter is converted into a message originating from the service converter first service is converted.
  • the predetermined data outputs are in particular periodic data outputs.
  • a first service can easily retrieve data outputs of a second service.
  • a message of a first service in the form of a response message of the first service which has been sent to the first service in response to a request message previously sent by the service converter is input into a data input a second service associated with the first service. In this way, data can be retrieved from a first service via a second service as appropriate.
  • the service converter subscribes to predetermined messages of a first service, a predetermined message of the first service arriving in the service converter in the service converter being converted into a data input of a second service associated with the first service ,
  • the messages arriving at the service converter are generated periodically.
  • data of a first service can be provided to a second service in a simple manner via a subscription mechanism.
  • the first and / or second services are at least partially implemented on the service converter.
  • the second services can be implemented as virtual services, via which the conversion of incoming messages of first services into corresponding data inputs of second services or the conversion of data outputs of second services into outgoing messages of first services are realized.
  • the invention further relates to a service converter for communication between a number of first services and a number of second services, the number of first services belonging to a service-oriented architecture which a respective service is provided via messages based on a request-response mechanism by means of a first protocol, and wherein the number of second services belongs to a data-driven architecture in which the second services are interconnectable by means of a second protocol, the second Protocol data entries and data outputs of the second services and the forwarding of data between the second services specified.
  • the service converter in this case comprises a first converter means for converting a message of a first service incoming in the service converter into a data input of a second service associated with the first service and / or a second converter means for converting one in the service converter incoming data output of a second service in a outgoing from the service converter message of the second service associated with the first service.
  • the service converter is configured such that one or more of the preferred embodiments of the inventive method described above can be carried out with the service converter.
  • 1 shows a network of several network nodes, in which second services are embedded
  • FIG. 2 shows the network of FIG. 1, showing the execution of embedded services based on a variant of a second protocol
  • FIG. Fig. 3 shows the network of Fig. 1, which represents a dynamic repositioning of the embedded services
  • FIG. 4 shows a schematic representation of a communication between first and second services by means of a service converter according to an embodiment of the invention
  • FIGS. 5 to 8 show different forms of the method according to the invention for communication between a first and a second service
  • FIG. 9 is a schematic illustration of an example scenario based on a blind control in which second services are executed by means of service chaining;
  • Fig. 10 is a schematic representation of an embodiment of the invention in which a first service to the service converter is realized via a WSDL document;
  • Fig. 11 is a schematic representation which the
  • this network comprises the network nodes N1, N2, N3, N4 and N5, which can represent different types of devices that can communicate with each other wirelessly and / or by wire.
  • the network nodes can represent sensors, actuators, pure computer units and a combination of these devices.
  • Second services are implemented on some of the nodes, which are indicated by gears labeled SEI, SE2, SE3, SE4 and SE5.
  • SEI, SE2, SE3, SE4 and SE5. are indicated by gears labeled SEI, SE2, SE3, SE4 and SE5.
  • a plurality of second services are distributed in the network, wherein these second services can communicate with each other via a second protocol and can be interconnected with each other.
  • This second protocol is based on data-driven communication in the network of FIG. 1.
  • receiving a datum may initiate the processing step of forwarding data. This type of data processing is used because it involves low delays and low communication overhead between the network nodes of the network.
  • the communication between the individual second services according to the second protocol proceeds in such a way that for each service a data input and a data output are specified and via the protocol for a data output of a respective second service it is determined to which services the output data is corresponding Data input should be forwarded.
  • the services are interconnected externally via the second protocol, where the knowledge about the routing of data between the services is determined via correspondingly specified data paths between the services. It is not known to the individual services to which service their data output is forwarded or from which service they receive a data input. This knowledge is specified based on a middleware by the second protocol.
  • the advantage is achieved that without the change of services, the concatenation of services in an appropriate manner on the adjustment can be changed by means of the second protocol specified data paths.
  • optimized data paths with the least possible amount of transmitted data can be implemented in the network. If e.g. If a data value of more than one service is used, then an optimized data path is determined such that as far as possible the transport of a data packet towards the destination takes place only once and the division into several data packets to different receiving nodes at optimized locations, e.g. as late as possible. For this purpose, the
  • Structures of the various applications realized via distributed services are collected at one or more central points in the network and there examined for possible overlaps of the data paths and optimized. Based on the results of this analysis, forwarding rules are determined that specify one or more services or nodes for forwarding based on a corresponding source address of the service.
  • source addresses are used which do not specify the transmitting network node but identify the transmitting service.
  • an identifier of the data content or its type can be used for the source addressing.
  • Fig. 2 illustrates the optimization just described.
  • a service chaining is realized starting from the service SEI to the service SE4, and a service chaining from the service SEI to the service SE5 is implemented by a second application.
  • the transmitted data between the services is first transmitted via the common data paths DPI and DP2, and only in the service SE3 is a division into the data paths DP3 and DP4 carried out, wherein according to the data path DP3 the Data about the service SE5 and according to the data path DP4 the data arrive at the service SE4.
  • a forwarding of messages between the network nodes is carried out such that the greatest possible combination of the transmission path for a message to multiple recipients based on the identification of the message with the source address and an assignment of the source address to receiving nodes or services is realized. This leads to a reduction in the number of forwarding rules on the common transmission path.
  • a repositioning of services distributed in the network is realized, so that the services are moved dynamically from one network node to another and additionally forwarding instructions based on the source address, which are additionally required on the new data paths. be installed in the network.
  • This variant is illustrated in FIG. It can be seen that, in contrast to FIG. 1 and FIG. 2, the service SE2, which was initially on the node N1, now lies on the node N3 and the service SE3, which was previously on the service N4, now on the node N5 lies.
  • An application via a concatenation of the service SEI to the service SE3 via the service SE2 is indicated by the data paths DP5 and DP6.
  • networks with complex distributed applications can achieve significant communication bandwidth savings. This means especially for wireless network nodes with battery power also a significant reduction in energy consumption and thus in many cases a longer battery life.
  • wireless network nodes with battery power also a significant reduction in energy consumption and thus in many cases a longer battery life.
  • the services there is the further advantage that they do not explicitly know their communication partners and need to manage.
  • the entire communication structure is mapped in the routing rules implemented outside of the services using a second protocol, this second protocol managing the services via corresponding identifiers and specifying data paths between the individual services.
  • the data-driven architecture DA is indicated in the lower part of FIG. 4 and the service-oriented architecture SA in the upper part of FIG. 4.
  • Network nodes in the data-driven architecture are again denoted by corresponding reference symbols N1, N2, N3, N4 and N5 denotes.
  • second services in the form of embedded services are designated by corresponding reference symbols SEI, SE2, SE3, SE4, SE5 and SE6.
  • first services in the service-oriented architecture SA are designated WS1, WS2 and WS3, wherein in the embodiment of FIG. 4 the first services are implemented in the form of known web services.
  • a client computer in the service-oriented architecture SA is designated C. Via this computer appropriate web services can be called up.
  • the service-oriented architecture SA and the data-driven architecture DA are linked to one another via a service converter in the form of a service bridge SB, wherein web services or second services can be implemented on the service bridge itself.
  • the web service WS3 and the second service SE6 represent services installed on the service bridge SB.
  • Communication with a web service in the service-oriented architecture SA is based on a request Response mechanism according to which a request can be made by a client to a web service, whereupon the request is answered by an appropriate response.
  • the requests and responses thereby represent messages according to a protocol of the service-oriented architecture.
  • SOAP Simple Object Access Protocol
  • the module M2 serves to convert a data output from a data-driven architecture DA of a corresponding embedded service into a suitable message of the service-oriented architecture SA.
  • the client C makes a web service request to one of the web services of the service-oriented architecture SA.
  • This web service request is associated with a data input at the input El of the first embedded service SEI.
  • the service bridge SB forwards the request to the input El of the addressed embedded service SEI by generating a corresponding data input from the request in accordance with the second protocol of the data-driven architecture.
  • a variant al) corresponds to Data output at the output Al of the embedded service SEI a corresponding response of the addressed in the service-oriented architecture web services.
  • the service bridge immediately generates a response as a function of the data output at the output A1 of the embedded service SEI and sends it via the web service addressed by the request to the client C.
  • the service bridge SB sends the corresponding response back to the requesting client C as soon as the output data arrives at the output A2 of the second embedded service SE2 according to a concatenation of the embedded services and is transmitted from there to the service bridge. In this way, a mapping of a distributed execution of embedded services of the data-driven architecture DA to a service-oriented architecture web service takes place.
  • web services can be called up via the service bridge SB and realized by service links, so that state information or output signals of the embedded services are buffered continuously on the service bridge.
  • a suitable cache is used, which is installed in the service bridge or assigned to it.
  • a client C in turn makes a request to a service-oriented architecture web service. This request is in turn linked to the input El of the first embedded service SEI and an output A2 of the second embedded service SE2. This in turn realizes a chain of services in the data-driven architecture.
  • the service bridge SB responds to the request sent by the client with output values of the second embedded service, these output values being cached in the cache.
  • the service bridge SB is configured as part of a service chaining within the data-driven architecture DA.
  • the output A1 of the first service SEI is connected to the service bridge, which forwards the output signal as a request to a web service of the service-oriented architecture.
  • the service bridge SB may be connected to the input E2 of the second embedded service SE2, so that the response of said web service is forwarded to this input.
  • This variant thus provides a web service from the service-oriented architecture in the data-driven architecture.
  • the service bridge SB is again configured as part of a service chain by connecting the service bridge SB to the input El of the embedded service SEI, so that response messages of a web service of the service-oriented architecture SA are forwarded to this input. Furthermore, the service chaining service bridge is configured to dispatch certain web service requests so that the web service responses are forwarded to the input of the embedded service El. As a result, the service bridge makes a web service available in the data-driven architecture DA.
  • the embedded services accessible via the service bridge SB can, for example, be identified and addressed via a URI (Universal Resource Indicator).
  • this URI directly represents the address of the corresponding embedded service.
  • the URI can also address a service of the service bridge, which in turn addresses the desired embedded service via information in the request.
  • the above-described cases a) and b) can also be combined in a preferred embodiment so that a web service request from the service-oriented architecture is answered with a value buffered in the service bridge.
  • the Web service messages in the service-oriented architecture are based on textual XML messages
  • the data inputs in the data-driven architecture contain binary XML messages
  • the corresponding message of the second protocol also specifies whether the message is a data input or a data output and to which second service it belongs.
  • the web service implements a corresponding conversion of textual XML messages into binary XML messages and vice versa.
  • the service bridge can wrap and unpack web service messages in accordance with the SOAP protocol and forward them to embedded services or web services based on a corresponding conversion.
  • the linking of queries and responses of web services with data input and data output from embedded services can, for example, be achieved via a WSDL document.
  • This document which is provided by the service bridge, describes for an appropriate web service the expected request and the responses based thereon, which are linked in the service bridge with a corresponding data input of a service and a corresponding data output of a service .
  • the bridge also specifies the corresponding concatenation of the services from the service at which the data input takes place to the service at which the data output takes place.
  • the concatenation can be optimized in a suitable way, as described above with reference to FIGS. 1 to 3.
  • the WSDL document does not already have to be available in the service bridge, but is only generated when needed, ie when the web service is addressed via a URI.
  • access to embedded services via web services according to the above variants a) and b) may be restricted to certain services.
  • a web service request may be compiled from data outputs of multiple embedded services on the service bridge, and / or one or more portions of the web service responses are each associated with one or more data inputs from embedded services.
  • FIG. 5 and FIG. 6 show exemplary embodiments of the above-described variants a) and b), whereas FIG. 7 and FIG. 8 illustrate further variants of a communication according to the invention.
  • SOAP Simple Object Access Protocol
  • all messages are on the right-hand side the service bridge SB are specified as data inputs or data outputs according to the second protocol of the data-driven architecture.
  • the structure of the messages of the second protocol is such that in the message it is specified on the one hand, whether it is the message is a data input or a data output, and on the other hand, which service the data input or data output is assigned.
  • the client C directs a web service request RE to a web service which runs on the service bridge SB.
  • This request is forwarded as a corresponding data input DI to the embedded service SEI, whereupon the embedded service SEI generates a data output DO at its output, which is converted via the service bridge SB into a response message RS of the web service.
  • the embedded service SEI generates a data output DO at its output, which is converted via the service bridge SB into a response message RS of the web service.
  • incoming Web service requests translated into data entries in the data-driven architecture DA.
  • the web service requests are postponed until the requested data arrives at the service bridge.
  • the deferred request message RE is reactivated and an appropriate web service response message RS is generated, which is then transmitted to the client C.
  • the embedded service SEI behaves like a requestable web service.
  • a cache in the form of a cache CA is used.
  • the cache CA retrieves stored data, especially in the event that embedded services can not be triggered, for example to provide readings.
  • a request message RE of a client C is sent to the service bridge SB.
  • the request message RE is reset in the service bridge SB and a data input DI corresponding to the request is generated, which however is now directed not directly to the embedded service SEI, but to the cache CA in which data of the embedded service SEI are cached.
  • These data are transmitted to the cache CA by the embedded service SEI as part of periodic updates PA.
  • the data input DI to the cache in turn triggers a data output DO, according to which the corresponding buffered data of the embedded service SEI are transmitted to the service bridge SB.
  • the cache is provided as a separate embedded service that stores the most recent metric provided by the embedded service SEI.
  • the cache can be queried in this way analogously to the embedded service SEI according to the variant of FIG. 5.
  • Fig. 7 shows a scenario in which data of an embedded service SEI is periodically retrieved by a client C.
  • the client subscribes / subscribes to it by him desired data provided by the corresponding embedded service SEI via a subscription SU to a service bridge web service.
  • This WS-Eventing is a special subscription method of the standard web service.
  • the data generated by the embedded service SEI are transmitted to the service bridge SB via data outputs DO in the form of periodic data deliveries.
  • the data is converted into periodic messages PN (e.g., WS-Eventing Notifications) and forwarded to the client C.
  • periodic messages PN e.g., WS-Eventing Notifications
  • a periodic data entry is made to the embedded service SEI.
  • the service bridge SB subscribes via a corresponding subscription SU to a web service of an external data source of a client C, again with the WS-eventing described above.
  • periodic notifications PN concerning the data of the external data source are supplied to the service bridge SB, which converts these notifications into a corresponding message format in the data-driven architecture DA and as data inputs DI in the form of periodic data transmissions to the embedded service sends SEI.
  • FIG. 9 A specific realization of a data-driven architecture in the form of a blind control is described below with reference to FIGS. 9 to 11, wherein this architecture can be suitably addressed via a service bridge by means of a web service.
  • the boxes of FIG. 9 represent embedded services, which are each designated by reference symbols SEI to SE9.
  • the bold-edged services SEI and SE2 are so-called virtual services, which are stored on the service bridge SB and represent placeholders for web service interactions in a service-oriented architecture.
  • the virtual service SEI is a user Assigned input Web service, wherein the service bridge a request to the Web service is converted into a data input of the service SEI, which generates a corresponding data output of the virtual user input service SEI.
  • the virtual service SE2 is an output service from whose data output in the service bridge the corresponding response of the user input web service is generated.
  • the other services shown in FIG. 9 do not have to be implemented in the service bridge and have the following functions:
  • SE5 stop sensor (top)
  • SE6 stop sensor (bottom)
  • a blind control is achieved, which based on a user input or on the data of a wind sensor or a brightness sensor, taking into account a suitable prioritization of the data by means of a control logic, a motor to start up and shutdown of a blind, whereby the uppermost position of the blind is detected by means of a corresponding stop sensor (top) and the lowest position of the blind is detected via a corresponding stop sensor (bottom), whereupon the shutter stops.
  • a control logic a motor to start up and shutdown of a blind, whereby the uppermost position of the blind is detected by means of a corresponding stop sensor (top) and the lowest position of the blind is detected via a corresponding stop sensor (bottom), whereupon the shutter stops.
  • the output service SE2 In response to a user input of the service SEI specifying a desired position of the blind, the output service SE2 generates an output which tells which position the blind is actually following processing the services chaining is located.
  • the above-described services SEI and SE2 should be available via an associated web service from the Internet, for example, to allow remote monitoring via a mobile phone. Due to the fact that a required user-determined position of the blind can be overwritten by the wind sensor according to the service SE3, the final position of the blind should be notified in response to user inputs via the output service SE2 ,
  • Fig. 10 shows how, based on the data-driven services SEI and SE2 of Fig. 9, a suitable WSDL document may be generated for use by a web service associated with the services SEI and SE2.
  • the blocks SD1 and SD2 represent the corresponding service description of the service SEI concerning the user input or the service SE2 concerning the output.
  • a data output in the form of a parameter is generated in float format, which represents the desired position of the blind.
  • a data output is generated in the form of a parameter in float format representing the actual position of the blind.
  • the service descriptions SD1 and SD2 are linked to the WSDL document D, of which only the parts relevant to the invention are reproduced and which in the upper part contains an XML schema definition of two types T1 and T2.
  • the type Tl represents the request to a web service and is designated with the element name "UserlnputRequest.”
  • the type T2 specifies a response of the web service and is designated with the element name "OutputResponse”.
  • Further down in the WSDL document D are the definitions of corresponding messages ME1 and ME2, where the message ME1 of the request of the web service in the form of The message ME2 corresponds to the response of the web service in the form of the actual blind position and is called "SetPositionOutput".
  • the definition of the messages ME1 and ME2 is followed by the corresponding addresses in the form of URI indicators to which the messages are to be sent. These addresses are not shown in FIG.
  • the WSDL document specifies a single communication endpoint for interaction with the embedded services, which - as shown in FIG. 9 - are concatenated with each other. This allows data from different embedded services to be received and sent at different locations in a corresponding daisy chain.
  • Web services that are associated with appropriate data inputs or data outputs at the beginning or at the end of the chaining of services.
  • the WSDL document may be generated in advance based on the embedded service chainings specified in the second protocol, where a URI is generated to address the service chain as soon as the service chaining is instantiated.
  • a URI may also be generated without instantiation, wherein the instantiation is then performed as soon as the URI is addressed by a web service.
  • the block RE represents a request to the web service in the form of a desired blind position "targetPosition" at 1.0
  • This request is represented by a textual XML document, which is referred to as D1, after which this textual SOAP message is converted into a so-called binary EXI file.
  • EXI Efficient XML Interchange
  • the message DI is then further processed in the concatenation of the embedded services, which is reproduced in FIG. 9 and designated SK in FIG. 11.
  • the service chaining is addressed by the URI already mentioned above.
  • the data input DI is addressed to all services that consume data established by the virtual service of the user input SEI.
  • this is the service SE3 which describes a prioritization between the outputs of the services SEI, SE3 and SE4.
  • a data output DO is finally generated which has the same format as the data input DI and is output by the virtual service SE2.
  • This data output DO again contains an EXI-coded SOAP message as well as the name of the service SE2 and the information that this is a data output.
  • This message DO is then in turn converted in the service bridge into a corresponding response RS of the web service, which takes place in that the EXI-coded SOAP message, which is contained in the data output DO, in the textual XML document D2 which specifies the position 1.0 as the final position "finalPosition" of the blind.
  • the SOAP message according to the document D2 is then given as a response RS to the web service.
  • the above described request / response interactions require storage of a map of SOAP messages and triggered messages or interactions in the data driven architecture to enable messages coming from one of the embedded services of the service chain to the right waiting web server.
  • Service request The web service endpoint created by the above-described WSDL
  • the method according to the invention achieves appropriate communication between services of a service-oriented architecture, defined by request-response mechanisms, in a data-driven architecture, which is supported by data entries and data outputs of services and services the routing of data between the services is specified.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente invention concerne un procédé permettant d'assurer la communication entre un certain nombre de premiers services (WS1, WS2, WS3) et un certain nombre de deuxièmes services (SE1, SE2,..., SE9). Lesdits premiers services (WS1, WS2, WS3) appartiennent à une architecture orientée service (SA) dans laquelle un premier service (WS1, WS2, WS3) respectif est fourni par l'intermédiaire de messages (RE, RS, SU, PN) sur la base d'un mécanisme demande-réponse au moyen d'un premier protocole. Lesdits deuxièmes services (SE1, SE2,..., SE9) appartiennent à une architecture orientée données (DA) dans laquelle de deuxièmes services (SE1, SE2,..., SE9) peuvent être commutés entre eux au moyen d'un deuxième protocole. Le deuxième protocole spécifie des entrées de données (DI) et des sorties de données (DO) des deuxièmes services (SE1, SE2,..., SE9) et le transfert de données entre les deuxièmes services (SE1, SE2,..., SE9). Le procédé se caractérise en ce qu'un message (RE, RS, PN) d'un premier service (WS1, WS2, WS3), entrant dans un convertisseur de service (SB), est converti en une entrée de données (DI) d'un deuxième service (SE1, SE2,..., SE9) associé au premier service (WS1, WS2, WS3) et/ou en ce qu'une sortie de données (DO) d'un deuxième service (SE1, SE2,..., SE9), entrant dans le convertisseur de service (SB), est convertie en un message (RE, RS, PN), émis par le convertisseur de service (SB), d'un premier service (WS1, WS2, WS3) associé au deuxième service (SE1, SE2,..., SE9). Les premiers services peuvent être des services web.
EP10719933A 2009-05-12 2010-04-29 Procédé permettant d'assurer la communication entre un certain nombre de premiers services et un certain nombre de deuxièmes services Withdrawn EP2430810A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102009020929 2009-05-12
PCT/EP2010/055816 WO2010130585A1 (fr) 2009-05-12 2010-04-29 Procédé permettant d'assurer la communication entre un certain nombre de premiers services et un certain nombre de deuxièmes services

Publications (1)

Publication Number Publication Date
EP2430810A1 true EP2430810A1 (fr) 2012-03-21

Family

ID=42269535

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10719933A Withdrawn EP2430810A1 (fr) 2009-05-12 2010-04-29 Procédé permettant d'assurer la communication entre un certain nombre de premiers services et un certain nombre de deuxièmes services

Country Status (4)

Country Link
US (1) US9277031B2 (fr)
EP (1) EP2430810A1 (fr)
CN (1) CN102422616B (fr)
WO (1) WO2010130585A1 (fr)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8112262B1 (en) 2008-09-30 2012-02-07 Interactive TKO, Inc. Service modeling and virtualization
US20140036852A1 (en) * 2011-05-27 2014-02-06 Alcatel-Lucent Method of communication under network condition converging cellular network and wlan
EP2557752B1 (fr) * 2011-08-11 2017-09-27 Siemens Aktiengesellschaft Procédé et dispositif de fabrication d'une communication bout-à-bout entre deux réseaux
US9558105B2 (en) 2013-03-15 2017-01-31 Ca, Inc. Transactional boundaries for virtual model generation
US10025839B2 (en) 2013-11-29 2018-07-17 Ca, Inc. Database virtualization
US9727314B2 (en) 2014-03-21 2017-08-08 Ca, Inc. Composite virtual services
US9531609B2 (en) 2014-03-23 2016-12-27 Ca, Inc. Virtual service automation
US9477454B2 (en) 2015-02-12 2016-10-25 Ca, Inc. Automated software deployment
US10296445B2 (en) 2015-09-13 2019-05-21 Ca, Inc. Automated system documentation generation
US10628420B2 (en) 2015-12-18 2020-04-21 Ca, Inc. Dynamic virtual service
US9886365B2 (en) 2016-01-07 2018-02-06 Ca, Inc. Transactional boundaries for software system debugging
US10154098B2 (en) 2016-01-07 2018-12-11 Ca, Inc. Transactional boundaries for software system profiling
US9983856B2 (en) 2016-01-08 2018-05-29 Ca, Inc. Transaction flow visualization
US10114736B2 (en) 2016-03-30 2018-10-30 Ca, Inc. Virtual service data set generation
US9898390B2 (en) 2016-03-30 2018-02-20 Ca, Inc. Virtual service localization
US10341214B2 (en) 2016-03-30 2019-07-02 Ca, Inc. Scenario coverage in test generation
US9946639B2 (en) 2016-03-30 2018-04-17 Ca, Inc. Transactional boundaries for virtualization within a software system
US10394583B2 (en) 2016-03-31 2019-08-27 Ca, Inc. Automated model generation for a software system

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6909899B2 (en) 2002-03-11 2005-06-21 Qualcomm, Incoporated Method and apparatus for handoff in a communication system supporting multiple service instances
US6801528B2 (en) 2002-07-03 2004-10-05 Ericsson Inc. System and method for dynamic simultaneous connection to multiple service providers
US7574524B2 (en) 2003-09-30 2009-08-11 International Business Machines Corporation Method and system for on-demand allocation of a dynamic network of services
US20050080811A1 (en) 2003-10-10 2005-04-14 Cendura Corporation Configuration management architecture
US20060179116A1 (en) 2003-10-10 2006-08-10 Speeter Thomas H Configuration management system and method of discovering configuration data
JP2006238330A (ja) 2005-02-28 2006-09-07 Sony Corp 通信システムおよび通信サービス移行方法
US8522341B2 (en) 2006-03-31 2013-08-27 Sap Ag Active intervention in service-to-device mapping for smart items
WO2007118217A2 (fr) 2006-04-06 2007-10-18 Continental Casualty Company Appareil et procédé d'examen de demandes d'indemnisation
US8396788B2 (en) 2006-07-31 2013-03-12 Sap Ag Cost-based deployment of components in smart item environments
US8356431B2 (en) 2007-04-13 2013-01-22 Hart Communication Foundation Scheduling communication frames in a wireless network
US8942219B2 (en) 2007-04-13 2015-01-27 Hart Communication Foundation Support for network management and device communications in a wireless network
US8325627B2 (en) 2007-04-13 2012-12-04 Hart Communication Foundation Adaptive scheduling in a wireless network
US8230108B2 (en) 2007-04-13 2012-07-24 Hart Communication Foundation Routing packets on a network using directed graphs
KR100874652B1 (ko) * 2007-06-26 2008-12-17 한국전자통신연구원 이기종 센서네트워크를 위한 통합 인터페이스 장치 및 그방법
US9730078B2 (en) 2007-08-31 2017-08-08 Fisher-Rosemount Systems, Inc. Configuring and optimizing a wireless mesh network
CN101136877A (zh) 2007-09-28 2008-03-05 腾讯科技（深圳）有限公司 即时通讯的方法及系统
FI123499B (fi) * 2008-05-05 2013-06-14 Sensinode Oy Menetelmä ja laite viestien prosessoimiseksi
WO2010039804A1 (fr) 2008-09-30 2010-04-08 Saudi Arabian Oil Company Système et procédé permettant une meilleure coordination entre des systèmes de commande et de sécurité
CN101882073A (zh) * 2009-05-04 2010-11-10 谭家辉 面向服务的应用系统及其通信方法、创建器和创建方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN102422616B (zh) 2015-06-24
CN102422616A (zh) 2012-04-18
US20120059868A1 (en) 2012-03-08
WO2010130585A1 (fr) 2010-11-18
US9277031B2 (en) 2016-03-01

Similar Documents

Publication Publication Date Title
EP2430810A1 (fr) Procédé permettant d'assurer la communication entre un certain nombre de premiers services et un certain nombre de deuxièmes services
DE102006058818B4 (de) Vorrichtung und Verfahren zur Umwandlung von Textmitteilungen
DE60222640T2 (de) Verfahren und system zur adressierung von geräten in einem rechnernetzwerk
EP3643019B1 (fr) Module de communication et système de bus d'éclairage pourvu d'une interface réseau
DE19528563A1 (de) Kommunikationsanordnung und Verfahren zur Bewertung von mindestens zwei mehrteiligen Kommunikationsverbindungen zwischen zwei Kommunikationspartnern in einem Mehrknotennetzwerk
DE69635511T2 (de) Verfahren und gerät zum weglenken von nachrichten in einem knoten-netz
DE102015215480A1 (de) Verfahren und Vorrichtung zum Übertragen einer Nachricht in einem Fahrzeug
EP3577871A1 (fr) Procédé et dispositif permettant l'orientation modulaire d'un flux avb
EP3676991B1 (fr) Réseau d'automatisation de voie et procédé de communication de messages dans un réseau d'automatisation de voie
WO2009037074A1 (fr) Procédé d'exploitation d'un réseau de communication décentralisé
EP1362304A2 (fr) Systeme et procede pour generer et memoriser des pages web tout en optimisant l'encombrement en memoire
EP1860830B1 (fr) Procédé d'installation d'un réseau hiérarchique
EP2503760B1 (fr) Procédé de réglage d'un réseau de communication à partir d'appareils d'une installation d'automatisation
DE602004002988T2 (de) System und Verfahren zur Datenweiterleitung
EP2868164B1 (fr) Système de commande destiné à des consommateurs répartis, et procédé permettant de mettre ledit système en service
EP1346521B1 (fr) Procede pour commander des liaisons dans un systeme de communication et systeme de communication mis en oeuvre a cette fin
EP2733555B1 (fr) Système BUS comprenant des participants qui sont des producteurs et/ou des consommateurs de valeurs de processus, dispositif comprenant un système BUS, système fluidique comprenant un système BUS et procédé de fonctionnement d'un système BUS
DE102004004345A1 (de) System und Verfahren zur Kommunikation zwischen entfernten Objekten und lokalen Stellvertretern
DE60036503T2 (de) Verfahren zur Kommunikation zwischen Fernobjekten
WO2004077760A1 (fr) Implementation efficace de noeuds simples dans un reseau commute
EP2536106A1 (fr) Procédé de transmission d'adresses
EP1511272B1 (fr) Procedé d' attribution de serveur pour le clients repartis dans plusieurs resaux et client pour cette precedé
DE102012015527A1 (de) Verfahren zum Nutzen eines zweiten Infotainmentsystems mittels eines ersten Infotainmentsystems und Fahrzeug
DE102004042004A1 (de) Energiemanagement auf der Basis eines logischen Rings
DE102008033552B4 (de) Verfahren zur Ausführung von Diensten in einem auf einer dienstorientierten Architektur beruhenden Kommunikationsnetz

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

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 SM TR

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIEMENS AKTIENGESELLSCHAFT

17Q First examination report despatched

Effective date: 20160630

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

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