阅读说明：本技术 用于转发节点数据的方法和聚合服务器 (Method and aggregation server for forwarding node data ) 是由 F·克罗索 R·布劳恩 于 2020-04-09 设计创作，主要内容包括：本发明涉及一种聚合服务器(100),其包括：在被聚合的地址空间(120)中的第一代理节点和第二代理节点(112、114)、控制逻辑(104),其中第一代理节点(112)对应被聚合的服务器(122)的远程地址空间(124)中的第一节点(116),并且第二代理节点(114)对应被聚合的服务器(122)的远程地址空间(124)中的第二节点(118)；其中,控制逻辑被配置成根据输入/输出关系,从远程空间(124)中的第一节点(116)经由第一代理节点(112)和第二代理节点(114)向远程空间(124)中的第二节点(118)转发节点数据。(The invention relates to an aggregation server (100) comprising: first and second proxy nodes (112, 114) in the aggregated address space (120), control logic (104), wherein the first proxy node (112) corresponds to the first node (116) in the remote address space (124) of the aggregated server (122), and the second proxy node (114) corresponds to the second node (118) in the remote address space (124) of the aggregated server (122); wherein the control logic is configured to forward node data from a first node (116) in the remote space (124) to a second node (118) in the remote space (124) via the first proxy node (112) and the second proxy node (114) according to the input/output relationship.)

1. An aggregation server (100) comprising: first and second proxy nodes (112, 114), control logic (104) in an aggregated address space (120),

wherein the first proxy node (112) corresponds to a first node (116) in a remote address space (124) of an aggregated server (122) and a second proxy node (114) corresponds to a second node (118) in the remote address space (124) of the aggregated server (122);

wherein the control logic is configured to forward node data from the first node (116) in the remote space (124) to the second node (118) in the remote space (124) via the first proxy node (112) and the second proxy node (114) according to an input/output relationship.

2. The aggregation server (100) of claim 1, wherein the control logic (102) comprises a control logic node (104), and the control logic node (104) is configured to receive the node data from the first proxy node (112) via a first interface node (106) and to forward the node data to the second proxy node (114) according to an input/output relationship.

3. The aggregation server (100) of claim 1 or 2,

wherein the control logic (102) further comprises a synchronization module;

wherein the synchronization module is configured to synchronize the node data of the first proxy node (112) with the node data of the first node (116) in the remote address space (124) prior to performing the forwarding, and configured to provide the node data to the second proxy node (114) and the second node (118) when performing the forwarding.

4. The aggregation server (100) of any one of the preceding claims,

wherein the first proxy node (112) and the second proxy node (114) comprise meta-information;

wherein the meta information describes whether the data has read or write permission;

wherein the input/output relationship between an interface node and a proxy node is defined by read or write permission of proxy node data, and the first proxy node (112) has read permission and the second proxy node (114) has write permission;

wherein the reference in the aggregated address space (120) further defines a relationship between the first proxy node (112) and the second proxy node (114); and

wherein the first proxy node (112) is defined as a forwarding source of the node data to be forwarded according to the input/output relationship between the first interface node (106) and the first proxy node (112) and the reference; and wherein the second proxy node (114) is defined as a forwarding target for the node data to be forwarded according to the reference and an input/output relationship between the second interface node (108) and the second proxy node (114).

5. The aggregation server (100) according to any one of the preceding claims, wherein the aggregation server (100) further comprises an input-output profile;

wherein the input-output configuration file (110) comprises the reference and/or data type definitions of the first agent node (112) and the second agent node (114); and

wherein the control logic is further configured to read the input-output profile (110) data and to forward the node data from the first node (116) to the second node (118) according to the profile data.

6. The aggregation server (100) according to any of the preceding claims, wherein the aggregation server (100) is an OPC UA aggregation server (100).

7. A controller (102) for use in an aggregation server (100), comprising: a control logic node (104), a first interface node (106), and a second interface node (108),

wherein the first interface node (106) is assigned to a first proxy node (112) and the second interface node (108) is assigned to a second proxy node (114); and

wherein the control logic node (102) is configured to forward node data from the first proxy node (112) to the second proxy node (114) according to an input/output relationship between the first interface node (106) and the first proxy node (112) and an input/output relationship between the second interface node (108) and the second proxy node (114).

8. A method (200) for forwarding node data of a first node (116) in a remote address space (124) to a second node (118) in the remote address space (124), the method comprising the following steps

S1: aggregating (210), by an aggregation server (100), node data of the second node (118) and the first node (116);

s2: creating (220), by the aggregation server (100), a first proxy node (112) and a second proxy node (114), the first proxy node (112) comprising node data of the first node (116), the second proxy node (114) comprising node data of the second node (118);

s3: receiving (230), by the aggregation server (100), node data from the first proxy node (112) at a first interface node (106) according to an input/output relationship between the first proxy node (112) and the first interface node (106) comprised in the first proxy node (112);

s4: providing (240), by the aggregation server (100), the node data of the first interface node (106) to a second interface node (108);

s5: forwarding (250), by the aggregation server (100), the node data of the first interface node (106) to the second proxy node (114) and the second node (118) according to the input/output relationship between the second interface node (108) and the second proxy node (114) and a reference defining a relationship between the first proxy node (112) and the second proxy node (114).

9. The method (200) according to claim 8, wherein step S2, creating (220), by the aggregation server (100), a first proxy node (112) and a second proxy node (114), the first proxy node (112) comprising node data of the first node (116) and the second proxy node (114) comprising node data of the second node (118), comprises the steps of:

s2 a: determining (222) a relationship between the first proxy node (112) and the second proxy node (114) by reading the reference information;

s2 b: determining (224) the input/output relationship by reading and evaluating meta-information of the first proxy node (112); the meta information describes read permissions;

s2 c: determining (226) the input/output relationship by reading and evaluating meta-information of the second proxy node (114); the meta information describes write permissions.

10. The method (200) according to claim 8 or 9, wherein step S3, receiving (230), by the aggregation server (100) from the first proxy node (112) at the first interface node (106), node data according to an input/output relationship between the first proxy node (112) and the first interface node (106) comprised in the first proxy node (112), comprises:

s3 a: detecting (232) a data change at the first node (116), and upon detecting the data change, performing the steps of:

s3 b: synchronizing (234) the first node (116) with the first proxy node (112) and triggering reception (230), by an aggregation server (100), of node data from the first proxy node (112) at a first interface node (106) according to an input/output relationship between the first proxy node (112) and the first interface node (106) comprised in the first proxy node (112).

11. A computer program element, which, when executed by control logic (102), instructs an aggregation server (100) to perform the steps S2-S5 of claim 8.

12. A computer-readable medium on which a program element according to claim 11 is stored.