A device status point code subscription method based on redis

Abstract

The present invention discloses a device status point code subscription method based on redis, comprising a device status point code configuration step, a subscription configuration step, a subscription interface activation step, and a subscription interface sleep or cancellation step. Redis is used as a real-time database, and the high-efficiency read and write performance of redis is utilized to well solve the real-time problem. The device status of each system can be centrally monitored, and all point codes only need to be configured in the monitoring system, and the scalability is very good. In addition, the scheme defines a complete device status point code subscription mechanism, which can well meet the needs of the actual monitoring system, and the process is simple and the implementation is not complicated.

Description

Technical Field

[0001] The present invention relates to the technical field of rail transit signal control, and more specifically to a device status point code subscription method based on Redis. Background Art

[0002] In the field of rail transit, organizational operation has always been an extremely important part. Against the background of the development of modern rail transit construction, automation and intelligence have increasingly become the mainstream of organizational operation. To achieve this automated and intelligent upgrade, it is necessary to perform efficient and accurate signal detection, identification, and reading of the entire rail transit system in order to obtain the operating status of rail transit equipment and facilities and adjust organizational operation strategies.

[0003] At present, it is a very important function for the monitoring system to monitor the operating status of equipment. It conducts real-time monitoring of equipment point codes such as analog quantities, enumeration quantities, and switch quantities of signal, vehicle, electromechanical and other systems. By real-time monitoring of changes in the operating status of equipment, hidden dangers of equipment can be discovered in time, thereby preventing equipment failures and ensuring the normal operation of equipment.

[0004] However, traditional equipment operation status monitoring technology requires the collection, processing and storage of the operation data of all online equipment, so as to aggregate, cluster, analyze and judge the data, and compare the history to finally generate the corresponding monitoring results. However, with the increasing size of rail transit systems, more complex designs, and more advanced functions, the monitoring of system equipment with this traditional monitoring technology will face the problems of large data volume, complex data types, and large space occupied by stored data, resulting in a sharp increase in the demand for data processing computing power and an inability to provide timely and accurate monitoring results.

[0005] As for the remote dictionary service, Redis is a memory-based Key-Value database. It is an open source data service technology written in ANSI C language, supports the network, can be based on memory or can be persistent. Its typical characteristics are very fast data reading speed and it provides a publish-subscribe message communication mode. The equipment point codes such as analog quantities, enumeration quantities and switch quantities to be monitored by our rail transit monitoring system are typical Key-Value pairs, and the number of equipment point codes is large. The real-time requirements of the monitoring system are high. To meet these requirements, it is difficult to achieve based on traditional database technology, and the characteristics of Redis are fully capable of meeting these requirements. Therefore, we need a system monitoring device based on Redis to meet the current increasing monitoring needs of rail transit systems. Summary of the invention

[0006] The purpose of the present invention is to provide a redis-based device status point code subscription mechanism for realizing real-time monitoring of the status of each system device, which is provided to the monitoring system in the form of a dll dynamic link library. The dll dynamic link library is essentially a redis client that realizes the device status point code subscription mechanism.

[0007] The objective of the present invention is achieved through the following technical solutions:

[0008] The present invention provides a device status point code subscription method based on redis, comprising the following steps:

[0009] The equipment status point code configuration step reads the configuration files of all the equipment in the monitoring system that need to be subscribed by the monitoring system, and configures each equipment including the equipment switch status, equipment point code serial number, equipment system information, equipment line information, equipment station information, and equipment identification information status point code, and obtains a redis server containing several types of data. Each equipment identification information uniquely corresponds to a specific equipment. The status point code of each equipment in the configuration file occupies a line. For example, a certain equipment point code of the vehicle system: BIT, 0, BAS, 9, JTQ, BAS_JSB_A0_FBST1, the first field BIT indicates that this is a switch quantity, the second field 0 indicates the point code serial number, the third field BAS indicates that the equipment belongs to the water pump system, the fourth field 9 indicates that the equipment belongs to Line 9, the fifth field JTQ indicates that the equipment belongs to Jituo Bridge Station, and the last field BAS_JSB_A0_FBST1 is the equipment identification information. The equipment identification information is unique and fixed in the system to which it belongs.

[0010] In the equipment status point code configuration step, the systems to which the equipment belongs include a signal system, a vehicle system, and an electromechanical system.

[0011] In the device status point code configuration step, after obtaining the configuration file, the uniqueness of the status point codes contained in the several types of data volumes needs to be determined, and the repeated status point codes in the configuration file need to be deleted or modified. Each device that needs to be subscribed should have a single status point code in a configuration file, as long as there is no repeated configuration of the status point code in a configuration file.

[0012] The various data quantities include analog quantities, enumeration quantities, switch quantities, etc.

[0013] In the configuration subscription step, the monitoring system sends a request message for the device to be subscribed to the redis database obtained in the device status point code configuration step, and subscribes to the information of the corresponding device from the redis server. For example, the vehicle system air conditioning equipment, traction equipment, braking equipment, etc. correspond to the air conditioning monitoring, traction monitoring, braking monitoring and other interfaces in the monitoring system. Opening a monitoring interface is to initiate a subscription to the corresponding device. The redis server can receive the subscription request of the monitoring system and send the device status to the monitoring system, hibernate or cancel the subscription that has not been updated for a long time in the monitoring system, and activate the monitoring system to check the subscription request according to the update of the device status. That is, the entire subscription process is that the monitoring system as a subscriber sends the subscription request of the corresponding device, and the publisher of the device data saves the subscription information and subscribes to the corresponding channel in the redis server (the channel is the message communication mode of publishing and subscribing provided by the redis server itself). The request information includes the point code set of the device to be subscribed, the subscription number, the name of the subscription topic, and the handle of the monitoring window. The device status point code configured above is the point code value of all devices on each interface in the monitoring system (one device point code uniquely identifies one device). The subscription number uniquely identifies a subscriber in the monitoring system (that is, the corresponding interface or subscription instruction). The subscription topic name is the name of the corresponding device channel in the redis server. Each system that needs to monitor the device status of the protocol uses a subscription topic. The window handle uniquely identifies an interface. Some redundancy can be deleted.

[0014] In the subscription interface activation step, the redis server marks the subscription interface corresponding to the request information first sent by the monitoring system in the configuration subscription step as activated, and marks the subscription interface corresponding to the previous request information of the same monitoring system as dormant; in the activated state, when the subscribed device status point code corresponding to the subscription interface changes, the subscription interface is refreshed accordingly; in the dormant state, the subscription interface is not refreshed until the same monitoring system opens the interface again (i.e., re-reads the result of the previous request information), without reconfiguring the subscription, the redis server re-marks the interface as activated; when the device corresponding to the request information has a status change, if the corresponding subscription interface is in an activated state, the status point code is refreshed on the subscription interface;

[0015] In the subscription interface step, the publish-subscribe message communication mode of redis is used. The sender sends a message, the receiver receives the message, and the channel for transmitting the message is called a channel. Multiple receivers can subscribe to a channel at the same time. When the sender sends a message to the channel, all receivers can receive the message.

[0016] The subscription interface activation step marks the subscription interface corresponding to the request information first sent by the monitoring system in the subscription configuration step as an activated state, specifically, comprising the following steps:

[0017] Step S1, initializing the subscription point code, the redis server groups the status point codes of each device according to the data volume of several types in the device status point code configuration step, and creates a redis dictionary for storage;

[0018] Redis itself is a Key-Value database. Redis generally has 16 databases by default, and the database index numbers range from 0 to 15. In step S1, it is agreed that in the redis server, the database with index number 0 is used to store switch quantities, the database with index number 1 is used to store enumeration quantities, and the database with index number 1 is used to store analog quantities.

[0019] Step S2, the monitoring system initializes its subscription interface, traverses the device status point code set of the subscribed device, and obtains the Value of the device status point code from the redis dictionary in step S1 to refresh the interface;

[0020] Value is stored in the Redis database and written to the Redis database by the data access service. For the signal, vehicle, electromechanical and other systems in this solution that need to monitor the status of the equipment, a data access service needs to be implemented. When the status of the equipment in the signal, vehicle and electromechanical system changes, in this solution, the subscribed equipment status changes, and the Value of the corresponding equipment status point code also changes. It is sent to the data access service of the system where the equipment is located through the HTTP protocol or MODBUS protocol, and the full amount of equipment data will be sent to the Redis server at regular intervals (for example, 10 minutes), or the full amount of equipment status data will be sent when a data access service connection is established with the Redis server.

[0021] Step S3, start the listening thread. When there is a status change point code published in the subscription topic corresponding to the request information, the updated status is obtained and the corresponding point code set is refreshed. If the detection system interface to which the listening thread belongs is in an activated state, it is refreshed on the subscription interface corresponding to the monitoring system. Starting the listening thread here means that if a subscriber subscribes to our publisher, whenever there is a new message in the subscribed channel, the publisher needs to obtain the channel's new message. The message in the channel is sent by the data access service, and the information contained is the device point code set of the device status change, and then the status value is obtained from the redis database, so a thread needs to be started to complete this task.

[0022] In step S3, the stateful point code is published, and the redis server traverses and compares the refreshed point code Key value set with the point code Key value set in the request information received by the redis server. If the corresponding state point code is subscribed and the corresponding subscription interface is activated, the redis server obtains the latest Value of the point code from the corresponding database and refreshes it on the subscription interface;

[0023] In step S3, there are three interfaces for refreshing the subscription interface corresponding to the monitoring system, namely, interfaces for refreshing the switch quantity, enumeration quantity and analog quantity.

[0024] The subscription interface sleep or cancellation step: if the monitoring system switches the subscription interface, that is, the same monitoring system sends a new request information to cover the previous request information, the subscription interface corresponding to the previous request information will be marked as dormant; if the monitoring system closes the subscription interface, that is, the request information is withdrawn or deleted, the device corresponding to the request information will be unsubscribed, and the request information will be deleted from the redis server.

[0025] Compared with the prior art, the above technical solution includes the following innovations and beneficial effects (advantages):

[0026] The technical solution of this application uses redis as a real-time database, and utilizes redis's efficient read and write performance to solve the real-time problem well. It can centrally monitor the equipment status of each system, and only needs to configure all point codes in the monitoring system, with good scalability. In addition, this solution defines a complete set of equipment status point code subscription mechanisms, which can well meet the needs of actual monitoring systems, with a simple process and uncomplicated implementation.

[0027] As for the field of train control technology, the main function of the monitoring system is to monitor the operating status of the equipment in real time, and the subscription mechanism provided in this application is an optimized technical means for realizing this function. In the monitoring system, the status change of a certain device is reflected as a change in the color of an icon or a change in the shape of an icon after being processed by the technical solution of the present invention. In this subscription mechanism, the monitoring system is regarded as a set of subscribers, which is intuitive and accurate. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The foregoing and following detailed description of the present invention will become more apparent when read in conjunction with the following drawings, in which:

[0029] Figure 1 It is a timing diagram of the device status point code subscription mechanism of the present invention;

[0030] Figure 2 It is a flowchart of the interface subscription device point code in a specific embodiment of the present invention;

[0031] Figure 3 The flowchart of the subscription point code status change in a specific embodiment of the present invention. DETAILED DESCRIPTION

[0032] The technical solution for achieving the purpose of the present invention is further described below through specific embodiments. It should be noted that the technical solution claimed to be protected by the present invention includes but is not limited to the following embodiments.

[0033] This embodiment provides a device status point code subscription method based on redis, and the device status point code subscription mechanism timing is as follows Figure 1 As shown, specifically, the solution includes a device status point code configuration step, a subscription configuration step, a subscription interface activation step, and a subscription interface sleep or cancellation step.

[0034] Specifically, the device status point code configuration step is to read the configuration files of all devices in the monitoring system that need to be subscribed by the monitoring system, and configure each device including the device switch status, device point code serial number, device system information, device line information, device station information, and device identification information status point code, and obtain a redis server containing several types of data. Each device identification information uniquely corresponds to a specific device. The status point code of each device in the configuration file occupies a line, such as a device point code of the vehicle system: BIT, 0, BAS, 9, JTQ, BAS_JSB_A0_FBST1, the first field BIT indicates that this is a switch quantity, the second field 0 indicates the point code serial number, the third field BAS indicates that the device belongs to the water pump system, the fourth field 9 indicates that the device belongs to Line 9, the fifth field JTQ indicates that the device belongs to the Jituo Bridge Station, and the last field BAS_JSB_A0_FBST1 is the device identification information, and the device identification information is unique and fixed in the system to which it belongs.

[0035] And preferably, the system to which the device belongs includes a signal system, a vehicle system, and an electromechanical system; after obtaining the configuration file, the uniqueness of the status point codes contained in the several types of data volumes needs to be determined, and the repeated status point codes in the configuration file need to be deleted or modified. Each device that needs to be subscribed should have a single status point code in a configuration file, as long as there is no repeated configuration of the status point code in a configuration file; the various data volumes include analog quantities, enumeration quantities, and switch quantities, etc.

[0036] The configuration subscription step is that the monitoring system sends a request message for the device to be subscribed to the redis database obtained in the device status point code configuration step, and subscribes to the information of the corresponding device from the redis server. For example, the vehicle system air conditioning equipment, traction equipment, braking equipment, etc. correspond to the air conditioning monitoring, traction monitoring, braking monitoring and other interfaces in the monitoring system. Opening a monitoring interface is to initiate a subscription to the corresponding device. The redis server can receive the subscription request of the monitoring system and send the device status to the monitoring system, hibernate or cancel the subscription that has not been updated for a long time in the monitoring system, and activate the monitoring system to check the subscription request according to the update of the device status. That is, the entire subscription process is that the monitoring system as a subscriber sends the subscription request of the corresponding device, and the publisher of the device data saves the subscription information and subscribes to the corresponding channel in the redis server (the channel is a message communication mode for publishing and subscribing provided by the redis server itself). The request information includes the point code set of the device to be subscribed, the subscription number, the name of the subscription topic, and the handle of the monitoring window. The device status point code configured above is the point code value of all devices on each interface in the monitoring system (one device point code uniquely identifies one device). The subscription number uniquely identifies a subscriber in the monitoring system (that is, the corresponding interface or subscription instruction). The subscription topic name is the name of the corresponding device channel in the redis server. Each system that needs to monitor the device status of the protocol uses a subscription topic. The window handle uniquely identifies an interface. Some redundancy can be deleted.

[0037] In the subscription interface activation step, the redis server marks the subscription interface corresponding to the request information first sent by the monitoring system in the configuration subscription step as activated, and marks the subscription interface corresponding to the previous request information of the same monitoring system as dormant; in the activated state, when the subscribed device status point code corresponding to the subscription interface changes, the subscription interface is refreshed accordingly; in the dormant state, the subscription interface is not refreshed until the same monitoring system opens the interface again (that is, re-reviews the result of the previous request information), without reconfiguring the subscription, the redis server re-marks the interface as activated; when the device corresponding to the request information has a status change, if the corresponding subscription interface is in an activated state, the status point code is refreshed on the subscription interface; in the subscription interface step, the redis publish-subscribe message communication mode is used, the sender sends a message, the receiver receives the message, the channel for transmitting the message is called a channel, multiple receivers can subscribe to a channel at the same time, when the sender sends a message to the channel, all receivers can receive the message.

[0038] More specifically, the subscription interface activation step marks the subscription interface corresponding to the request information first sent by the monitoring system in the subscription configuration step as an activated state, and specifically includes the following steps:

[0039] Step S1, subscription point code initialization, redis server groups the status point codes of each device according to the data volume of several types in the device status point code configuration step, and creates a redis dictionary to save. Redis itself is a Key-Value database. Redis generally has 16 databases by default, and the database index numbers are from 0 to 15. Therefore, in step S1, it is agreed that in the redis server, the database with index number 0 is used to store switch quantities, the database with index number 1 is used to store enumeration quantities, and the database with index number 1 is used to store analog quantities.

[0040] In step S2, the monitoring system initializes its subscription interface, traverses the device status point code set of the subscribed device, and obtains the Value of the device status point code from the redis dictionary in step S1 to refresh the interface; the Value is stored in the Redis database and written to the redis database by the data access service. For the signal, vehicle, electromechanical and other systems in this solution that need to monitor the device status, a data access service needs to be implemented. If the device status in the signal, vehicle and electromechanical system changes, in this solution, the subscribed device status changes, and the Value of the corresponding device status point code also changes. It is sent to the data access service of the system where the device is located through the HTTP protocol or the MODBUS protocol, and the full device data will be sent to the redis server at regular intervals (for example, 10 minutes), or the full device status data will be sent when a data access service connection is established with the redis server.

[0041] Step S3, start the listening thread. When a state change point code is published in the subscription topic of the corresponding request information, the updated state is obtained and the corresponding point code set is refreshed. If the detection system interface to which the listening thread belongs is in an activated state, it is refreshed on the subscription interface corresponding to the monitoring system. Here, starting the listening thread means that if a subscriber subscribes to our publisher, whenever the subscribed channel has a new message, the publisher needs to obtain the channel's new message. The message in the channel is sent by the data access service, and the information contained is the device point code set of the device state change, and then the state value is obtained from the redis database, so a thread needs to be started to complete this task. When a state change point code is published, the redis server traverses and compares the refreshed point code Key value set with the point code Key value set in the request information received by the redis server. If the corresponding state point code is subscribed and the corresponding subscription interface is in an activated state, the redis server obtains the latest Value value of the point code from the corresponding database and refreshes it on the subscription interface; there are three interfaces for refreshing the subscription interface corresponding to the monitoring system, namely, the interface for refreshing the switch quantity, enumeration quantity and analog quantity.

[0042] The subscription interface sleep or cancellation step: if the monitoring system switches the subscription interface, that is, the same monitoring system sends a new request information to cover the previous request information, the subscription interface corresponding to the previous request information will be marked as dormant; if the monitoring system closes the subscription interface, that is, the request information is withdrawn or deleted, the device corresponding to the request information will be unsubscribed, and the request information will be deleted from the redis server.

[0043] The technical solution provided in this embodiment uses redis as a real-time database, and utilizes redis's efficient read and write performance to solve the real-time problem well. It can centrally monitor the equipment status of each system, and only needs to configure all point codes in the monitoring system, and has good scalability. In addition, this solution defines a complete set of equipment status point code subscription mechanisms, which can well meet the needs of the actual monitoring system, with a simple process and uncomplicated implementation.

[0044] The above solution can be further explained in conjunction with the accompanying drawings. Figure 2 As shown, this technical solution includes the following steps:

[0045] Step S1: The monitoring system needs to configure all device status point codes to be monitored. The device point codes of different systems are configured in different configuration files. In the point code configuration file, each device point code occupies one line in the configuration file. After the monitoring system is started, the device point code configuration file is read to verify the uniqueness of the device status point codes contained in various data quantities (analog quantity, enumeration quantity, switch quantity, etc.). If there are duplicate point codes of the same data type, reconfiguration is required.

[0046] Step S2: When the monitoring system opens a certain interface, it sends the point code set configured in the interface, the subscription number, the name of the subscription topic, and the handle of the window to the redis client for subscription.

[0047] Step S3, the Redis client saves the interface subscription information, subscribes to the redis server, and marks the subscription interface as activated; (there are two states when the interface subscribes to the point code: activated and dormant. In the activated state, when the subscribed device point code status changes, the interface is refreshed accordingly. In the dormant state, it is not refreshed, but it is still in the subscription state. When the interface is opened again, there is no need to re-subscribe to the point code, just change to the activated state).

[0048] The corresponding step S3 is specifically:

[0049] Step S31, the subscription point code is initialized, the redis client groups the point codes according to the data type (analog quantity, enumeration quantity and switch quantity) of the point codes, and creates a dictionary for storage;

[0050] Step S32: The subscription interface of the monitoring system is initialized, the subscribed point code set is traversed, and the point code Value is obtained from the corresponding redis database to refresh the interface;

[0051] Step S33, start the listening thread, listen to whether there is any status change point code published in the subscription topic, and obtain the point code set of the status update if there is. If the detection system interface to which the listening thread belongs is in an activated state, the callback interface is refreshed on the monitoring system interface (there are three interfaces for refreshing the interface, namely, the interface for refreshing the switch quantity, enumeration quantity and analog quantity).

[0052] Next, enter the subscription point code status change, specifically:

[0053] Step S4: At the data access system end, when the device point code status changes, the changed device status is written to redis, different data types are written to different databases of redis, and the device point code Key value of the changed status is published to the subscribed topic;

[0054] Step S5, the Redis client receives the point code Key value set of the changed status from the subscribed topic, and traverses it. If the point code is subscribed and the status of the interface is activated, the point code Value is obtained from the corresponding database of redis, and the callback interface is refreshed on the interface;

[0055] Step S6: If the monitoring system switches interfaces, the subscription state of the interface before the switch is set to a dormant state, and the interface after the switch is subscribed according to steps S2 and S3;

[0056] Step S7: When a certain interface is closed, the subscription is canceled and the redis client deletes the saved information.

Claims

1. A device status point code subscription method based on redis, characterized in that: The following steps are involved: The device status point code configuration step reads the configuration files of all devices in the monitoring system that need to be subscribed by the monitoring system, configures each device with a status point code including the device switch status, device point code serial number, device system information, device line information, device station information, and device identification information, and obtains a redis server containing several types of data. Each device identification information uniquely corresponds to a specific device, and the status point code of each device in the configuration file occupies one line; Configuration subscription step, the monitoring system sends a request message of the device to be subscribed to the redis database obtained in the device status point code configuration step, and subscribes to the information of the corresponding device from the redis server, the request message includes the point code set of the device to be subscribed, the subscription number, the name of the subscription topic, and the handle of the monitoring window; In the subscription interface activation step, the redis server marks the subscription interface corresponding to the request information first sent by the monitoring system in the configuration subscription step as an activated state, and marks the subscription interface corresponding to the previous request information of the same monitoring system as a dormant state; in the activated state, when the subscribed device status point code corresponding to the subscription interface changes, the subscription interface is refreshed accordingly; In dormant state, the subscription interface is not refreshed until the same monitoring system opens the interface again. There is no need to reconfigure the subscription, and the redis server re-marks the interface as active. When the device corresponding to the requested information changes state, if the corresponding subscription interface is in active state, the status point code is refreshed on the subscription interface. The subscription interface activation step marks the subscription interface corresponding to the request information first sent by the monitoring system in the configuration subscription step as activated, including step S1, subscription point code initialization, the redis server groups the status point codes of each device according to the data volume of several types in the device status point code configuration step, and creates a redis dictionary for storage; step S2, the monitoring system initializes its subscription interface, traverses the device status point code set of the subscribed device, and obtains the Value value of the device status point code from the redis dictionary in step S1 to refresh the interface; step S3, starts the listening thread, when the status change point code is published in the subscription subject of the corresponding request information, the updated status is obtained and the corresponding point code set is refreshed, if the detection system interface to which the listening thread belongs is in an activated state, then refresh is performed on the subscription interface corresponding to the monitoring system; The subscription interface sleep or cancellation step: if the monitoring system switches the subscription interface, that is, the same monitoring system sends a new request information to cover the previous request information, the subscription interface corresponding to the previous request information will be marked as dormant; if the monitoring system closes the subscription interface, that is, the request information is withdrawn or deleted, the device corresponding to the request information will be unsubscribed, and the request information will be deleted from the redis server.

2. A device status point code subscription method based on redis as claimed in claim 1, characterized in that: In the equipment status point code configuration step, the systems to which the equipment belongs include a signal system, a vehicle system, and an electromechanical system.

3. A device status point code subscription method based on redis as described in claim 1 or 2, characterized in that: In the device status point code configuration step, after obtaining the configuration file, the uniqueness of the status point codes included in the several types of data volumes needs to be determined, and the repeated status point codes in the configuration file need to be deleted or modified.

4. A device status point code subscription method based on redis as claimed in claim 3, characterized in that: The several types of data quantities include analog quantities, enumeration quantities and switch quantities.

5. A device status point code subscription method based on redis as claimed in claim 1, characterized in that: In the step S1, it is agreed that in the redis server, the database with index number 0 is used to store switch quantities, the database with index number 1 is used to store enumeration quantities, and the database with index number 1 is used to store analog quantities.

6. A device status point code subscription method based on redis as claimed in claim 1, characterized in that: When the subscribed device status changes, the Value of the corresponding device status point code also changes. It is sent to the data access service of the device system itself through the HTTP protocol or MODBUS protocol, and the full device data will be sent to the redis server at regular intervals, or the full device status data will be sent when a data access service connection is established with the redis server.

7. A device status point code subscription method based on redis as claimed in claim 1, characterized in that: In step S3, a stateful point code is published, and the redis server traverses and compares the refreshed point code Key value set with the point code Key value set in the request information received by the redis server. If the corresponding state point code is subscribed and the corresponding subscription interface is activated, the redis server obtains the latest Value of the point code from the corresponding database and refreshes it on the subscription interface.

8. A device status point code subscription method based on redis as described in claim 1 or 7, characterized in that: In step S3, there are three interfaces for refreshing the subscription interface corresponding to the monitoring system, namely, interfaces for refreshing the switch quantity, enumeration quantity and analog quantity.

Images