Control device

• US 20030233407A1
• Filed: 03/26/2003
• Published: 12/18/2003
• Est. Priority Date: 03/26/2002
• Status: Abandoned Application

• Current Assignee: Albrecht Mayer, Harry Siebert, Martin Terry, Vladimir Khavrov
• Original Assignee: Albrecht Mayer, Harry Siebert, Martin Terry, Vladimir Khavrov
• Inventors: Khavrov, Vladimir, Terry, Martin, Siebert, Harry, Mayer, Albrecht
• Application Number:
  US10/397,143
• Publication Number:
  US 20030233407A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G05B 2219/33148 CLS client server architecture, client consumes, server provides services
• CPC Class Codes: G05B 2219/33297 Diagnostic, test, debug
• CPC Class Codes: G06F 11/3648 using additional hardware

Abstract

A control device is provided for observing and/or changing internal states and processes of a controllable unit from outside the unit. The control device is a component of a network including a server and two or more clients. The clients are system components for initiating or carrying out the observation, change and/or evaluation of the internal states and processes of the programmable unit. Whenever the clients access the programmable unit in order to carry out the necessary tasks they are responsible for, they transmit to the server a request that specifies what action is to be initiated by the access. The server defines how the programmable unit must be accessed in order to carry out the actions specified by the requests, and carries out the corresponding access to the programmable unit.

Claims

1. In combination with a programmable unit having internal states and processes, a network comprising:

a server; and

at least two clients for carrying out or initiating at least one function selected from a group consisting of an observation, a change, and an evaluation of the internal states and the processes of the programmable unit;

each of said clients responsible for carrying out necessary tasks by accessing said server;

each of said clients configured for performing the accessing of said server by transmitting a request to said server, said request specifying what action will be initiated by the accessing of said server; and

said server defining how the programmable unit must be accessed to carry out the action specified by said request and said server carrying out a corresponding access to the programmable unit.

2. The network according to claim 1, wherein said request is transmitted as a request list including a multiplicity of requests.

3. The network according to claim 2, wherein said server is configured to prohibit processing of any other requests while processing said multiplicity of requests contained in said request list.

4. The network according to claim 1, wherein a respective one of said clients transmits further requests or request lists to said server before said server has processed requests or request lists that have already been supplied to said server by said respective one of said clients.

5. The network according to claim 1, wherein said server is configured such that when said clients transmit a plurality of requests to said server, said server defines a sequence for processing said plurality of requests, taking account of priorities allocated to ones of said clients from which said plurality of requests originated.

6. The network according to claim 1, wherein said server is configured such that when said clients transmit a plurality of requests or request lists to said server, said server defines a sequence for processing said plurality of requests or request lists, taking account of priorities allocated to said clients from which said plurality of requests or request lists originated.

7. The network according to claim 1, wherein said server is configured such that when said clients transmit a plurality of requests or request lists to said server, said server defines a sequence for processing said plurality of requests or request lists, taking account of priorities that said clients issuing said plurality of requests or request lists have assigned to said plurality of requests or request lists.

8. The network according to claim 1, wherein said server is configured such that when one of said clients transmits a request or request list to said server, said server, before processing said requests or said request lists, checks whether said one of said clients is authorized to initiate actions specified by said request or said request list.

9. The network according to claim 1, wherein said server includes at least a partial model of the programmable unit for checking whether said server is functioning correctly.

10. The network according to claim 9, wherein said model also serves for checking whether at least one of said clients is functioning correctly.

11. The network according to claim 1, wherein said server includes at least a partial model of the programmable unit for checking whether at least one of said clients is functioning correctly.

12. The network according to claim 1, wherein said server includes at least a partial model of the programmable unit for checking whether said server and said clients are cooperating correctly.