Application monitoring and collaboration method, device and system

Abstract

The present invention discloses an application monitoring and collaboration method, device and system to solve the problem of non-closed loop of deterministic control of multiple applications in the "edge-end-cloud" of the industrial Internet network. The method is used for the deterministic network middleware server side and includes the following steps: obtaining the task data packet corresponding to the application task, collecting task data, and generating or updating the application dependency graph; making policy decisions based on the application dependency graph and the task data packet, generating an overall deterministic policy, and splitting the overall deterministic policy into policies on each device; translating the policies on each device into corresponding device control commands or device configuration parameters, and issuing the device control commands or device configuration parameters. The present application also includes devices and systems for using the method. The present invention is particularly suitable for the industrial Internet within an enterprise.

Description

Technical Field

[0001] The present invention relates to the field of industrial Internet technology, and in particular to an application monitoring and collaboration method, device and system. Background Art

[0002] The Industrial Internet connects various elements within an enterprise's intranet to form a digital and intelligent production model. It is the result of a deep integration of industrial systems, network technologies, computing technologies, and sensor technologies. Enterprise networks contain a large number of devices with diverse functions. "Network-edge-end-cloud" primarily refers to deterministic networks, edge computing devices, industrial terminal devices, and cloud platforms. Currently, devices within these networks are relatively independent. When performing deterministic configuration, there is no fully collaborative interoperability interface between these devices. Current technology only enables collaborative configuration between any two devices, lacking a centralized management and refined coordination mechanism tailored to the specific characteristics of each device. Specifically, there is no application-layer deterministic middleware for centralized control of the network-edge-end-cloud, ensuring the overall deterministic requirements of the network-edge-end-cloud. There is also no interface protocol for transmitting application-layer deterministic information between these devices. Summary of the Invention

[0003] The present invention provides an application monitoring and collaboration method, device and system to solve the problem of non-closed-loop deterministic control of multiple applications in the "network-edge-end-cloud" industrial Internet network in existing methods, and is particularly suitable for the industrial Internet within enterprises.

[0004] To solve the above problems, the present invention is achieved as follows:

[0005] In the first aspect, an embodiment of the present invention provides an application monitoring and collaboration method for an application layer deterministic network middleware server, comprising the following steps: obtaining a task data packet corresponding to an application task, collecting task data, and generating or updating an application dependency graph, wherein the task data packet includes at least: device status, application status, application layer deterministic events, and application layer deterministic requirements; making policy decisions based on the application dependency graph and the task data packet, generating an overall deterministic policy, and splitting the overall deterministic policy into policies on each device; translating the policies on each device into corresponding device control commands or device configuration parameters, and issuing the device control commands or device configuration parameters.

[0006] Preferably, the application monitoring and collaboration method also includes: the specific strategies used when making policy decisions include at least one of the following: making algorithm-based decisions in response to the quantitative requirements of each application task to obtain corresponding quantitative parameters; making discrete decisions through classifiers in response to the quantitative requirements of each application task; generating application configurations and application parameters through manual review in response to the quantitative requirements of each application task.

[0007] Preferably, the application monitoring and collaboration method uses the TCP protocol to send the device control commands or device configuration parameters to each device through the southbound interface. The specific format of the southbound interface includes deterministic service type, message type, deterministic service header, length, payload and checksum. The deterministic service type is used to provide a coarse-grained classification of application tasks; the message type is a field used to mark the purpose of the sent data packet, including registration messages, pre-operation messages, demand messages, data updates, configuration updates, heartbeat messages and query messages; the deterministic service header is present in each message and includes task number, task name, timestamp, message sequence number, time characteristics and bandwidth. The payload is the data carried by the application layer deterministic message, which is used to describe the application status, network configuration and events.

[0008] Preferably, the application monitoring and collaboration method further includes: constructing, maintaining and destroying the application dependency graph.

[0009] Preferably, the step of generating or updating the application dependency graph further comprises: generating an application communication relationship sequence according to the collected task data, and forming the application dependency graph in a network topology manner.

[0010] Preferably, the payload is an application-layer deterministic southbound payload, specifically comprising: network controller configuration, edge configuration, cloud configuration, and industrial terminal configuration. The data format corresponding to the network controller configuration includes task number, task type, latency, and jitter. The data formats corresponding to the edge and cloud configurations are identical, including task number, task type, latency, preemption, and computational complexity. The data format corresponding to the industrial terminal configuration includes task number, task type, latency, operation list, and description.

[0011] In the second aspect, an embodiment of the present invention also provides an application monitoring and collaboration method for a deterministic network device end, comprising the following steps: obtaining device status and application status through an operating system, obtaining detailed application information through an application interface, wherein the detailed application information includes at least application layer deterministic events and application layer deterministic requirements; encapsulating the application status and detailed information into a task data packet for sending; receiving device control commands or device configuration parameters, and calling a response configuration update interface for configuration update.

[0012] Preferably, the application monitoring and collaboration method uses the TCP protocol server to send information or responses through the northbound interface, and the specific format of the northbound interface includes deterministic service type, message type, deterministic service header, length, payload and checksum. The deterministic service type is used to provide a coarse-grained classification of application tasks. The message type is a field used to mark the purpose of the data packet, including registration messages, pre-operation messages, demand messages, data updates, configuration updates, heartbeat messages and query messages. The deterministic service header is a message that each message must have, including task number, task name, timestamp, message sequence number, time characteristics and bandwidth. The payload is the data carried by the application layer deterministic message, which is used to describe the application status, network configuration and events.

[0013] Preferably, the application monitoring and collaboration method further comprises: acquiring application status and detailed information in an active and / or passive manner.

[0014] Preferably, the payload is an application-layer deterministic northbound payload, comprising: an application request mode, a real-time data mode, and a pre-operation reporting mode. The application request mode comprises a task registration request, deterministic requirements, a deterministic requirements report, and a task shutdown request. The data format corresponding to the task registration request comprises a task number, an operation number, a deterministic requirement, and a checksum. The data format corresponding to the deterministic requirements comprises a service level, latency, jitter, bandwidth, load, and task type. The data format corresponding to the deterministic requirements report comprises a task number, an operation number, a deterministic requirement. The data format corresponding to the task shutdown request comprises a task number and an operation number. The real-time data mode comprises application data updates and device data updates; the data format corresponding to the application data update comprises a task number, an event code, and event parameters; the data format corresponding to the device data update comprises CPU utilization, memory utilization, bandwidth utilization, an event code, and an event description. The data format corresponding to the pre-operation reporting mode comprises a task number, a relay sequence number, a status code, a timestamp, and a pre-operation operation description.

[0015] In a third aspect, an embodiment of the present invention further provides an application monitoring and collaboration middleware device, which uses the application monitoring and collaboration method described in any embodiment of the present invention for the server side, comprising: a monitoring and analysis module, a decision module, and a network edge control module. The monitoring and analysis module is used to receive task data packets corresponding to application tasks, collect task data, and generate or update an application dependency graph. The decision module is used to make policy decisions based on the application dependency graph and task data, generate an overall deterministic policy, and split the overall deterministic policy into policies on each device. The network edge control module is used to translate the policies on each device into corresponding device control commands or device configuration parameters, and issue the device control commands or device configuration parameters.

[0016] Preferably, the monitoring and analysis module is further used to construct, maintain and destroy the application dependency graph.

[0017] In a fourth aspect, an embodiment of the present invention further provides an application monitoring and collaboration middleware agent device, which uses any of the application monitoring and collaboration methods of the present invention for a device, and includes: an application monitoring module, a device monitoring module, and a configuration update module. The device monitoring module is used to obtain the device status through the operating system; the application monitoring module is used to obtain the application status through the operating system and obtain detailed information about the application through the application interface. The configuration update module is used to encapsulate the device status, application status, and detailed information into a data packet for transmission, receive device control commands or device configuration parameters, and call a response configuration update interface to perform a configuration update.

[0018] Preferably, the device monitoring module is further configured to acquire device status in an active and / or passive manner; and the application monitoring module is further configured to acquire detailed information of application tasks in an active and / or passive manner.

[0019] In a fifth aspect, an embodiment of the present invention further provides an application monitoring and collaboration system, comprising an application monitoring and collaboration middleware device and an application monitoring and collaboration middleware agent device corresponding to any one embodiment of the present invention.

[0020] The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of the present application.

[0021] Furthermore, the present application also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in any embodiment of the present application when executing the computer program.

[0022] At least one of the above-mentioned technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: The present invention provides an application layer deterministic collaboration method for "network-edge-end-cloud" collaboration, which can realize the industrial network deployment, application layer deterministic software registration, network event monitoring, application layer deterministic decision-making, and network configuration distribution required for "network-edge-end-cloud" collaboration, provide centralized control for application layer deterministic control, and provide effective infrastructure and technical means for the subsequent global collaboration of complex applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0024] Figure 1 This is an embodiment of the method flow of the present invention used on the server side;

[0025] Figure 2 This is an embodiment of the method flow of the present invention used on a device side;

[0026] Figure 3 An embodiment of the method flow of the present invention for use in a system;

[0027] Figure 4 This is an embodiment of the middleware device of the present invention;

[0028] Figure 5 This is an embodiment of the middleware proxy device of the present invention;

[0029] Figure 6 This is a system embodiment of the present invention. DETAILED DESCRIPTION

[0030] To make the objectives, technical solutions, and advantages of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below in conjunction with specific embodiments of the present invention and corresponding drawings. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0031] Determinism means ensuring low latency, low jitter, zero packet loss, and high reliability for tasks. Taking deterministic networks as an example, achieving synchronized scheduling of network-wide devices requires mechanisms such as time synchronization, centralized control, and resource reservation. However, existing deterministic networks primarily rely on Layer 2-3 technologies. While the network can guarantee deterministic metrics for the transmission process, when multiple applications have dependencies and the control chain involves edge computing or cloud computing platforms, the processing latency of complex computing applications cannot be guaranteed if related resources cannot be adjusted according to the application's deterministic requirements. As Industrial Internet tasks become increasingly complex, the control loop within enterprise intranets is currently fragmented.

[0032] The innovation of the present invention lies in: First, the present invention innovatively provides an application collaboration method, which realizes deterministic centralized control of the application layer by making overall decisions on the application tasks of each device end; Second, the network interface protocol and key parameters between the server end and the device end of the present invention can be used for monitoring and control in the visual network edge-cloud collaboration scenario.

[0033] The technical solutions provided by various embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0034] Figure 1 This is an embodiment of the method flow of the present invention used on the server side.

[0035] An application collaboration method, used for a deterministic network middleware server, specifically includes the following steps 101 to 103:

[0036] Step 101: Obtain a task data packet corresponding to an application task, collect task data, and generate or update an application dependency graph.

[0037] In step 101, the task data packet at least includes: application status, device status, application layer deterministic events and application layer deterministic requirements.

[0038] It should be noted that application status refers to the operations currently being performed by the application, resource consumption, configuration parameters, etc. Device status includes but is not limited to device manufacturer, device model, adopted (industrial) protocol, device performance, resource usage (CPU usage, storage usage, bandwidth usage), task queue, etc. Application layer deterministic events refer to inputs generated in response to changes in the device's application layer determinism. Application layer deterministic requirements refer to the formal description of indicators that the application provides deterministic services to each device, such as the network providing deterministic bandwidth, latency, and latency jitter, and edge computing devices providing upper bounds on processing latency and memory access speed.

[0039] In step 101, an application initiates a new application task, which is then encapsulated on the device side into a task data packet and uploaded to a deterministic network server. The data packet corresponding to the application task contains device status information and application status information.

[0040] It should be noted that the server side includes application collaborative middleware equipment. The deterministic network in the present invention refers to the application layer deterministic network, which includes the server side and the device side. The device side includes industrial terminals, edge devices, cloud computing devices and network control devices.

[0041] In step 101, the server periodically receives task data packets corresponding to application tasks.

[0042] In step 101, the server collects task data from the received task data packets, including device status information and application status information, analyzes and constructs them into deterministic requirements, application dependency graphs, statistical data, and application behavior descriptions.

[0043] In step 101, the application state and application layer deterministic events on the host device are obtained through the application layer deterministic agent in a combination of active and passive methods. After preliminary analysis, the original data and deterministic requirements are uploaded to the application layer deterministic middleware. The application layer deterministic middleware receives the data packets corresponding to the application tasks, collects the task data, and generates an application dependency graph.

[0044] It should be noted that the host device refers to the device that initiates the application on the device side; the active method means that the server side actively obtains basic status and application layer deterministic events from the device side by sending instructions, and the passive method means that the server side obtains device status and application layer deterministic events through listening.

[0045] In step 101, the application layer deterministic middleware receives deterministic metadata corresponding to the application task, generates an application communication relationship sequence, and forms an application dependency graph based on the network topology.

[0046] It should be noted that the deterministic metadata corresponding to an application task refers to the data structure that describes the deterministic requirements of the application's business. The communication relationship sequence refers to the chronologically ordered set of end-to-end communications that includes all steps in an application-layer deterministic control chain. The application dependency graph is a directed acyclic graph that represents the relationships between registered applications.

[0047] It should be noted that, in step 101, the application layer deterministic middleware server can dynamically update the application dependency graph according to the received task data packets that are updated in real time.

[0048] In step 101, the monitoring and analysis module of the application collaborative middleware device can perform information collection and analysis in response to the application on the device side, and upload relevant data, including but not limited to the resources, port numbers, manufacturers, versions, etc. used by the application, as well as the relationship between the application and various other applications, deterministic requirements, QoS (quality of service), SLA (service level agreement), etc. The monitoring and analysis module will perform independent preprocessing and aggregation in response to each specific application task, thereby providing multi-dimensional data support for the decision-making module of the application collaborative middleware device.

[0049] It should be noted that the methods of data collection, data statistics, preprocessing and feature extraction in the monitoring and analysis module are the same as those in the prior art. Specifically, real-time statistical results of devices, operating systems, networks, etc. can be obtained through open interfaces.

[0050] Step 102: Make a policy decision based on the application dependency graph and the task data packet, generate an overall deterministic policy, and split the overall deterministic policy into policies on each device.

[0051] In step 102, the server side makes a policy decision based on the deterministic requirements of each task and the application dependency graph, takes the device as the target, generates an overall deterministic policy, and splits the overall deterministic policy into policies on each device.

[0052] It should be noted that the overall deterministic strategy refers to the SLA for a business process involving multiple applications, and is a control rule that is formulated by global management software or equipment and covers all devices involved in the business process.

[0053] In step 102, the decision module of the application collaboration middleware device makes a decision based on the task data and application dependency graph provided by the monitoring and analysis module.

[0054] Furthermore, the specific strategies used by the decision module when making policy decisions include at least one of the following: first, in response to the quantitative requirements of each application task, an algorithm-based decision is made, and each different task is precisely calculated to obtain the corresponding quantitative parameters; second, in response to the quantitative requirements of each application task, a discrete decision is made through a classifier, such as identifying the approximate category of the application through hidden Markov, Bayesian, SVM and other classifiers or other similar classifiers, and the requirements uploaded by the task application are classified into a template already existing in the policy database, and then the matched policy is deployed; third, in response to the quantitative requirements of each application task, the application configuration and application parameters are generated by manual review, and the configuration efficiency can be improved by visualization or checking existing solutions.

[0055] In step 102, the policy on each device specifically corresponds to the policy on the industrial terminal, edge device, cloud computing device and network control device. If a device initiates an application task on the device side, the server side generates the policy for the corresponding device side accordingly.

[0056] Step 103: Translate the policy on each device into a corresponding device control command or device configuration parameter, and issue the device control command or device configuration parameter.

[0057] In step 103, the network edge control module of the collaborative middleware device translates the policy on each device into executable control commands or device configurations, and then sends them to the device end via a specific southbound interface.

[0058] In step 103, the southbound interface is an interface for the application collaboration middleware device to send configuration information or responses to each device-end device.

[0059] The application collaborative middleware device uses the TCP protocol through the southbound interface to send the device control commands or device configuration parameters to each device. The specific format of the southbound interface at least includes the deterministic service type, message type, deterministic service header, length, payload and checksum, as shown in Table 1 below.

[0060] Table 1 Specific format of deterministic messages carried by the southbound interface

[0061] Deterministic business Message Type Deterministic business head length load check

[0062] It should be noted that the specific format of the southbound interface may also include other data, which is not particularly limited here.

[0063] The deterministic business types are used to provide a coarse-grained classification of application tasks, enabling rapid decision-making. This coarse-grained classification of application tasks specifically includes periodic tasks, bursty tasks, and other categories. This classification of application tasks involves categorizing them into several coarse-grained categories, such as periodic and bursty tasks, rather than into detailed categories based on specific application functions.

[0064] The message type is a field used to mark the purpose of the data packet, including but not limited to registration request, registration response, pre-operation report, configuration update, etc. The message type occupies 2 bytes. Different types of messages do not occupy the same data bits, so multiple messages can be put into one data packet for transmission.

[0065] The message types specifically include a 2-bit registration message, a 1-bit pre-operation message, a 1-bit demand message, a 2-bit data update, a 3-bit configuration update, a 1-bit heartbeat message and a 2-bit query message, as shown in Table 2 below.

[0066] Table 2 Application layer deterministic message list

[0067]

[0068] The deterministic service header is a required message for each message and includes a task number, task name, timestamp, message sequence number, time characteristics, and bandwidth, as described in Table 3 below.

[0069] Table 3 Deterministic service header field list

[0070]

[0071]

[0072] The payload is data carried by application-layer deterministic messages and is used to describe information such as application status, network configuration, and events. In this embodiment of the present invention, the payload is an application-layer deterministic southbound payload, specifically in the form of network controller configuration, edge configuration, cloud configuration, and industrial terminal configuration.

[0073] Specifically, the network controller configuration data format includes task number, task type, latency, and jitter, as shown in Table 4 below. The task number refers to the unique number assigned to a specific service by an application when registering with the application layer deterministic middleware device. The task type refers to the classification category proactively given by the application from the perspective of application layer determinism, such as the classification based on time characteristics and demand characteristics. Latency refers to the total processing time requirement of the task initiator. Jitter refers to the absolute value of the variation in the forwarding delay between two consecutive data packets in the same data flow. The network controller configuration data format also includes other content, which is not specifically limited here.

[0074] Table 4 Network controller configuration data format

[0075] Task No. Task Type Latency Jitter ……

[0076] The data formats corresponding to the edge configuration and cloud configuration are the same, including task number, task type, latency, preemption, and computational complexity, as shown in Table 5. The task number refers to the unique number assigned to a specific service by the application when it registers with the application-layer deterministic middleware device. The task type refers to the classification category proactively given by the application from the perspective of application-layer determinism. Latency refers to the total processing time requirement of the task initiator. Preemption refers to the forwarding priority and computational priority. Computational complexity refers to the computational complexity of the service based on historical experience. The edge configuration and cloud configuration data formats also include other content, which is not specifically limited here.

[0077] Table 5 Edge configuration / cloud configuration data format

[0078] Task No. Task Type Latency Whether to preempt Computational complexity ……

[0079] The data format corresponding to the industrial terminal configuration includes the task number, task type, latency, operation list, and description, as shown in Table 6. The task number refers to the unique number assigned to a specific service by the application when registering with the application-layer deterministic middleware device. The task type refers to the classification category proactively given by the application from the perspective of application-layer determinism. The latency refers to the total processing time requirement of the task initiator. The operation list and description refer to the sequence of operations and the parameters of each operation that the industrial terminal needs to handle when processing the computing task. If necessary, the industrial terminal needs to negotiate with the application-layer deterministic middleware device in advance to determine the supported operation space and parameters. The industrial terminal configuration data format also includes other content, which is not specifically limited here.

[0080] Table 6 Industrial terminal configuration data format

[0081] Task No. Task Type Latency Operation list and description ……

[0082] It should be noted that in this interface protocol, the functions of the length and check fields are the same as those of the fields with the same name in other protocols and are not described here.

[0083] In this embodiment of the present invention, payloads are used to synchronize the deterministic requirements or status of applications or tasks, and can be used for task registration, system analysis, resource decision-making, and device configuration updates. First, they describe the abstraction of the application, including but not limited to the application name, deterministic task number, application and task type. Second, they describe the application-layer deterministic requirements, including but not limited to control chain latency, control chain jitter, application bandwidth, security level, reliability, and service time.

[0084] The embodiments of the present invention realize control signaling transmission, information collection, event filtering, and configuration conversion between network edge cloud devices and the server, reducing the difficulty of collaborative control of multiple applications. Network administrators do not need to directly deal with the applications in the devices, but instead call the applications and tasks on each device through the application collaboration middleware, thereby realizing a deterministic closed loop of complex control of multiple services at the application layer.

[0085] Figure 2 This is an embodiment of the method process of the present invention used on the device side.

[0086] An application monitoring and collaboration method, used for a deterministic network device, specifically includes the following steps 201 to 203:

[0087] Step 201: Obtain device status and application status through the operating system, and obtain detailed application information through the application interface.

[0088] It should be noted that the detailed information of the application at least includes application layer deterministic events and application layer deterministic requirements.

[0089] In step 201, the deterministic network device side includes an application collaboration middleware agent device, on which device and application information can be obtained through the operating system. It can directly read general information such as CPU utilization, and can also capture application communication data and judge based on port number and protocol type.

[0090] On the application collaborative middleware agent device, detailed information of the application can be obtained through the application interface. On the one hand, some public information can be obtained through the interface or protocol defined in international and domestic standards. On the other hand, after the system opens the permission, it can call the private customized interface to obtain deterministic parameters and the current task queue status.

[0091] In step 201, the application layer deterministic agent collects applications and their real-time status and application layer deterministic requirements in a combination of active and passive methods.

[0092] Step 202: Encapsulate the application status and detailed information into a task data packet and send it.

[0093] In step 202, the application collaborative middleware agent device may encapsulate the task information and device information into a data packet and send it to the server.

[0094] The application collaborative middleware agent uses the TCP protocol server to send information or responses through the northbound interface. The specific format of the northbound interface includes deterministic service type, message type, deterministic service header, length, payload and checksum.

[0095] It should be noted that the specific format of the deterministic message carried by the northbound interface is the same as that of the deterministic message carried by the southbound interface, and only the specific content of the payload is different, as shown in Table 7. It should also be noted that the northbound interface may also contain other content, which is not specifically limited here.

[0096] Table 7 Specific format of deterministic messages carried by the northbound interface

[0097] Deterministic business Message Type Deterministic business head length load check

[0098] The deterministic business type is used to provide a coarse-grained classification of application tasks.

[0099] The message type is used to mark the field used for the sent data packet, including a 2-bit registration message, a 1-bit pre-operation message, a 1-bit demand message, a 2-bit data update, a 3-bit configuration update, a 1-bit heartbeat message and a 2-bit query message, as shown in Table 2.

[0100] The deterministic service header is a required header for each message and includes a task number, task name, timestamp, message sequence number, time characteristics, and bandwidth, as shown in Table 3.

[0101] The payload is data carried by application layer deterministic messages and is used to describe application status, network configuration, and events. In an embodiment of the present invention, the payload is an application layer deterministic northbound payload, which includes: application request mode, real-time data mode, and pre-operation reporting mode.

[0102] Specifically, the application request mode includes task registration request, deterministic demand, deterministic demand reporting and task closing request.

[0103] The data format corresponding to the task registration request includes a task number, an operation number, a determinism requirement, and a checksum, as shown in Table 8. The task number refers to the unique number assigned to a specific service when the application registers with the application-layer deterministic middleware device. The task type refers to the classification category proactively provided by the application from the perspective of application-layer determinism. The operation number refers to the sequence number of the registration request, which can be provided in the form of a timestamp or serial number. The determinism requirement refers to the detailed application-layer determinism requirement of the application, as shown in Table 9.

[0104] It should be noted that the data format in Table 8 may also include other content, which is not particularly limited here.

[0105] Table 8 Data format corresponding to task registration request

[0106] Task No. Operation number Deterministic requirements check

[0107] The data format corresponding to the deterministic demand includes service level, latency, jitter, bandwidth, load and task type in order from front to back, as shown in Table 9. Among them, service level refers to the service level number identified by a numerical value, which can represent what kind of priority and resources the application wants to obtain. Latency refers to the requirement of the task initiator for the total processing time, that is, the maximum difference between the end time and the start time set by the application layer deterministic middleware for the control chain closed loop of the business. Jitter refers to the absolute value of the change in the forwarding delay of two consecutive data packets of the same data stream. Bandwidth refers to the forwarding bandwidth of the network, load refers to the processing throughput of edge computing and cloud, and task type refers to the classification category actively given by the application from the perspective of application layer determinism. It should be noted that the data format corresponding to the deterministic demand request also contains other content, which is not specifically limited here.

[0108] Table 9 Data format corresponding to deterministic demand request

[0109] Service Level Latency Jitter bandwidth load Task Type ……

[0110] The data format corresponding to the deterministic demand report includes, in descending order, the task number, the operation number, and the deterministic demand, as shown in Table 10. The task number refers to the unique number assigned to a specific service when the application registers with the application layer deterministic middleware device; the operation number refers to the sequence number of the registration request, i.e., the label of the report message; and the deterministic demand refers to the entire portion of Table 9. It should be noted that the data format corresponding to the deterministic demand report also includes other content, which is not specifically limited here.

[0111] Table 10 Data format corresponding to deterministic demand reporting

[0112] Task No. Operation number Deterministic requirements ……

[0113] The data format corresponding to the task close request includes, in descending order, a task number and an operation number, as shown in Table 11. The task number refers to the unique number assigned to a specific service when the application registers with the application-layer deterministic middleware device, and the operation number refers to the sequence number of the registration request, specifically the number of the task close request message in Table 11. It should be noted that the data format corresponding to the deterministic demand report also includes other content, which is not specifically limited here.

[0114] Table 11 Data format corresponding to task close request

[0115] Task No. Operation number (closed) ……

[0116] The real-time data mode includes application data update and device data update.

[0117] The data format corresponding to the application data update includes, in descending order, a task number, an event code, and event parameters, as shown in Table 12. The task number is the unique number assigned to a specific service when the application registers with the application-layer deterministic middleware device. The event code is the category number corresponding to the event that triggers the application to report the update. Event parameters are the information required to describe this type of event. It should be noted that the data format corresponding to the application data update may also include other content, which is not specifically limited here.

[0118] Table 12 Data format corresponding to application data update

[0119] Task No. Event Code Event Parameters ……

[0120] The data format corresponding to the device data update includes, in order from front to back, CPU utilization, memory utilization, bandwidth utilization, event code, and event description, as shown in Table 13. Among them, CPU utilization refers to the real-time occupancy of the CPU, memory utilization refers to the real-time occupancy of the memory, bandwidth utilization refers to the real-time occupancy of the device bandwidth, event code refers to the category number corresponding to the event that triggers the application to report the update, and event description refers to the cause of the event, specific status, monitoring indicators and other information. The specific expression method can be defined by the implementation unit, but can be expressed in standard protocols and description languages. It should be noted that the data format corresponding to the device data update also includes other content, which is not specifically limited here.

[0121] Table 13 Data format corresponding to device data update

[0122]

[0123] The data format corresponding to the pre-operation reporting mode includes, in order from front to back, the task number, relay sequence number, status code, timestamp and pre-operation operation description, as shown in Table 14. Among them, the task number refers to the unique number assigned to a specific service when the application is registered with the application layer deterministic middleware device, the relay sequence number refers to the record if there is a relay node or application, and the status code refers to the type of pre-operation information, which is used to express what stage the pre-operation has reached and what state it is in. The timestamp refers to the time when the message is sent, and the clock of the application service is required to be consistent with the application layer deterministic middleware. The pre-operation operation description refers to the terminal, edge computing or cloud computing operations to be performed by the simulation service. It should be noted that the data format corresponding to the pre-operation reporting mode also includes other content, which is not specifically limited here.

[0124] Table 14 Data format corresponding to pre-operation reporting mode

[0125] Task No. Relay number Status Code Timestamp Pre-run operation description ……

[0126] Step 203: Receive device control commands or device configuration parameters, and call a response configuration update interface to perform configuration update.

[0127] In steps 201 to 203 , step 201 and step 202 are executed sequentially, step 201 and step 203 are not executed sequentially, and step 202 and step 203 are not executed sequentially.

[0128] Figure 3 The present invention is a method flow embodiment for a system.

[0129] Deterministic service management is implemented for each task in industrial applications, requiring all devices involved to be monitorable, analyzable, and controllable. By gradually and dynamically adjusting the computing, storage, and communication resources of each device, the overall performance of the closed-loop control chain is guaranteed and optimized. This involves opening application and operating system application-layer interfaces, expanding deterministic specifications and operational parameters, and ensuring that the entire system operates in a deterministic manner.

[0130] An embodiment of the present invention provides an application collaboration method for an application collaboration system, specifically comprising the following steps 301 to 317:

[0131] Step 301: Configure initial parameters and report.

[0132] In step 301, after the application on the device initiates a new task, the middleware agent device encapsulates the information and uploads it to the middleware device. It should be noted that the middleware agent device in the present invention refers to the application collaboration middleware agent device, and the middleware device refers to the application collaboration middleware device.

[0133] In step 301, the device side configures initial parameters for the application task, including device information and task information, including but not limited to device manufacturer, device model, application name, application type, service number, specific computing task, deterministic indicators, etc.

[0134] Step 302: Add the task to the monitoring list.

[0135] In step 302, the middleware agent device adds the task configuration initial parameters sent by the device end to the monitoring list.

[0136] Step 303: Query application detailed information.

[0137] In step 303, the middleware agent device queries application detailed information.

[0138] Step 304: Query application type, service requirements, security information, and management information.

[0139] In step 304, the application task calls the middleware agent device to query application detailed information, including application type, service requirements, security information, and management information.

[0140] Step 305: Upload application and task information.

[0141] In step 305, the middleware proxy device encapsulates the retrieved application detailed information and device information into a data packet and uploads it to the middleware device.

[0142] Step 306: Create a new device association diagram and feedback relevant information.

[0143] In step 306, the middleware device receives the task data packet corresponding to the application, collects the task data, creates a new device association graph, that is, generates an application dependency graph, and feeds back relevant information to the middleware agent device. The relevant information fed back specifically includes: deterministic indicators of the application business on the device where the middleware agent is located, including but not limited to processing delay, processing delay jitter, throughput, and reliability.

[0144] Step 307: Transmit association graph feedback information.

[0145] In step 307 , the middleware agent device sends the association graph feedback information sent by the middleware device to the application task module on the device side.

[0146] Step 308: Read the business process pre-entered by the user.

[0147] In step 308, after receiving the association graph feedback information, the application task module reads the business process pre-input by the user.

[0148] Step 309: Upload the business process file.

[0149] In step 309, the application task module packages the business process into a file and uploads it.

[0150] Step 310: Deliver the business process file.

[0151] In step 310 , the middleware agent device delivers the business process file.

[0152] Step 311: Review the correctness of the task process.

[0153] In step 311, the application layer deterministic middleware device reviews the correctness of the task process, specifically including but not limited to whether there is a missing application node, missing application connection, or abnormal deterministic parameters.

[0154] Step 312: Broadcast the task configuration to all devices participating in the task.

[0155] In step 312 , when the task process is verified to be correct, the middleware device broadcasts the task configuration to all devices participating in the task.

[0156] Step 313: Transfer the configuration of the task.

[0157] In step 313, the middleware agent device is responsible for delivering the task configuration to each device.

[0158] Step 314: In response to step 313, detect the task configuration and provide feedback.

[0159] In step 314, the application task module detects the task configuration and provides feedback, the feedback content including: the current status of the device and application, the total resources and the occupied resources, etc.

[0160] Step 315: In response to step 313, the task configuration is detected and the remaining resources are reported.

[0161] In step 315, the terminal device that has not initiated the application layer deterministic task detects the task configuration and reports the remaining resources.

[0162] Step 316: In response to step 314 or 315, transmit task configuration feedback information and remaining resources.

[0163] In step 316 , the middleware agent device is responsible for transmitting the received task configuration feedback information and remaining resource feedback information.

[0164] Step 317: Start monitoring events of the task.

[0165] In step 317 , after receiving the corresponding feedback information, the middleware device starts to monitor the events of the task.

[0166] The embodiment of the present invention provides a task-oriented scheduling process. When an application initiates a new task, the agent encapsulates the information and uploads it to the middleware device. The middleware device reviews and creates an independent device association diagram, and sends the configuration of each device involved in the task to the middleware agent device of each device. The middleware agent device then calls the configuration update interface to update it. Subsequently, the middleware device will continue to monitor various events of the task and dynamically adjust it according to the policy running on the middleware device.

[0167] Figure 4 In an embodiment of the middleware device of the present invention, any application collaboration method for a server of the present invention is used.

[0168] An application monitoring and collaboration middleware device 1 includes: a monitoring and analysis module 11, a decision module 12, a network edge control module 13, and further includes: a message queue module 14 and a management UI module 15.

[0169] The monitoring and analysis module is configured to receive data packets corresponding to application tasks, collect task data, and generate or update an application dependency graph. The decision module is configured to make policy decisions based on the application dependency graph and task data, generate an overall deterministic policy, and split the overall deterministic policy into policies for each device. The edge control module is configured to translate the policies for each device into corresponding device control commands or device configuration parameters and issue the device control commands or device configuration parameters.

[0170] The message queue module is used to receive messages sent by the device end, sort them, and send the sorted results to the monitoring and analysis module.

[0171] The management UI module is used to perform visual management of application layer deterministic middleware devices, and comprehensively adopts parameter configuration files, graphical controls, command lines and other means to manage application layer deterministic middleware devices.

[0172] Specifically, the management UI module is used to receive and display an application dependency graph, an overall policy, a policy on each device, a device control command, or a device configuration parameter.

[0173] In an embodiment of the present invention, the message queue module realizes efficient processing of messages between network controllers, edge devices, industrial terminals and cloud computing, thereby ensuring that a large number of devices can be managed simultaneously in the factory intranet.

[0174] It should be noted that the specific methods for implementing the functions of the monitoring and analysis module, decision-making module, and network edge control module are as described in the various method embodiments of this application and will not be repeated here.

[0175] Figure 5For an embodiment of the middleware proxy device of the present invention, any device-side application collaboration method of the present invention may be used.

[0176] A middleware agent device 2 includes an application monitoring module 21 , a device monitoring module 22 and a configuration updating module 23 .

[0177] The device monitoring module is used to obtain the device status through the operating system; the application monitoring module is used to obtain the application status through the operating system and obtain detailed information of the application through the application interface; the configuration update module is used to encapsulate the device status, application status and detailed information into a data packet for transmission, receive device control commands or device configuration parameters, and call the response configuration update interface to perform configuration updates.

[0178] In an embodiment of the present invention, an application layer deterministic middleware agent device is deployed on a network edge cloud device and needs to perform differentiated parameter configuration in response to each device. Information such as application status, operating system resources, and device status is collected. In addition to basic information and real-time information such as application status, application type, and application port number, application information focuses on obtaining data related to service quality, determinism requirements, etc. When communicating with the middleware device, timestamps, tags, task numbers, parameter configurations, etc. are added according to the application layer determinism requirements. After receiving the device configuration, the interface of the application or operating system is called and executed.

[0179] In an embodiment of the present invention, the application layer deterministic middleware agent device also includes a second management UI module for visually managing the application layer deterministic middleware agent device, and comprehensively adopts parameter configuration files, graphical controls, command lines and other means to manage the application layer deterministic middleware agent device.

[0180] It should be noted that the specific methods for implementing the functions of the application monitoring module, device monitoring module and configuration update module are as described in the various method embodiments of this application and will not be repeated here.

[0181] Figure 6 This is a system embodiment of the present invention.

[0182] An application monitoring and collaboration system comprises the application monitoring and collaboration middleware device and the application monitoring and collaboration middleware agent device described in any one of the embodiments of the present invention.

[0183] An application monitoring and collaboration system includes an application monitoring and collaboration middleware device 1 and an application monitoring and collaboration middleware agent device 2.

[0184] In the embodiment of the present invention, the application collaboration middleware device and the application collaboration middleware agent device transmit application requirements, real-time data and configuration information through a specific interface protocol.

[0185] In the embodiment of the present invention, each module of the collaborative middleware device has the following functions:

[0186] The monitoring and analysis module can realize application dependency graph generation and maintenance, state synchronization, and data flow monitoring. Among them, application dependency graph generation and maintenance refers to saving the association between registered applications based on a directed acyclic graph, and dynamically updating according to the events uploaded by the agent; state synchronization refers to applications that have been successfully registered with the middleware, actively and regularly reporting their own information to the middleware to support the middleware in decision-making. Decision-making refers to formulating a global resource allocation plan based on the global configuration input by the user. Data flow monitoring refers to monitoring new application tasks sent by the middleware agent device.

[0187] The decision-making module can implement closed-loop scheduling, network policies, and application registration management. Closed-loop scheduling is based on a directed acyclic graph and the deterministic requirements of tasks. It calculates the performance indicators that each device needs to achieve, and is a process of splitting from the overall to the local.

[0188] The network edge control module can implement service strategies, protocol conversion and configuration updates; among them, service strategy refers to the method of scheduling all device resources in the application layer deterministic system based on certain algorithms, and protocol conversion is to convert the decisions of each device into executable configuration parameters, involving the unified management of heterogeneous device control interfaces.

[0189] The message queue module can realize data caching, hash table creation, protocol conversion and data distribution, etc.

[0190] In the embodiment of the present invention, each module of the collaborative middleware agent device has the following functions:

[0191] The configuration update module can realize information upload and configuration update.

[0192] The application monitoring module can realize the establishment of application feature library, feature extraction, application identification, application monitoring and communication monitoring; among them, the application feature library is a database that stores application information and features, feature extraction is a classifier that can identify applications and their services through multiple classification algorithms or matching, application identification is through protocols, representation information or active reporting by applications, application monitoring is to monitor the progress and new tasks of applications, and communication monitoring is to implement data flow monitoring by calling communication interfaces.

[0193] The device monitoring module can realize device monitoring and communication monitoring. Device monitoring monitors the device status changes on the device side, and communication monitoring monitors the device side data flow by calling the communication interface.

[0194] In an embodiment of the present invention, the application collaborative middleware agent device can obtain some public information through interfaces or protocols defined in international and domestic standards, for example, calling device CPU, process, storage and other information through the Linux interface; the application collaborative middleware agent device can also obtain deterministic parameters and current task queuing status through a private customized interface, for example, calling task queuing status through the edge computing platform interface.

[0195] In an embodiment of the present invention, the application collaboration middleware agent device can obtain device and application information through the operating system. It can directly read general information such as CPU utilization, and can also capture application communication data and make judgments based on port numbers and protocol types.

[0196] An embodiment of the present invention provides an application monitoring and collaboration system, which is implemented through a centralized control architecture and includes an application collaboration middleware device and an application collaboration middleware agent device. The application collaboration middleware device can be deployed on an independent device, or on a network controller, edge computing device, or cloud platform virtual machine, and can obtain a global view of all deterministic applications for real-time management and optimization. The application collaboration middleware agent device is deployed on each device where a deterministic application is located to perform monitoring and configuration. Through this system, the production control completed by multiple applications in collaboration can be characterized, and the performance of its control chain can be analyzed from the perspective of deterministic requirements. The deterministic requirements of the multi-application control chain can be met through network-edge-end-cloud control.

[0197] The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of the present application.

[0198] Furthermore, the present application also provides an electronic device (or computing device), comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in any embodiment of the present application when executing the computer program.

[0199] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0200] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0201] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0202] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0203] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-permanent storage in a computer-readable medium, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0204] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a..." does not preclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0205] The foregoing is merely an embodiment of the present invention and is not intended to limit the present invention. It will be apparent to those skilled in the art that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are intended to be included within the scope of the claims of the present invention.

Claims

1. An application monitoring and collaboration method for an application layer deterministic network middleware server, characterized in that: The following steps are involved: Obtaining a task data packet corresponding to an application task, collecting task data, and generating or updating an application dependency graph, wherein the task data packet includes at least: application status, device status, application layer deterministic events, and application layer deterministic requirements; application layer deterministic events refer to inputs driven by changes in the application layer determinism of a device; application layer deterministic requirements refer to a formal description of the indicators of deterministic services provided by the application to each device; Making policy decisions based on the application dependency graph and the task data packet, generating an overall deterministic policy, and splitting the overall deterministic policy into policies on each device; The policy on each device is translated into a corresponding device control command or device configuration parameter, and the device control command or device configuration parameter is issued.

2. The application monitoring and collaboration method according to claim 1, wherein: Also includes: The specific strategies used when making strategic decisions include at least one of the following: In response to the quantitative requirements of each application task, an algorithm-based decision is made to obtain the corresponding quantitative parameters; In response to the quantitative requirements of each application task, discrete decisions are made through classifiers; In response to the quantitative requirements of each application task, application configuration and application parameters are generated through manual review.

3. The application monitoring and collaboration method according to claim 1, wherein: Sending the device control command or device configuration parameter to each device via the southbound interface using the TCP protocol, wherein the specific format of the southbound interface includes a deterministic service type, a message type, a deterministic service header, a length, a payload, and a checksum; The deterministic business type is used to provide a coarse-grained classification of application tasks; The message type is a field used to mark the purpose of the data packet, including a 2-bit registration message, a 1-bit pre-operation message, a 1-bit demand message, a 2-bit data update, a 3-bit configuration update, a 1-bit heartbeat message and a 2-bit query message; The deterministic service header is present in each message and includes a task number, task name, timestamp, message sequence number, time characteristics, and bandwidth; The payload is data carried by application layer deterministic messages and is used to describe application status, network configuration, and events.

4. The application monitoring and collaboration method according to claim 1, wherein: It also includes: constructing, maintaining and destroying the application dependency graph.

5. The application monitoring and collaboration method according to claim 1, wherein: The step of generating or updating the application dependency graph further includes: An application communication relationship sequence is generated based on the collected task data, and the application dependency graph is formed using a network topology method.

6. The application monitoring and collaboration method according to claim 3, wherein: The payload is a deterministic southbound payload at the application layer, and its specific forms include: network controller configuration, edge configuration, cloud configuration, and industrial terminal configuration; The network controller configuration, the corresponding data format includes task number, task type, delay and jitter; The data format corresponding to the edge configuration and cloud configuration is the same, including task number, task type, latency, whether to preempt and computational complexity; The data format corresponding to the industrial terminal configuration includes task number, task type, delay, operation list and description.

7. An application monitoring and collaboration method for a deterministic network device, characterized in that: The following steps are involved: Obtain device and application status through the operating system, and obtain detailed application information through the application interface. The detailed application information includes at least application layer deterministic events and application layer deterministic requirements. Application layer deterministic events refer to inputs generated in response to changes in the device's application layer determinism. Application layer deterministic requirements refer to formal descriptions of indicators for the deterministic services provided by the application to each device. Encapsulate application status and detailed information into task data packets for sending; Receive device control commands or device configuration parameters, and call the response configuration update interface to update the configuration; the device control commands or device configuration parameters are to split the overall deterministic strategy into strategies on each device, and translate the strategies on each device into corresponding device control commands or device configuration parameters and issue them.

8. The application monitoring and collaboration method according to claim 7, wherein: Send information or responses via a northbound interface using the TCP protocol server, where the specific format of the northbound interface includes a deterministic service type, message type, deterministic service header, length, payload, and checksum; The deterministic business type is used to provide a coarse-grained classification of application tasks; The message type is a field used to mark the purpose of the data packet, including registration message, pre-operation message, demand message, data update, configuration update, heartbeat message and query message; The deterministic service header is a required header for each message, including task number, task name, timestamp, message sequence number, time characteristics and bandwidth; The payload is data carried by application layer deterministic messages and is used to describe application status, network configuration, and events.

9. The application monitoring and collaboration method according to claim 7, wherein: Obtain application status and details in a proactive and / or reactive manner.

10. The application monitoring and collaboration method according to claim 8, wherein: The payload is a deterministic northbound payload at the application layer, including: application request mode, real-time data mode, and pre-operation reporting mode; The application request mode includes a task registration request, deterministic requirements, deterministic requirements reporting, and a task shutdown request; the data format corresponding to the task registration request includes a task number, an operation number, a deterministic requirement, and a checksum; the data format corresponding to the deterministic requirement includes a service level, latency, jitter, bandwidth, load, and task type; the data format corresponding to the deterministic requirement reporting includes a task number, an operation number, and a deterministic requirement; the data format corresponding to the task shutdown request includes a task number and an operation number; The real-time data mode includes application data update and device data update; the data format corresponding to the application data update includes task number, event code, and event parameters; the data format corresponding to the device data update includes CPU utilization, memory utilization, bandwidth utilization, event code, and event description; The data format corresponding to the pre-operation reporting mode includes a task number, a relay sequence number, a status code, a timestamp and a pre-operation operation description.

11. An application monitoring and collaboration middleware device, using the application monitoring and collaboration method according to any one of claims 1 to 6, characterized in that: Includes: monitoring and analysis module, decision-making module, and network edge control module; The monitoring and analysis module is used to receive task data packets corresponding to application tasks, collect task data, and generate or update application dependency graphs; The decision module is used to make a policy decision based on the application dependency graph and task data, generate an overall deterministic policy, and split the overall deterministic policy into policies on each device; The network edge control module is used to translate the policy on each device into a corresponding device control command or device configuration parameter, and issue the device control command or device configuration parameter.

12. The application monitoring and collaboration middleware device according to claim 11, characterized in that: The monitoring and analysis module is also used to construct, maintain and destroy the application dependency graph.

13. An application monitoring and collaboration middleware agent device, using the application monitoring and collaboration method according to any one of claims 7 to 10, characterized in that: Contains: application monitoring module, device monitoring module and configuration update module; The device monitoring module is used to obtain the device status through the operating system; The application monitoring module is used to obtain application information through the operating system and obtain detailed application information through the application interface; The configuration update module is used to encapsulate the device status, application status and detailed information into a data packet for transmission, receive device control commands or device configuration parameters, and call a response configuration update interface to perform configuration update.

14. The application monitoring and collaboration middleware agent device according to claim 13, wherein: The device monitoring module is further used to obtain device status in an active and / or passive manner; the application monitoring module is further used to obtain detailed information about applications in an active and / or passive manner.

15. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

16. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method according to any one of claims 1 to 10 when executing the computer program.

17. An application monitoring and collaboration system, comprising the application monitoring and collaboration middleware device according to claim 11 and the application monitoring and collaboration middleware agent device according to claim 13.

Images