System for virtual process interfacing via a remote desktop protocol (rdp)

• US 20060142878A1
• Filed: 09/01/2003
• Published: 06/29/2006
• Est. Priority Date: 09/16/2002
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Banik, Thomas, List, Stefan, Volkmann, Frank, Talanis, Thomas, Gerlach, Hendrik, Troster, Thomas
• Application Number:
  US10/527,913
• Publication Number:
  US 20060142878A1
• Time in Patent Office: Days
• US Class Current: 700/17
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality

Abstract

The invention relates to a system and a method for virtual on line process interfacing for distributed engineering systems in automation technology based on a remote desktop protocol. A communication channel is established from any client within the system to a server via the RDP by means of online access. Process data and project planning data are tunneled via the channel. Quasi peer-to-peer communication between random clients in the system is made possible by means of routing on the server.

Claims

1-20. -20. (canceled)

21. A system for process interfacing within an automation scenario for distributed engineering systems, the system comprising:

a server for providing at least one application required for engineering;

at least one client for accessing automation devices that supply process data and/or project-planning data and for setting up an online communication channel maintained for any length of time between the client and server;

first mechanisms for feeding data of the automation devices into the server via the communication channel; and

second mechanisms for linking the applications to the automation devices, wherein

the first mechanisms have a first interface to a current communication channel and a second interface to the applications, and wherein

the first mechanisms are provided for communicating with the second mechanisms via the communication channel.

22. The system according to claim 21, wherein the client is designed as a programming device and/or as an operator panel and/or as a diagnostic device and/or as a browser and/or as a Windows CE device.

23. The system according to claim 21, wherein the server is designed as a terminal server for use simultaneously by one or more participants.

24. The system according to claim 21, wherein the communication channel is designed as a Remote Desktop Protocol for transmitting data to one or more participants in realtime via one or more separate virtual channels.

25. The system according to claim 21, wherein the first mechanisms are provided for feeding data of further automation devices into the server via the communication channel via at least one further client.

26. The system according to claim 21, wherein the transmission of data in the communication channel is provided via an Intranet and/or an Internet.

27. The system according to claim 21, wherein the transmission of data from the client is provided using a Remote Desktop Protocol via a Wireless LAN.

28. The system according to claim 21, wherein the transmission of data using a Remote Desktop Protocol is provided from further data sources present in the system using standard protocols such as HTTP and/or FTP.

29. The system according to claim 21, wherein the system is provided for use across different sites.

30. A method for process interfacing within an automation scenario for distributed engineering systems, the method comprising:

providing an application required for engineering by a server;

accessing automation devices that supply process data and/or project-planning data via at least one client;

setting up an online communication channel between the client and the server;

feeding the data of the automation devices into the server via the communication channel; and

linking the applications to the automation devices, wherein communication takes place with a second mechanism via the communication channel via a first mechanism having a first interface to a current communication channel and a second interface to the applications.

31. The method according to claim 30, wherein a programming device and/or an operator panel and/or a diagnostic device and/or a browser and/or a Windows CE device is used as the client.

32. The method according to claim 30, wherein one or more participants can use the server simultaneously.

33. The method according to claim 30, wherein a Remote Desktop Protocol for transmitting data to one or more participants in real-time via one or more separate virtual channels is used as the communication channel.

34. The method according to claim 30, wherein data of further automation devices is fed by the first mechanism into the server via the communication channel via at least one further client.

35. The method according to claim 30, wherein data is transmitted in the communication channel over an intranet and/or the Internet.

36. The method according to claim 30, wherein data is transmitted from the client using the Remote Desktop Protocol via a Wireless LAN.

37. The method according to claim 30, wherein data using a Remote Desktop Protocol from further data sources present in the system is transmitted employing standard protocols such as HTTP and/or FTP.

38. The method according to claim 30, wherein the system is used across different sites.

39. A server for providing at least one application required for engineering, the server comprising:

mechanisms for feeding in data of automation devices via a communication channel, wherein said mechanisms having a first interface to a current communication channel and a second interface to the applications.

40. A client for accessing automation devices that supply process data and/or project-planning data and for setting up an online communication channel maintained for any length of time between the client and a server, the client having mechanisms for linking applications provided by the server to the automation devices.