CN111913387A - System for redundancy and load balancing of multiple acquisition devices based on soft bus - Google Patents

Abstract

The invention relates to a system for redundancy and load balancing of multiple acquisition devices based on a soft bus, including a platform server, a node management server, a message soft bus and various regional comprehensive monitoring subsystems, wherein each regional comprehensive monitoring subsystem includes a main The communication front-end computer and the standby communication front-end computer, the platform server, the node management server, the main communication front-end computer and the standby communication front-end computer are all connected through the message soft bus communication; the node management server dynamically manages the main communication front-end computers of all areas. In the standby state, the main communication front-end computer allocates all subsystem channels in this area to different communication front-end computers according to the rules, which realizes the multi-machine redundancy of the communication front-end computer; during operation, the main communication front-end computer is based on the load Equalization algorithms adjust subsystem channel assignments in real time. Compared with the prior art, the present invention solves the complex communication problem among heterogeneous components of distributed platforms, and at the same time alleviates the problem of excessive data access load of a single acquisition device.

Description

A System of Redundancy and Load Balancing of Multiple Acquisition Devices Based on Soft Bus

technical field

The invention relates to the field of comprehensive monitoring of rail transit, in particular to a system for redundancy and load balancing of multiple acquisition devices based on a soft bus.

Background technique

The modern smart rail transit platform is connected to multiple subsystems, such as Automatic Train Monitoring System (ATS), Broadcasting System (PA), Passenger Information System (PIS), Video Monitoring System (CCTV), Fire System (FAS), Environmental Control System (BAS), by analyzing the data of many subsystems and combining with intelligent operation and maintenance algorithms, it provides auxiliary decision-making for dispatchers, which not only improves the efficiency of operation and maintenance, but also improves the efficiency of operation and maintenance through the linkage between subsystems in emergency situations. Human-driven driving safety provides a stronger guarantee. However, these subsystems are scattered all over the line, the amount of data accessed is huge, the access methods and communication protocols are also different, and they cannot be directly connected to the rail transit platform. A communication front-end machine is set between the subsystem and the rail transit platform to parse the subsystem data into platform-identifiable data.

When the line scale is small, the communication front-end machine can be set in the center to access all subsystem data, and to ensure the stable operation of the communication front-end machine, two redundant communication front-end machines are usually set up. However, the general method is to set A cold standby communication front-end computer, only when the main communication front-end computer fails will the backup communication front-end computer take over all data access work. Although this method solves the problem of system stability, due to the cold standby communication The built-in machine does not participate in the data access work, so it causes a waste of resources to a certain extent, and due to the whole machine switching of the communication front-end machine, and the data of the main and standby communication front-end machines are not synchronized, which will cause data fluctuations during switching. , affecting the user's use.

In order to solve the problem of data fluctuation, some methods are to use two hot standby communication front-end computers for data access at the same time, and the server selectively receives the data uploaded by one of the communication front-end computers, but this method is also unavoidable. It wastes resources, and also increases the comparison work of the server. At the same time, due to the particularity of some subsystem interfaces, it cannot support two-way connections, so this method also has certain limitations.

With the increase of the line scale, the centralized access method of the center can no longer meet the processing requirements of big data. Therefore, it is necessary to introduce distributed technology. By setting up multiple sets of redundant servers in the center and centralized station, and sinking the communication front-end to the At the station, after accessing and processing subsystem data at the station, part of the data is uploaded to the station server and the central server as required, thereby reducing the processing pressure on the communication front-end and server. However, the introduction of the distributed architecture has greatly increased the number of communication front-end computers and servers. If the traditional API coding communication method is used at this time, the network structure of the entire platform will be extremely complicated, which is very unfavorable for platform development and maintenance. It has caused some difficulties for the later expansion of the platform.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a system for redundancy and load balancing of multiple acquisition devices based on a soft bus in order to overcome the above-mentioned defects in the prior art, which is suitable for the acquisition of external subsystem data of a comprehensive monitoring platform for rail transit, and solves the problem of It solves the complex communication problems between heterogeneous components of distributed platforms, and at the same time alleviates the problem of excessive data access load of a single acquisition device.

The object of the present invention can be realized through the following technical solutions:

A system for redundancy and load balancing of multiple acquisition devices based on a soft bus, including a platform server, a node management server, a message soft bus, and a comprehensive monitoring subsystem in each area, wherein each regional comprehensive monitoring subsystem includes a main communication front-end computer and standby communication front-end computer, the platform server, node management server, main communication front-end computer and standby communication front-end computer are all connected through message soft bus communication;

The node management server dynamically manages the active and standby states of all regional communication front-end computers, and the main communication front-end computer allocates all sub-system channels in the region to different communication front-end computers for access according to rules, thereby realizing the pre-communication process. Built-in multi-machine redundancy; during operation, the main communication front-end machine adjusts the subsystem channel allocation in real time according to the load balancing algorithm.

Preferably, the message soft bus is a non-centralized message soft bus based on a publish or subscribe system.

Preferably, the system configures all devices connected to the platform to communicate using the message soft bus, and sets the message soft bus to be strictly reliable transmission.

Preferably, the communication front-end computer provides data collection and command forwarding services through a message soft bus, the node management server provides a full-line communication front-end computer active and standby state management service through the message soft bus, and the platform server is provided through the message soft bus. The message soft bus subscribes to the data of the communication front-end, and sends control commands to the main communication front-end in different areas in combination with the active and standby status information of the communication front-end provided by the node management service.

Preferably, the specific process of dynamically managing the active and standby states of all regional communication front-end machines by the node management server is as follows:

1) When the communication front-end computer is started, it first registers the local information with the node management server;

2) The node management server monitors the online status of the communication front-end in each area in real time. When the communication front-end in a certain area triggers the soft bus disconnection event, it will re-elect the main communication front-end for this area according to the rules, and the election result will be immediately Released via soft bus;

3) When the node management server fails to start or run, it will cause the communication front-end machine to fail to register. If the communication front-end machine does not receive the response data containing the status of the node within the specified time t after the registration message is issued, it will be re-registered. Initiate registration until registration is successful.

Preferably, the specific process of the communication front-end registering local information to the node management server is as follows:

a) The communication front-end computer publishes the local area number, device number, and device status to the node management server;

b) The node management server groups the communication front-end machines according to the area number, and sets the main and backup status of the communication front-end machines according to the communication front-end machine information in the group;

c) If there is no communication front-end registration in the current group, or there is no online communication front-end, set the communication front-end as the main communication front-end;

d) If there is a communication front-end registered in the current group, and there is a main communication front-end, then set the communication front-end as a backup communication front-end;

e) If there is a communication front-end registered in the current group, but there is no main communication front-end, select the main communication front-end according to the rules:

f) After the registration is successful, the node management server immediately returns the status information of all the communication front-end machines in the area to the communication front-end machine, and adds the communication front-end machine status to the state information of the full-line communication front-end machine that is periodically released later.

Preferably, the election rule in described e) is

First, compare the equipment status, and the communication front-end with the best equipment status is preferentially selected as the main communication front-end;

Assuming that the network status is NS, the single-network online value is 0, the dual-network online value is 1, the CPU usage rate is Ucpu, and the memory usage rate is Umem, the device status priority calculation formula is as follows:

0.5×NS+0.3×(1-Ucpu)+0.2×(1-Umem)

If all communication front-end devices have the same status priority, the device numbers of the communication front-end devices are compared again, and the communication front-end device with a larger device number is preferentially selected as the main communication front-end device.

Preferably, the described message soft bus configuration communication front-end FEP data publishing and subscription rules are specifically:

Divide FEP data into four categories, namely system data S, business data D, control command C and command return R, where S is FEP status information, including equipment operation status, software operation status, system alarm and channel status, D is the subsystem data parsed by FEP, C is the FEP control command or subsystem control command, and R is the FEP control command back to school or the subsystem control command back to school. Publish, C is subscribed by FEP;

Each type of data is published and subscribed using different softbus topics, and topic parameters, including domain, partition, topic name, and content filter conditions, are modified through the configuration library.

Preferably, the soft bus topics corresponding to the four types of data are combined into a soft bus route, and the FEP and different platform servers use the same or different topics to publish and subscribe data according to the soft bus routing configuration, while the FEP uses the soft bus route. The routing table provides differentiated data collection services for different modules of the platform.

Preferably, the configuration of the soft bus routing table is as follows:

{ROUTE_1(T _S ,T _D ,T _C ,T _R ),…,ROUTE_N(T _S ,T _D ,T _C ,T _R )}

T _S represents the system data topic, _TD represents the business data topic, _TC represents the control command topic, and _TR represents the command back to school topic.

Preferably, the system data S is periodically released data, wherein the device operation status, software operation status and channel status are all configured through the configuration library release cycle, and the system alarm is released at the fastest speed in a change-triggered manner , the same system data topic can be configured for different soft bus routes.

Preferably, the business data D is divided into three types, which are digital data, analog data and cumulative data, each type of data corresponds to a data forwarding table, and the configuration data and the soft bus routing are in the data forwarding table. Mapping relationship. When the data in the data forwarding table changes, FEP uses the business data topic corresponding to the soft bus route to publish the changed data to the corresponding platform server according to the mapping relationship between the data and the soft bus route.

Preferably, the control command C can only be subscribed by the main FEP, and is forwarded by the main FEP to the FEP where the main channel is located according to the channel distribution;

When each platform server issues a control command to the FEP, it first obtains the main FEP information of the corresponding area from the node management server, and appends the main FEP number to the control command. The FEP number in the received control command is the control command of the local number, so the control command will only be subscribed by the main FEP.

Preferably, the command to return to school R is issued in a change-triggered manner, and is directly issued by the FEP that executes the control command or the FEP that receives the sub-system command to return to school.

Preferably, the subsystem accessed by the communication front-end FEP is virtualized as an RTU channel, and the RTU channel will be used as the smallest unit of channel redundancy and load balancing;

According to the characteristics of the subsystem, combined with the load balancing rules, configure the redundancy mode of each RTU, including failover and load balancing. Among them, failover means that the RTU only switches when the link or service is unavailable, while load balancing means The RTU can be dynamically switched according to the load balancing result.

Preferably, the main communication front-end computer adjusts the subsystem channel allocation in real time according to the load balancing algorithm, specifically:

(1) After the FEP is elected as the main FEP, first determine whether the RTU channel is allocated, if not, then according to the RTU configuration and the current online FEP information, the RTU channel is evenly allocated to each FEP;

(2) Each FEP creates corresponding services according to the RTU channel allocated by the machine, including collection services, forwarding services and synchronization services;

(3) The standby FEP publishes the local device status information and RTU channel status information to the main FEP in real time, and the main FEP calculates whether the RTU channel needs to be switched currently according to the load balancing rules;

(4) When load balancing switching occurs on the RTU channel, the master FEP will immediately publish the RTU channel allocation result after load balancing to other standby FEPs, and if no channel switching occurs, the RTU channel information will be published periodically.

Preferably, the allocation rule of the RTU channel in (1) is:

a) If N _rtu <= N _fep , assign the RTUs to the FEPs in sequence according to the RTU and FEP numbers in ascending order;

按RTU和FEP编号由小到大顺序，将RTU分组分配给FEP，b) If N _rtu >N _fep , the number of RTUs allocated by each FEP is

Assign RTU groups to FEPs in ascending order of RTU and FEP numbers.

表示向下取整。where the number of RTUs is N _rtu , the number of FEPs is N _fep , and the number of FEPs is i, where i=0,1,2...,

Indicates rounded down.

Preferably, the collection service in (2) loads the corresponding device driver according to the RTU configuration and the collection protocol establishes communication with the subsystem; the forwarding service publishes business data in real time according to the forwarding table, and the synchronization service synchronizes the RTU channel data to other The FEP where the redundant RTU channel is located.

Preferably, the load balancing rule in (3) is specifically:

A) If a certain RTU channel of the FEP is not in the running state and the duration exceeds T _offline , the current optimal FEP is selected from other FEPs, and the RTU channel is switched to the optimal FEP. The selection of the optimal FEP is determined by the CPU of the FEP. The usage rate U _cpu , the memory usage rate U _mem and the network status NS are determined. The specific calculation formula is:

0.5×NS+0.3×(1-U _cpu )+0.2×(1-U _mem )

The FEP with the largest calculation result is the optimal FEP. If there are multiple FEPs with the same calculation result, the FEP with the largest number is taken as the optimal FEP;

B) Set the CPU usage rate and memory usage rate of the FEP to U. If U is greater than the set value U _max and the duration exceeds T _overload , some RTU channels under the FEP need to be allocated to other FEPs.

Preferably, the distribution rules in described B) are as follows:

B1) All RTU channels configured as load balancing under the FEP are sorted in ascending order according to the channel-related usage rate U _rtu ;

B2) Read _Urtu in turn, and select the FEP with the lowest current related usage rate U _best ;

B3) If U _rtu +U _best <U _max , switch the corresponding RTU channel to the FEP with the lowest usage rate, and set U=UU _rtu and U _best =U _best +U _rtu at the same time;

B4) If U _rtu +U _best >U _max , jump out of the allocation process;

B5) If UU _rtu >U _max , repeat step B2, otherwise jump out of the allocation process.

Compared with the prior art, the present invention has the following advantages:

1) Realize non-differentiated distribution of data, by connecting all FEPs to a non-centralized message soft bus based on the publish/subscribe system;

2) The multi-machine redundancy of the FEP is realized, the node management server is set, and the active and standby states of the FEPs in all areas of the line are dynamically managed; the main FEP allocates all subsystem channels in the area to different FEPs for access according to the rules;

3) The performance of the FEP equipment is fully utilized, and the stability of the data access of the subsystem is also ensured. During the operation, the main FEP adjusts the channel allocation of the subsystem in real time according to the load balancing algorithm.

Description of drawings

1 is a network architecture diagram of multiple redundant collection devices according to the present invention;

Fig. 2 is the main functional module diagram of the collection device according to the present invention;

FIG. 3 is a data flow diagram of a control command according to the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

The present invention is a system suitable for multi-machine redundancy and load balancing of communication front-end machines in the field of rail transit, and in order to adapt to the distributed architecture of a modern smart rail transit platform, a communication method using a soft bus is proposed. The specific solutions are:

1. Configure the platform device to communicate using the message soft bus

Configure all devices connected to the platform to communicate using the message soft bus, and set the message soft bus QoS to strict and reliable transmission. FEP provides data collection and command forwarding services through the message soft bus, the node management server provides the full-line FEP active and standby status management services through the message soft bus, and other modules of the platform subscribe to FEP data through the message soft bus, combined with the FEP active and standby status provided by the node management service. information, and issue control commands to master FEPs in different areas.

2. Configure the node management server to manage the active and standby status of FEP across the board

When FEP starts, it first registers the local information with the node management server, which includes the following steps:

a) FEP publishes the local area number, device number, and device status to the node management server;

b) The node management server groups the FEPs according to the area number, and sets the active and standby status of the FEPs according to the FEP information in the group;

c) If there is no FEP registration in the current group, or there is no online FEP, set the FEP as the main FEP;

d) If there is an FEP registered in the current group and there is a primary FEP, set the FEP as a standby FEP;

e) If there are FEP registrations in the current group, but there is no main FEP, the main FEP will be elected according to the rules. The election rules are:

First, the device states are compared, and the FEP with the best device state is preferentially selected as the master FEP. Assuming that the network status is NS, the single-network online value is 0, the dual-network online value is 1, the CPU usage rate is U _cpu , and the memory usage rate is U _mem , the device status priority calculation formula is as follows:

0.5*NS+0.3*(1-U _cpu )+0.2*(1-U _mem )

If the status priorities of all FEP devices are the same, the device numbers of the FEP devices are compared again, and the FEP with a larger device number is preferentially selected as the master FEP.

f) After the registration is successful, the node management server immediately returns the status information of all FEPs in the area to the FEP, and adds the FEP status to the status information of the entire line of FEPs periodically released later.

The node management server monitors the online status of the FEPs in each area in real time. When the FEP in a certain area triggers a soft bus disconnection event, it will re-elect the main FEP for the area according to the rules in step e, and immediately publish the election results through the soft bus.

When the node management server fails to start or run later, the FEP registration will fail. If the FEP does not receive the response data containing the status of the node within the specified time t after publishing the registration message, it will re-initiate the registration until the registration is successful.

3. Configure FEP data publishing and subscription rules

The FEP data is divided into four categories, namely system data S, business data D, control command C and command return R, where S is FEP status information, including equipment running status, software running status, system alarm and channel status, D is the subsystem data parsed by FEP, C is the FEP control command or subsystem control command, and R is the FEP control command back to school or the subsystem control command back to school. Published, C is subscribed by FEP.

In order to avoid mutual influence between data and ensure the efficiency of data publishing and subscription, each type of data is published and subscribed using different soft bus topics, and topic parameters can be modified through the configuration library, including domain, partition, topic name and content filter conditions.

Combining the four topics into soft bus routing, FEP and different modules of the platform use the same or different topics to publish and subscribe data according to the soft bus routing configuration, while FEP provides differentiation for different modules of the platform through the soft bus routing table For the data acquisition service, the configuration of the soft bus routing table is as follows:

{ROUTE_1(T _S ,T _D ,T _C ,T _R ),…,ROUTE_N(T _S ,T _D ,T _C ,T _R )}

The system data S is generally released periodically, in which the device operation status, software operation status and channel status can be configured with the release cycle through the configuration library, while the system alarm is released at the fastest speed in the way of change triggering. Soft bus routing, the same system data topic can be configured to reduce FEP release pressure.

Business data D can be divided into three categories, namely digital data, analog data and cumulative data. Each type of data corresponds to a data forwarding table. The mapping relationship between data and soft bus routing is configured in the forwarding table. When the data in the server changes, FEP uses the business data topic corresponding to the soft bus route to publish the changed data to the corresponding module of the platform according to the mapping relationship between the data and the soft bus route.

The control command C can only be subscribed by the master FEP, and the master FEP forwards it to the FEP where the master channel is located according to the channel distribution, so as to avoid the security problem of repeatedly issuing control commands when dual masters and dual channels occur. When each module of the platform issues a control command to the FEP, it first obtains the main FEP information of the corresponding area from the node management server, and appends the main FEP number to the control command. The FEP number in the received control command is the control command of the local number, so the control command will only be subscribed by the main FEP.

The command to return to school R is issued in a change-triggered manner, and is directly issued by the FEP that executes the control command or the FEP that receives the command from the subsystem to return to school, and is no longer forwarded through the main FEP.

4. Channel redundancy and load balancing rules

The subsystem accessed by the FEP is virtualized as an RTU channel, and the RTU channel will be used as the smallest unit of channel redundancy and load balancing. According to the characteristics of the subsystem, combined with the load balancing rules, configure the redundancy mode of each RTU, including failover and load balancing. Among them, failover means that the RTU only switches when the link or service is unavailable, while load balancing means The RTU can be dynamically switched according to the load balancing result.

After the FEP is elected as the master FEP, it firstly judges whether the RTU channel is allocated. If it is not allocated, the RTU channel is evenly allocated to each FEP according to the RTU configuration and the current online FEP information. Let the number of RTUs be N _rtu and the number of FEPs to be N _fep , the FEP number is i (i=0, 1, 2...), and the allocation rule is:

a) If N _rtu <= N _fep , assign the RTUs to the FEPs in sequence according to the RTU and FEP numbers in ascending order;

按RTU和FEP编号由小到大顺序，将RTU分组分配给FEP；b) If N _rtu >N _fep , the number of RTUs allocated by each FEP is

Allocate RTU groups to FEPs in ascending order of RTU and FEP numbers;

Each FEP creates corresponding services according to the RTU channel allocated by the machine, including collection service, forwarding service and synchronization service. The collection service loads the corresponding device driver and collection protocol according to the RTU configuration to establish communication with the subsystem; the forwarding service publishes business data in real time according to the forwarding table, and the synchronization service synchronizes the RTU channel data to the FEP where other redundant RTU channels are located in real time.

The standby FEP publishes the local device status information and RTU channel status information to the master FEP in real time. The master FEP calculates whether the RTU channel needs to be switched according to the load balancing rules. The load balancing rules are as follows:

a) If a certain RTU channel of the FEP is not in the running state and the duration exceeds T _offline , select the current optimal FEP among other FEPs, and switch the RTU channel to the optimal FEP. The selection of the optimal FEP is determined by the CPU of the FEP. The usage rate U _cpu , the memory usage rate U _mem and the network status NS are determined. The specific calculation formula is:

0.5*NS+0.3*(1-U _cpu )+0.2*(1-U _mem )

The FEP with the largest calculation result is the optimal FEP. If there are multiple FEPs with the same calculation result, the FEP with the largest number is taken as the optimal FEP.

b) Set the CPU usage rate and memory usage rate of the FEP to U. If U is greater than the set value U _max and the duration exceeds T _overload , some RTU channels under the FEP need to be allocated to other FEPs. The allocation rules are as follows:

1. Sort all RTU channels configured for load balancing under the FEP according to the channel-related usage U _rtu from small to large;

2. Read _Urtu in turn, and select the FEP with the lowest current related usage rate U _best ;

3. If U _rtu +U _best <U _max , switch the corresponding RTU channel to the FEP with the lowest usage rate, and set U=UU _rtu and U _best =U _best +U _rtu at the same time;

4. If U _rtu +U _best >U _max , jump out of the allocation process;

5. If UU _rtu >U _max , repeat step 2, otherwise jump out of the allocation process.

When load balancing switching occurs on the RTU channel, the master FEP will immediately publish the RTU channel allocation result after load balancing to other standby FEPs. If no channel switching occurs, the RTU channel information will be published periodically.

specific embodiment

Fig. 1 is the network structure diagram of a plurality of redundant acquisition equipment described in the present invention, in each area, disposes a plurality of FEP, adopts soft bus communication between FEP and platform module, the communication protocol adopts soft bus IDL+PROTOBUF self-defined format, FEP It communicates with subsystems through Ethernet or serial port, and the communication protocol uses IEC-60870-5-104, Modbus TCP or custom protocol.

In this embodiment, an area number and number are configured for each FEP, and the subsystems that need to be connected to each area are represented by RTU channels. For example, the power supply subsystem PSCADA is represented as RTU 1, and the fire subsystem FAS is represented as RTU 2. The environmental control subsystem BAS is denoted as RTU 3.

Configure the interface mode and communication protocol of each RTU channel, and select the redundancy mode for each RTU channel. For subsystems that do not require frequent switching, such as the PSCADA subsystem, set the redundancy mode to failover mode, while for the data volume For larger subsystems with lower security levels, such as FAS/BAS subsystems, set the redundancy mode to load balancing.

Configure the FEP soft bus routing table, including system data topics, business data topics, control command topics, and command return topics for communication between FEP and each module of the platform, and configure the domain, partition, topic name, and content filter conditions of each topic. For example, in this embodiment, the FEP can be configured with three soft bus routes to provide data services for the station server, the central PSCADA server, and the central environmental control server, respectively.

Configure the FEP data forwarding table, including the digital forwarding table, the analog forwarding table, and the cumulative forwarding table. The forwarding table includes the mapping relationship between RTU data and soft bus routes, such as mapping all PSCADA subsystem data to station server soft bus routes. , Mapping some important data of PSCADA with the soft bus routing of the central PSCADA server. When PSCADA data changes, FEP uses one or more business topics to publish data according to the mapping relationship between the data and the soft bus routing, thereby providing differentiated services for different modules. data service.

Figure 2 shows the main functional modules of the FEP of the present invention, including a node management module, a forwarding module, a synchronization module and an acquisition module. After the FEP is started, all RTU channels are first set to standby state, and the node management module sends to the node management server through the soft bus. Register the machine information, including the following registration steps:

a) Use the node registration topic to publish the local node information, including the area number, device number and device status, and wait for the node management server to respond;

b) If the response data containing the state of the node is not received within the time t, repeat step a;

c) If the response data containing the node status of the local machine is received within the time t, it indicates that the node registration is successful. At this time, according to the received status data, the active and standby status of the local machine is set.

If the FEP is elected as the master FEP, first determine whether all the current RTU channels have been allocated, if not, allocate the RTU channel to each FEP according to the RTU channel configuration and the current online FEP information, and the allocation result will be released to all the standby FEPs through the soft bus , if the RTU channel has been allocated, it will directly enter the load balancing calculation cycle;

If the FEP is selected as the standby FEP, it will directly subscribe to the RTU channel allocation results published by the main FEP through the soft bus, and publish the local state information and RTU channel status information to the main FEP through the soft bus in real time, and the main FEP will load according to all data. Equilibrium calculation, including the following calculation steps:

a) First check the RTU link status allocated by each FEP, if the link is not established and exceeds the specified time, then re-allocate the RTU channel.

b) Next, check the performance usage of each FEP, when it is found that the FEP performance usage is overloaded, combine the performance usage of the RTU channel of the FEP, and reassign some of the RTU channels to other FEPs with the best performance.

After the registration is successful, the node management module subscribes in real time to all the FEP active and standby status information in the local area published by the node management server, and automatically switches to the corresponding state when it finds that the active and standby status of the local machine changes.

When the FEP exits normally, the node management module will initiate the exit process, including the following two situations:

a) If the local machine is the main FEP, first reassign all the RTU channels of the local machine to other FEPs in the area, and then publish the local machine logout information through the node registration topic. After receiving the FEP deregistration information, the node management server sets the FEP to an offline state, and re-selects the primary FEP for the area;

c) If the local machine is the standby FEP, directly use the node registration topic to publish the local machine logout information. After the master FEP receives the FEP deregistration information, it re-allocates the RTU channel on the FEP to other FEPs in the area; after receiving the FEP deregistration information, the node management server sets the FEP to an offline state.

When FEP exits abnormally, the exit process includes the following two situations:

a) If the local machine is the main FEP, after the node management server detects the FEP disconnection event, it sets the FEP to the offline state, and selects the main FEP for the area again. The RTU channel on the offline FEP is reassigned to other FEPs in the area;

b) If the local machine is the standby FEP, after the node management server detects the FEP disconnection event, it sets the FEP to the offline state, and the master FEP reassigns the RTU channel on the offline FEP to Other FEPs in the region;

FEP starts the following services according to the RTU channel assigned to the machine:

1. Start the data collection service of the corresponding channel. The main functions of the collection service include:

a) Create a communication link with the subsystem according to the channel interface configuration, and load the corresponding communication protocol library according to the channel protocol configuration;

c) Receive and parse the subsystem data, and write the data into the FEP real-time library;

d) Parse the platform control command, and package the control command according to the communication protocol structure and forward it to the subsystem.

2. Start the data forwarding service of the corresponding channel. The forwarding service includes the following functions:

a) Real-time release of local equipment operating status, software operating status, channel status, and system alarms through system data topics;

b) Check in real time whether the corresponding channel data in the forwarding table has changed. When the data changes, use the corresponding business data topic to publish the changed data according to the mapping relationship between the data and the soft bus route;

c) Subscribing the control commands of each module of the platform through the control command topic;

As shown in Figure 3, FEP sets the content filtering condition based on the FEP number when subscribing to the control command, that is, it only receives the control command whose FEP number is the local number in the control command. The active and standby status information of each area FEP issued by the management server adds the main FEP number to the control command. Therefore, the control command can only be received by the main FEP of the corresponding area.

After the main FEP forwarding module receives the control command, it first checks whether the RTU channel corresponding to the control command is allocated to the local machine. If so, it is directly forwarded by the local acquisition module to the corresponding subsystem. If not, the RTU is queried according to the RTU channel allocation table. The FEP where the channel is located, and then change the FEP number in the control command to the FEP number where the RTU channel is located, and reissue the control command through the control command topic, so as to realize the one-to-one sending of the control command and avoid the dual-master or dual-channel occurrence of the FEP. Control security issues.

d) Issue the subsystem command to return to school in real time through the command back to school topic.

3. Start the data synchronization service of the corresponding channel. The synchronization service checks whether the data of the corresponding RTU channel in the local real-time library has changed in real time. When the data changes, the changed data is released through the data synchronization topic, while the FEP of other redundant RTU channels is Subscribe data through the data synchronization topic to realize data synchronization between redundant RTU channels.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of various equivalents within the technical scope disclosed by the present invention. Modifications or substitutions should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (20)

1. a system based on a plurality of acquisition equipment redundancy and load balancing of soft bus, it is characterized in that, comprise platform server, node management server, message soft bus and each regional comprehensive monitoring subsystem, wherein each regional comprehensive monitoring sub-system. The system includes a main communication front-end computer and a standby communication front-end computer, and the platform server, the node management server, the main communication front-end computer and the standby communication front-end computer are all connected through a message soft bus communication; The node management server dynamically manages the active and standby states of all regional communication front-end computers, and the main communication front-end computer allocates all sub-system channels in the region to different communication front-end computers for access according to rules, thereby realizing the pre-communication process. Built-in multi-machine redundancy; during operation, the main communication front-end machine adjusts the subsystem channel allocation in real time according to the load balancing algorithm. 2. a kind of system based on soft bus redundancy and load balancing according to claim 1, it is characterized in that, described message soft bus is based on publishing or subscription system and decentralized message soft bus. bus. 3. a kind of system based on the redundancy of a plurality of acquisition devices of soft bus and load balancing according to claim 1, it is characterized in that, the equipment of this system configuration all access platforms uses message soft bus communication, sets message soft bus For strictly reliable transmission. 4. a kind of system based on the redundancy of a plurality of acquisition devices and load balancing of the soft bus according to claim 1 or 3, it is characterized in that, described communication front-end machine provides data acquisition and command forwarding through message soft bus Service, the node management server provides the full-line communication front-end master and standby state management services through the message soft bus, and the platform server subscribes the communication front-end data through the message soft bus, combined with the communication front-end provided by the node management service. Active and standby status information, and issue control commands to the main communication front-end machines in different areas. 5. The system according to claim 1 for redundancy and load balancing of multiple acquisition devices based on a soft bus, wherein the node management server dynamically manages the active and standby states of all regional communication front-end computers. The process is as follows: 1) When the communication front-end computer is started, it first registers the local information with the node management server; 2) The node management server monitors the online status of the communication front-end in each area in real time. When the communication front-end in a certain area triggers the soft bus disconnection event, it will re-elect the main communication front-end for this area according to the rules, and the election result will be immediately Released via soft bus; 3) When the node management server fails to start or run, it will cause the communication front-end machine to fail to register. If the communication front-end machine does not receive the response data containing the status of the node within the specified time t after the registration message is issued, it will be re-registered. Initiate registration until registration is successful. 6. a kind of system based on multiple acquisition equipment redundancy and load balancing according to claim 5, is characterized in that, described communication front-end machine registers local machine information to node management server The concrete process is: a) The communication front-end computer publishes the local area number, device number, and device status to the node management server; b) The node management server groups the communication front-end machines according to the area number, and sets the main and backup status of the communication front-end machines according to the communication front-end machine information in the group; c) If there is no communication front-end registration in the current group, or there is no online communication front-end, set the communication front-end as the main communication front-end; d) If there is a communication front-end registered in the current group, and there is a main communication front-end, set the communication front-end as a backup communication front-end; e) If there is a communication front-end registered in the current group, but there is no main communication front-end, select the main communication front-end according to the rules: f) After the registration is successful, the node management server immediately returns the status information of all the communication front-end machines in the area to the communication front-end machine, and adds the communication front-end machine status to the state information of the full-line communication front-end machine that is periodically released later. 7. a kind of system based on the redundancy of a plurality of acquisition equipment of soft bus and load balancing according to claim 6, is characterized in that, the election rule in described e) is First, compare the equipment status, and the communication front-end with the best equipment status is preferentially selected as the main communication front-end; Assuming that the network status is NS, the single-network online value is 0, the dual-network online value is 1, the CPU usage rate is Ucpu, and the memory usage rate is Umem, the device status priority calculation formula is as follows: 0.5×NS+0.3×(1-Ucpu)+0.2×(1-Umem) If all communication front-end devices have the same status priority, the device numbers of the communication front-end devices are compared again, and the communication front-end device with a larger device number is preferentially selected as the main communication front-end device. 8. a kind of system based on a plurality of acquisition equipment redundancy and load balancing of soft bus according to claim 1, it is characterized in that, described message soft bus configuration communication front-end machine FEP data publishing and subscription rules are specifically: : Divide FEP data into four categories, namely system data S, business data D, control command C and command return R, where S is FEP status information, including equipment operation status, software operation status, system alarm and channel status, D is the subsystem data parsed by FEP, C is the FEP control command or subsystem control command, and R is the FEP control command back to school or the subsystem control command back to school. Publish, C is subscribed by FEP; Each type of data is published and subscribed using different softbus topics, and topic parameters, including domain, partition, topic name, and content filter conditions, are modified through the configuration library. 9. a kind of system based on a plurality of acquisition equipment redundancy and load balancing of soft bus according to claim 8, is characterized in that, the described soft bus subject corresponding to four types of data is combined into soft bus route, FEP and Different platform servers use the same or different topics to publish and subscribe data according to the soft bus routing configuration, while FEP provides differentiated data collection services for different modules of the platform through the soft bus routing table. 10. The system according to claim 9, wherein the software bus routing table configuration is as follows: {ROUTE_1(T _S ,T _D ,T _C ,T _R ),…,ROUTE_N(T _S ,T _D ,T _C ,T _R )} T _S represents the system data topic, _TD represents the business data topic, _TC represents the control command topic, and _TR represents the command back to school topic. 11. A system for redundancy and load balancing of multiple acquisition devices based on a soft bus according to claim 10, wherein the system data S is periodically released data, wherein the device operating status, software Both the running status and the channel status are configured with the release cycle through the configuration library, while the system alarm is released at the fastest speed using the change-triggered method. For different soft bus routes, the same system data topic can be configured. 12. A system for redundancy and load balancing of multiple acquisition devices based on a soft bus according to claim 10, wherein the business data D is divided into three categories, which are digital data and analog data respectively. For data and accumulated data, each type of data corresponds to a data forwarding table, and the mapping relationship between data and soft bus routing is configured in the data forwarding table. The mapping relationship is used to route the corresponding business data topic through the soft bus to publish the changed data to the corresponding platform server. 13. The system according to claim 10, characterized in that, the control command C can only be subscribed by the main FEP, and is subscribed by the main FEP according to the channel. The distribution information is forwarded to the FEP where the main channel is located; When each platform server issues a control command to the FEP, it first obtains the main FEP information of the corresponding area from the node management server, and appends the main FEP number to the control command. The FEP number in the received control command is the control command of the local number, so the control command will only be subscribed by the main FEP. 14. A system for redundancy and load balancing of multiple acquisition devices based on a soft bus according to claim 10, wherein the command return to school R is issued using a change-triggered mode, and is directly controlled by the execution The FEP commanded or the FEP commanded by the receiving subsystem to return to school is issued. 15. The system according to claim 1 for redundancy and load balancing of multiple acquisition devices based on a soft bus, wherein the subsystem that the communication front-end machine FEP accesses is virtualized as an RTU channel representation, and the RTU channel Will serve as the smallest unit of channel redundancy and load balancing; According to the characteristics of the subsystem, combined with the load balancing rules, configure the redundancy mode of each RTU, including failover and load balancing. Among them, failover means that the RTU only switches when the link or service is unavailable, while load balancing means The RTU can be dynamically switched according to the load balancing result. 16. A system for redundancy and load balancing of multiple acquisition devices based on a soft bus according to claim 15, wherein the main communication front-end computer adjusts the subsystem channel allocation in real time according to a load balancing algorithm. for: (1) After the FEP is elected as the main FEP, first determine whether the RTU channel is allocated. If not, the RTU channel is evenly allocated to each FEP according to the RTU configuration and the current online FEP information; (2) Each FEP creates corresponding services according to the RTU channel allocated by the machine, including collection services, forwarding services and synchronization services; (3) The standby FEP publishes the local device status information and RTU channel status information to the main FEP in real time, and the main FEP calculates whether the RTU channel needs to be switched currently according to the load balancing rules; (4) When load balancing switching occurs on the RTU channel, the master FEP will immediately publish the RTU channel allocation result after load balancing to other standby FEPs, and if no channel switching occurs, the RTU channel information will be published periodically. 17. The system according to claim 16 for redundancy and load balancing of multiple acquisition devices based on a soft bus, wherein the allocation rule of the RTU channel in (1) is: a) If N _rtu <= N _fep , assign the RTUs to the FEPs in sequence according to the RTU and FEP numbers in ascending order; b) If N _rtu >N _fep , the number of RTUs allocated by each FEP is

Assign RTU groups to FEPs in ascending order of RTU and FEP numbers. where the number of RTUs is N _rtu , the number of FEPs is N _fep , and the number of FEPs is i, where i=0,1,2...,

Indicates rounded down. 18. The system according to claim 16 for redundancy and load balancing of multiple collection devices based on soft bus, wherein the collection service in (2) loads corresponding device drivers and corresponding device drivers according to RTU configuration. The collection protocol establishes communication with the subsystem; the forwarding service publishes business data in real time according to the forwarding table, and the synchronization service synchronizes the RTU channel data to the FEP where other redundant RTU channels are located in real time. 19. A system for redundancy and load balancing of multiple acquisition devices based on a soft bus according to claim 16, wherein the load balancing rule in (3) is specifically: A) If a certain RTU channel of the FEP is not in the running state and the duration exceeds T _offline , select the current optimal FEP among other FEPs, and switch the RTU channel to the optimal FEP. The selection of the optimal FEP is determined by the CPU of the FEP. The usage rate U _cpu , the memory usage rate U _mem and the network status NS are determined. The specific calculation formula is: 0.5×NS+0.3×(1-U _cpu )+0.2×(1-U _mem ) The FEP with the largest calculation result is the optimal FEP. If there are multiple FEPs with the same calculation result, the FEP with the largest number is taken as the optimal FEP; B) Set the CPU usage rate and memory usage rate of the FEP to U. If U is greater than the set value U _max and the duration exceeds T _overload , some RTU channels under the FEP need to be allocated to other FEPs. 20. a kind of system based on the redundancy of a plurality of acquisition equipment of soft bus and load balancing according to claim 16, it is characterized in that, the distribution rule in described B) is as follows: B1) All RTU channels configured as load balancing under the FEP are sorted in ascending order according to the channel-related usage rate U _rtu ; B2) Read _Urtu in turn, and select the FEP with the lowest current related usage rate U _best ; B3) If U _rtu +U _best <U _max , switch the corresponding RTU channel to the FEP with the lowest usage rate, and set U=UU _rtu and U _best =U _best +U _rtu at the same time; B4) If U _rtu +U _best >U _max , jump out of the allocation process; B5) If UU _rtu >U _max , repeat step B2, otherwise jump out of the allocation process.

Images