Connecting module for connecting at least one sensor, actuator, or effector to a service-oriented-architecture network

• US 8,751,707 B2
• Filed: 12/18/2010
• Issued: 06/10/2014
• Est. Priority Date: 01/19/2010
• Status: Active Grant

• Current Assignee: Thales Defence Deutschland Gmbh (Thales SA)
• Original Assignee: Thales Defence Deutschland Gmbh (Thales SA)
• Inventors: Moench, Egon, Klotz, Rainer, Michel, Jeremy, Prasse, Christoph, Schmidt, Wolfgang
• Primary Examiner(s): Mamo, Elias
• Application Number:
  US13/522,849
• Publication Number:
  US 20120290749A1
• Time in Patent Office: 1,270 Days
• Field of Search: None
• US Class Current: 710/63
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

The invention relates to a connecting module (3) for connecting at least one sensor (2), effector, or actuator to a service-oriented-architecture, called SOA, network (4), wherein a functionality of the at least one sensor (2) is mapped as a service in the SOA network (4). In order to enable the integration of sensors (2) that are not SOA-capable in themselves into an SOA environment, the connecting module (3) has at least one first interface (3.2) for connecting the at least one sensor (2), effector, or actuator, at least one second interface (3.4) for connecting the SOA network (4), and a computing device (7) for executing a computer program, wherein a part (8.1) of the computer program to be executed is specified by default and another part (8.2) of the computer program is freely programmable by a manufacturer of the at least one sensor (2) in order to adapt firmware on the at least one sensor (2) to the SOA environment. The invention further relates to a module unit (22) of the connecting module (3) that prepares the service mapped in the SOA environment for transmission over a military radio network (35) having low bandwidth while maintaining the SOA functionality.

Claims

1. A connecting module for connecting at least one appliance to a network, comprising:

at least one first interface for connecting the at least one appliance;

at least one second interface for connecting the network, and

a computation appliance for executing a computer program, wherein one portion of the computer program is prescribed and only a second portion of the computer program is freely programmable by a manufacturer of the at least one appliance;

characterized in that the network is a service-oriented architecture, termed SOA network, wherein a functionality of the at least one appliance is mapped as a service in the SOA network, and programming by the manufacturer is for customization of a piece of firmware which is present on the at least one appliance without any knowledge about SOA, a statefulness of the appliance, a statelessness of the service in the SOA environment of the SOA network and allowance for the service, in order to maintain security of the appliance.

2. The connecting module as claimed in claim 1, characterized in that the appliance to be connected to the SOA network comprises a sensor, effector or actuator.

3. The connecting module as claimed in claim 1, characterized in that the first interface comprises an RS232 interface, a USB interface, a LAN connection, an Ethernet connection or an optical connection.

4. The connecting module as claimed in claim 1, characterized in that the second interface comprises a bus connection, particularly a CAN, TTCAN, LIN, MOST, ByteFlight, D2B Optical or FlexRay bus connection.

5. The connecting module as claimed in claim 1, characterized in that the second interface is in the form of a radio interface.

6. The connecting module as claimed in claim 4, characterized in that the radio interface is designed for data transmission between the connecting module and the SOA network with a short delay time, particularly in realtime.

7. The connecting module as claimed in claim 1, characterized in that the computation appliance designed to execute the computer program is a microprocessor.

8. The connecting module as claimed in claim 1, characterized in that the computation appliance designed to execute the computer program is a digital signal processor, termed DSP.

9. The connecting module as claimed in claim 1, characterized in that the computation appliance controls the first and/or the second interface.

10. The connecting module as claimed in claim 1, characterized in that the computation appliance does not actuate the first and/or the second interface and in that the connecting module has a further computation appliance, particularly a digital signal processor, termed DSP, which controls the first and/or the second interface.

11. The connecting module as claimed in claim 1, characterized in that the connecting module has a watchdog timer.

12. The connecting module as claimed in claim 1, characterized in that the customization of the firmware which is present on the at least one appliance to the SOA network involves automatic production and implementation of a heartbeat operation.

13. The connecting module as claimed in claim 1, characterized in that the connecting module stores and effects coordinated execution of SOA calls from the SOA network.

14. The connecting module as claimed in claim 1, characterized in that the firmware which is present on the at least one appliance is customized to the SOA network by the appliance manufacturer using knowledge by the appliance manufacturer about interfaces of the appliance to be encapsulated and about a programming language for an encapsulation framework for the firmware, which encapsulation framework is generated as part of the customization.

15. The connecting module as claimed in claim 1, characterized in that SOA encapsulation of a functionality of the appliance is implemented such that the SOA encapsulation processes priorities for SOA calls from the SOA network such that the functionalities of the appliance which correspond to the SOA calls can be executed in an order which corresponds to the priorities.

16. The connecting module as claimed in claim 1, characterized in that the connecting module has a sandbox which is separate from the other components of the connecting module and which stores the customizations of the appliances to the SOA network.

17. The connecting module as claimed in claim 1, characterized in that the customizations of the appliances to the SOA network are implemented by service descriptions which are stored in a service registry of the connecting module.

18. The connecting module as claimed in claim 17, characterized in that the service registry delivers a suitable WSDL (Web-Service Definition Language) file for various SOA networks.