Middleware management and control method and system, nonvolatile storage medium and electronic equipment

Abstract

The invention discloses a middleware management and control method and system, a nonvolatile storage medium and electronic equipment. The method comprises the following steps: receiving a first management and control command sent by an operation management platform, and converting the first management and control command into a second management and control command in a preset format; the second management and control command is sent to a management and control plug-in in middleware through an asynchronous message channel, the middleware runs in gateway equipment, and the management and control plug-in is used for distributing the second management and control command to bottom-layer atomic power of the gateway equipment and obtaining an execution result of the bottom-layer atomic power on the second management and control command; a first message sent by the control plug-in through the asynchronous message channel is received, the first message is returned to the operation management platform, and the first message comprises the execution result. According to the method and the device, the technical problem of low middleware management and control efficiency caused by low compatibility and large resource occupation of a traditional middleware management and control technology is solved.

Description

Technical Field

[0001] The present application relates to the field of information and communication technology, and in particular, to a middleware management and control method, system, non-volatile storage medium and electronic device. Background Art

[0002] With the rapid development of technologies such as the Internet of Things and the Industrial Internet, ICT convergence gateways play a key role in connecting different networks, devices, and systems. Traditional middleware management solutions mainly rely on the operation, maintenance, and management functions provided by the middleware itself, where gateway devices are used as nodes for management and control, that is, real-time monitoring or alarming of middleware through gateway devices, which has the problems of low compatibility and high bandwidth occupied by data transmission.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a middleware management method, system, non-volatile storage medium and electronic device to at least solve the technical problem of low middleware management efficiency caused by low compatibility and high resource occupation of traditional middleware management technology.

[0005] According to one aspect of an embodiment of the present application, a middleware management and control method is provided, including: receiving a first management and control command sent by an operation and management platform, converting the first management and control command into a second management and control command in a preset format; sending the second management and control command to a management and control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in a gateway device, and the management and control plug-in is used to distribute the second management and control command to the underlying atomic capabilities of the gateway device, and obtain the execution result of the underlying atomic capabilities on the second management and control command; receiving a first message sent by the management and control plug-in through the asynchronous message channel, and returning the first message to the operation and management platform, wherein the first message includes the execution result.

[0006] Optionally, the control command type of the first control command includes a query command and a control command. When the control command type of the first control command is a query command, the execution result includes relevant information of the middleware corresponding to the query command, wherein the relevant information includes at least one of the following: middleware version, middleware running status.

[0007] Optionally, the operation management platform sends a first control command through an application programming interface; receives a first message sent asynchronously by the control plug-in, and returns the first message to the operation management platform, including: when the control command type of the first control command is a query command, synchronously returning the first message to the operation management platform through the application programming interface; when the control command type of the first control command is a control command, returning the first message to the operation management platform through an asynchronous message channel.

[0008] Optionally, the method also includes: receiving a second message sent by the management and control plug-in through an asynchronous message channel, wherein the second message includes information about the middleware that the management and control plug-in regularly collects according to a preset period, and the middleware information includes at least one of the following: middleware version, middleware status; encapsulating the second message; and returning the encapsulated second message to the operation management platform through the asynchronous message channel.

[0009] Optionally, encapsulating the second message includes: filtering the second message and converting the format of the second message.

[0010] Optionally, after receiving the first control command sent by the operation management platform, the method further includes: checking the authority of the first control command, and if the check passes, converting the first control command into a second control command in a preset format.

[0011] Optionally, the middleware includes a device adaptation interface, wherein the device adaptation interface is used to adapt underlying devices of various manufacturers according to a standardized protocol.

[0012] According to another aspect of an embodiment of the present application, a middleware management and control method is also provided, including: receiving a second management and control command sent by an asynchronous message channel of a gateway management platform; distributing the second management and control command to the underlying atomic capability of a gateway device for execution; obtaining the execution result of the underlying atomic capability on the second management and control command; and sending a first message to the gateway management platform through an asynchronous message channel, wherein the first message includes the execution result.

[0013] Optionally, the method further includes: regularly collecting middleware information according to a preset period, wherein the middleware information includes at least one of the following: middleware version, middleware status; and sending the middleware information to the gateway management platform via an asynchronous message channel.

[0014] According to another aspect of an embodiment of the present application, a middleware management and control system is also provided, including an operation management platform, a gateway management platform, and a gateway device, wherein: the operation management platform is used to send a first management and control command to the gateway management platform; the gateway management platform is used to convert the first management and control command into a second management and control command in a preset format; the second management and control command is sent to a management and control plug-in in the middleware through an asynchronous message channel; the gateway device runs the middleware, and the management and control plug-in of the middleware is used to distribute the second management and control command to the underlying atomic capabilities of the gateway device, and obtain the execution result of the underlying atomic capabilities on the second management and control command; the gateway management platform is also used to receive a first message sent by the management and control plug-in through the asynchronous message channel, and return the first message to the operation management platform, wherein the first message contains the execution result.

[0015] According to another aspect of an embodiment of the present application, a non-volatile storage medium is provided, in which a program is stored, wherein when the program is running, a device where the non-volatile storage medium is located is controlled to execute a middleware management and control method.

[0016] According to another aspect of an embodiment of the present application, there is further provided an electronic device, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the middleware management and control method is executed when the program is running.

[0017] According to another aspect of an embodiment of the present application, a computer program product is also provided, including a computer program, and when the computer program is executed by a processor, the middleware management and control method is implemented.

[0018] In an embodiment of the present application, a first control command sent by an operation management platform is received, and the first control command is converted into a second control command in a preset format; the second control command is sent to a control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in a gateway device, and the control plug-in is used to distribute the second control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second control command; a first message sent by the control plug-in through an asynchronous message channel is received, and the first message is returned to the operation management platform, wherein the first message includes a method for executing the result. By constructing a gateway middleware control architecture based on asynchronous message channel data transmission, the control command format is unified through the gateway management platform, thereby achieving the purpose of simplifying operations and improving management efficiency, thereby achieving the technical effects of improving compatibility, reducing latency, and reducing bandwidth occupancy, thereby solving the technical problem of low middleware control efficiency caused by low compatibility and high resource occupation of traditional middleware control technology. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 is a structural schematic diagram of a computer terminal provided according to an embodiment of the present application;

[0021] Figure 2 is a schematic diagram of a middleware management and control system provided according to an embodiment of the present application;

[0022] Figure 3 It is a schematic diagram of a middleware architecture design provided according to an embodiment of the present application;

[0023] Figure 4 It is a framework diagram of a middleware management and control system provided according to an embodiment of the present application;

[0024] Figure 5 It is a schematic diagram of an interaction process of a middleware management and control system provided according to an embodiment of the present application;

[0025] Figure 6 It is a flowchart of a middleware management and control method provided according to an embodiment of the present application;

[0026] Figure 7 is a schematic diagram of an operation management platform interface provided according to an embodiment of the present application;

[0027] Figure 8 It is a schematic diagram of a middleware upgrade process provided according to an embodiment of the present application;

[0028] Fig. 9 It is a schematic diagram of a middleware result provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0032] MQTT (Message Queuing Telemetry Transport): MQTT is a lightweight, publish / subscribe-based message transmission protocol designed for low-bandwidth, high-latency or unreliable networks. It is built on the TCP / IP protocol and is widely used in the Internet of Things (IoT), mobile Internet and other fields to achieve efficient communication between devices.

[0033] MQ (Message Queue): MQ message queue is a middleware technology used to store and forward messages in a distributed system. It is similar to a container for storing messages, which are transmitted between different software components, applications or systems. Message queue provides an asynchronous communication mechanism so that the sender and receiver do not need to be directly connected to each other or be in operation at the same time.

[0034] In the related technologies, there are many problems with the traditional gateway middleware management and control methods. The traditional gateway has fixed functions and is difficult to meet diversified business needs. It also has high learning costs, complex configuration and maintenance, high data transmission delays leading to resource occupation, compatibility issues between equipment from different manufacturers, different versions of protocol standards, and security issues in the middleware itself.

[0035] In order to solve the above problems, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0036] According to an embodiment of the present application, a method embodiment of a middleware management and control method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0037] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing the middleware management and control method is shown. Figure 1As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0038] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0039] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the middleware management and control method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned middleware management and control method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0040] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0041] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0042] The present application embodiment provides a middleware 04 management and control system, Figure 2 A schematic diagram of a middleware 04 control system is shown, Figure 2 As shown, the middleware 04 control system includes: an operation management platform 01, a gateway management platform 02, and a gateway device 03, wherein: the operation management platform 01 is used to send a first control command to the gateway management platform 02; the gateway management platform 02 is used to convert the first control command into a second control command in a preset format; the second control command is sent to the control plug-in 05 in the middleware 04 through an asynchronous message channel; the gateway device 03 runs the middleware 04, and the control plug-in 05 of the middleware 04 is used to distribute the second control command to the underlying atomic capability of the gateway device 03, and obtain the execution result of the underlying atomic capability on the second control command; the gateway management platform 02 is also used to receive the first message sent by the control plug-in 05 through the asynchronous message channel, and return the first message to the operation management platform 01, wherein the first message contains the execution result.

[0043] Optionally, Figure 3 The architecture design diagram of the middleware 04 is shown as follows: Figure 3As shown, the middleware 04 is solidified in the gateway device 03 as a container image and starts automatically when it is powered on. Subsequently, the gateway management platform 02 and the gateway device 03 establish a stable channel for communication through asynchronous messages. The M bus based on lightweight asynchronous messages includes the M1 platform southbound management and control interface (including computing power, fusion gateway, fttr (Fiber to The Room), terminal management); M2 computing power chip and application management interface; M3 manufacturer equipment adaptation layer interface; M4 master-slave gateway management interface; M5 intelligent terminal networking protocol interface; M6 container management, control plug-in 05, business plug-in management interface; M bus internal call function interface. By interacting with these interfaces, the middleware 04 includes LXC container management, FTTR control, middleware 04 upgrade and keep alive, equipment control, business plug-in interface development and adaptation, business plug-in upgrade and other capabilities.

[0044] Optionally, unified connection of downstream devices is achieved through the M3 interface unified protocol: gateway devices 03 from different manufacturers and their connected downstream devices (such as sensors, smart terminals, etc.) are unified into a standardized communication protocol to solve compatibility issues between devices.

[0045] Specifically, the M3 interface provides a unified access method for downstream devices (device bottom layer). It converts and adapts the communication protocols between the gateway and various devices, ensuring that all devices can exchange data with the gateway through a unified interface, thereby achieving interoperability between devices. This means that no matter what type of downstream device, as long as it complies with the protocol specifications of the M3 interface, it can be identified and managed by the gateway, promoting unified management of devices and centralized processing of data.

[0046] Through the unified protocol of the M3 interface, the entire system can achieve seamless connection and efficient management between different devices, promote device interoperability and system integration in the ICT converged gateway scenario, improve the stability and reliability of the overall network, and reduce operation and maintenance costs.

[0047] Optionally, Figure 4 A framework diagram of a middleware 04 control system is shown, such as Figure 4 As shown, the interaction is initiated by the platform side, and various operation management platforms 01 (including APP, self-service portal, etc.) interact with the gateway management platform 02 by calling the gateway management platform 02 API interface. The gateway management platform 02 translates the control commands of each operation management platform 01 into commands in MBUS format and sends them to the control plug-in 05 on the gateway side through the asynchronous message channel. The control plug-in 05 then distributes the commands to the underlying atomic capabilities for execution. After the execution is completed, the control plug-in 05 uploads the results to the gateway management platform 02 again through the asynchronous message channel. The gateway management platform 02 asynchronously feeds back to the operation platform through the MQ message channel.

[0048] Optionally, Figure 5 The interactive process of a middleware control system is shown as follows: Figure 5 As shown in the figure, the service components related to middleware control mainly include: the platform side, which is composed of the operation management platform and the gateway management platform; the gateway side, which is composed of MBUS plug-ins (including control plug-ins and LXC services / gateway firmware services). The interaction modes of the four parts are mainly divided into the following two types:

[0049] (1) Active reporting: Mainly used for the collection of periodic data of the gateway. Initiated by the management and control plug-in on the gateway side, the LXC / encapsulation interface is called to collect middleware-related information, including middleware version, running status, etc., and then forwarded to the gateway management platform through asynchronous messages. After message assembly and filtering, the gateway management platform reports to the operation platform through the asynchronous MQ channel.

[0050] (2) Passive commands: mainly used for the platform to issue control / query operations. Initiated by the platform, the gateway management platform API interface is called. The gateway management platform translates the command into MBUS and sends it to the management and control plug-in on the gateway side through the asynchronous message channel. The management and control plug-in then distributes the command to the underlying atomic capability for execution. After execution, the management and control plug-in uploads the result to the gateway management platform again through the asynchronous message channel. The gateway management platform feeds back the results to the operation platform in different ways according to the speed of command execution: for fast commands, synchronous response is directly made through the API; for slow commands, asynchronous feedback is made through the MQ message channel. Due to the influence of network jitter, the platform side implements the ability to receive messages asynchronously, and synchronous response is only used for acceleration.

[0051] Finally, the overall system is divided into the platform side and the gateway device side, which communicate through asynchronous message channels. The platform side uses the "gateway management platform" to connect with the gateway device in a unified manner, establish a stable message channel, and build business services such as APP, portal, and operation management platform based on the gateway management platform according to the system business functions.

[0052] In the above operating environment, the present application embodiment provides a middleware management and control method, such as Figure 6 As shown, the method comprises the following steps:

[0053] Step S602: Receive a first control command sent by the operation management platform, and convert the first control command into a second control command in a preset format.

[0054] Optionally, the operation management platform sends a first control command through an API interface, which contains specific operation instructions and parameters. After receiving this command, the gateway management platform converts it into a second control command of the MBUS protocol, that is, a command in a preset format that the gateway device can recognize and execute. Subsequently, an asynchronous message channel is implemented through the MQTT protocol. Through the asynchronous message channel, the gateway management platform sends the second control command to the control plug-in of the target gateway for actual operation. After the operation is completed, the result is fed back to the gateway management platform through the asynchronous message channel again, and then the gateway management platform converts the result into a format that the operation management platform can understand, completing the entire control process. Centrally manage various types of gateway devices through a unified platform, simplifying management operations and improving management efficiency: platform intensive management of various types of government and enterprise integration gateways, and centralized management through a unified platform. It can monitor the status of multiple types of gateways in real time, uniformly allocate resources, improve management efficiency, and ensure business continuity. Standardized adaptation of multi-vendor gateways breaks down manufacturer barriers, enabling gateways of different brands to work together in the same system. It reduces integration costs and complexity, and provides greater flexibility for enterprise equipment selection.

[0055] In the technical solution provided in step S602, after receiving the first control command sent by the operation management platform, the method also includes: checking the authority of the first control command, and if the check passes, converting the first control command into a second control command in a preset format.

[0056] Optionally, the operation management platform and the gateway management platform establish a multi-level security protection mechanism, including identity authentication, access control, and data encryption. This strengthens the protection of user privacy data, standardizes the data storage and transmission process, and ensures the security and reliability of the ICT convergence gateway middleware.

[0057] Optionally, before the operation management platform sends the first control command to the gateway management platform, the operation management platform will ensure the legitimacy and authority of the sender through an identity authentication process. This process involves digital certificates, dynamic passwords or role-based access control (RBAC) mechanisms to ensure that only verified users or systems can send the first control command, thereby effectively preventing unauthorized commands.

[0058] Optionally, after receiving the control command, the gateway management platform will further verify the legitimacy of the request according to the preset access control policy. The access control policy includes a whitelist mechanism that only allows specific IP addresses or device identifiers to communicate, as well as sophisticated permission management to ensure that each user or operation management platform can only access gateway devices and functions within its scope of authority, thereby reducing the risk of internal attacks and protecting the overall security of the system.

[0059] Optionally, at the data transmission level, in order to protect user privacy data and ensure the confidentiality of the communication content, security protocols such as SSL / TLS are used for encapsulation to ensure that even if the data is intercepted during transmission, it cannot be interpreted by a third party. This encryption mechanism not only enhances the security of data storage, but also standardizes the data transmission process, so that even if there are potential threats in the network environment, the communication between systems can maintain a high degree of reliability.

[0060] Step S604, sending the second control command to the control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in the gateway device, and the control plug-in is used to distribute the second control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second control command.

[0061] Optionally, the middleware includes a device adaptation interface, wherein the device adaptation interface is used to adapt underlying devices of various manufacturers according to a standardized protocol.

[0062] Optionally, the gateway management platform uses an asynchronous message channel to send the second control command to the middleware running in the gateway device. In this process, the asynchronous message mechanism plays a key role. Even in an environment with unstable network conditions or high latency, the transmission and reception of messages can still maintain high efficiency and timeliness, ensuring the accurate issuance of control commands. After receiving the second control command, the middleware distributes the command to the underlying atomic capabilities of the gateway device through its built-in control plug-in. This process involves specific operations such as querying device status, reading logs, and detecting system performance.

[0063] The control plug-in is not only responsible for command distribution, but also monitors the execution process of the underlying atomic capabilities for the second control command and collects all relevant execution results. These results include at least one of the following: real-time status of the device, error code, performance indicators, etc., which are essential for evaluating the operation status of the gateway and diagnosing potential problems. After collecting the execution results, the control plug-in feeds the results back to the gateway management platform through an asynchronous message channel, which is then sorted and analyzed by the gateway management platform and finally presented to the operation management platform.

[0064] Optionally, the middleware also integrates a device adapter interface, which can adapt to the underlying devices produced by different manufacturers based on standardized protocols. This means that no matter which manufacturer's device the gateway is connected to, the device adapter interface can ensure smooth communication between it and the gateway, greatly simplifying the device integration process and improving the comprehensiveness and efficiency of operation and maintenance.

[0065] In the technical solution provided in step S604, the control command type of the first control command includes a query command and a control command. When the control command type of the first control command is a query command, the execution result includes relevant information of the middleware corresponding to the query command, wherein the relevant information includes at least one of the following: middleware version, middleware running status.

[0066] Step S606, receiving a first message sent by the management and control plug-in through the asynchronous message channel, and returning the first message to the operation management platform, wherein the first message includes an execution result.

[0067] In the technical solution provided in step S606, the operation management platform sends a first control command through an application programming interface; receives a first message sent asynchronously by the control plug-in, and returns the first message to the operation management platform, including: when the control command type of the first control command is a query command, synchronously returning the first message to the operation management platform through the application programming interface; when the control command type of the first control command is a control command, returning the first message to the operation management platform through an asynchronous message channel.

[0068] Optionally, the gateway management platform can feed back the results to the operation platform in different ways according to the speed of command execution: for fast commands (generally query commands), it can directly respond synchronously through the API; for slow commands (generally control commands), it can asynchronously respond through the MQ message channel. Due to the influence of network jitter, the platform side implements the ability to receive messages asynchronously, and the synchronous response is only used for acceleration.

[0069] Optionally, when the operation management platform needs to send the first control command to the gateway device, whether it is a query command or a control command, it is sent through the application programming interface (API). This interface provides a standardized communication method, which makes the command sending process not only convenient but also ensures accurate data transmission.

[0070] In response to the query command, the first control command issued by the operation and management platform is mainly to obtain the current status or specific information of the gateway device, such as the version information and running status of the middleware. For such a query command, the control plug-in in the gateway device supports the immediate execution of the corresponding query operation and collects the required information. Since the query command usually does not require a long time to process, the control plug-in will asynchronously return the collected information, that is, the first message, to the gateway management platform, and the gateway management platform will synchronously return it to the operation and management platform through the API. This synchronous return mechanism ensures that the operation and management platform can obtain the query results in a timely manner, which is crucial for monitoring the real-time status of the gateway device and making quick decisions.

[0071] On the contrary, for control commands, the first control command may involve configuration modifications, business adjustments, or other time-consuming operations on the gateway device. In this case, after receiving the control command, the control plug-in will start to execute the corresponding operation, but because the execution of the control command may require a certain amount of processing time, the control plug-in will not return the result immediately. Instead, the first message of the execution status or result is sent back to the gateway management platform through the asynchronous message channel, and the gateway management platform then asynchronously feeds back the information to the operation management platform. The adoption of the asynchronous message mechanism avoids the impact of long waiting on system performance, while also ensuring the integrity of the execution of control commands and the timeliness of the results, and can ensure the stability of information transmission even when processing complex operations or encountering network delays.

[0072] Through the above process, this technical solution can not only flexibly adapt to the different characteristics of query commands and control commands, but also improve the interaction efficiency through a combination of synchronous and asynchronous methods, ensuring the immediacy and accuracy of information feedback, thereby effectively improving the overall operation and maintenance level and user experience of the ICT converged gateway system.

[0073] Optionally, the method also includes: receiving a second message sent by the management and control plug-in through an asynchronous message channel, wherein the second message includes information about the middleware that the management and control plug-in regularly collects according to a preset period, and the middleware information includes at least one of the following: middleware version, middleware status; encapsulating the second message; and returning the encapsulated second message to the operation management platform through the asynchronous message channel.

[0074] Optionally, encapsulating the second message includes: filtering the second message and converting the format of the second message.

[0075] Optionally, the management and control plug-in regularly collects relevant information from the middleware in the gateway device based on a preset period. This information may include key indicators such as the current version and operating status of the middleware, which are used to evaluate the health of the middleware and ensure its continued efficient operation.

[0076] The control plug-in packages the collected information into a second message and sends it to the gateway management platform through an asynchronous message channel. After receiving the second message, the gateway management platform performs encapsulation processing. This processing mainly includes two aspects: filtering the data in the second message to remove unnecessary information or perform data cleaning to ensure that the data transmitted to the operation management platform is accurate and relevant; at the same time, converting the format of the second message, adjusting the data structure and representation, and ensuring that the data can be correctly parsed and displayed by the operation management platform.

[0077] After the encapsulation, the second message is returned to the operation management platform through the asynchronous message channel again. After receiving and parsing this information, the operation management platform can monitor the version and status of the middleware of the gateway device in real time, and promptly discover potential abnormalities, such as outdated middleware version or abnormal middleware operation status, so that measures can be taken quickly, such as triggering the automatic update process or starting fault diagnosis, to ensure the stable operation of the ICT convergence gateway and its connected devices.

[0078] By regularly collecting and processing middleware information, this technical solution not only provides continuous monitoring capabilities for gateway devices, but also simplifies the complexity of data transmission, ensures the accuracy and timeliness of information, and provides a comprehensive view of the status of gateway devices for the operation management platform, thereby enhancing the operation and maintenance efficiency and reliability of the entire ICT converged gateway system.

[0079] Optionally, internal operators can perform middleware management and control operations through the operation management platform, and issue the first control command through the operation management platform. The middleware version is centrally managed by the ICT management platform (operation management platform). After the new version of the middleware is tested, it needs to be reported to the management platform for security scanning. After the scan passes, it will be put on the ICT management platform for use:

[0080] Only internal operators can upload middleware: The "Upload middleware" button is visible to internal operators. They can select the device manufacturer, device model, middleware name, middleware type, enter the version number, upload the image file and configuration file, and click the "Upload" button to upload the middleware.

[0081] Query: Enter part or all of the name of the middleware you want to find in the input box, or select the middleware type, device manufacturer, device model, version number, upload time, and uploader, and click the query button to query. After the query is successful, the query results will be displayed in the list below. Click the reset button to clear the text entered in the input box and display all middleware upload records in pages.

[0082] View: Click the View button in the Action column to view the middleware upload details.

[0083] Figure 7 A schematic diagram of an operation management platform interface is shown, such as Figure 7 As shown, there is a strict approval process for uploading middleware files, and only people with corresponding permissions can perform operations, including uploading, editing, testing, and reviewing.

[0084] The ICT management platform can remotely send middleware upgrade or rollback commands. The gateway device obtains the image and configuration files from the platform and upgrades or rolls back to the corresponding version. Figure 8 A middleware upgrade process is shown, such as Figure 8 As shown:

[0085] 1. The ICT management platform initiates a middleware upgrade request:

[0086] Internal operations staff initiate an application on the ICT management platform: click the "Initiate Application" button, select the operation type, which supports "Batch Upgrade" and "Specified Upgrade", select "Batch Upgrade", select the device manufacturer, device model, middleware name, current version, upgraded version, province, set the upgrade start time, fill in the application description, and click "Initiate Application". The application form will exist in the "Under Review" status and wait for approval.

[0087] The ICT management platform supports selecting "Specified Upgrade", selecting the device manufacturer, device model, middleware name, current version, upgraded version, filling in the MAC of the designated upgrade gateway, filling in the application description, and clicking "Initiate Application". The application form will exist in the "Under Review" status and wait for approval.

[0088] The ICT management platform also supports operation and management personnel to click the "View" button in the "Operation" column to view the version upgrade details; click the "Upgrade Result" button in the "Operation" column to view the version upgrade results. It supports entering the gateway MAC, selecting the upgrade result, and filtering the upgrade results. Fig. 9 A schematic diagram showing an upgrade result.

[0089] 2. The gateway management platform receives the first control command sent by the operation management platform, and converts the first control command into a second control command in a preset format, which is used to query the gateway device middleware information, obtain the gateway device middleware version, determine whether it is an initial upgrade or a subsequent upgrade, query the middleware configuration file, and instruct the gateway device to download the middleware image and upgrade.

[0090] 3. After receiving the second control command, the management and control plug-in of the gateway device downloads the image file and upgrades it, obtains the execution result of the middleware, and asynchronously pushes the upgrade failure result to the gateway management platform if the upgrade fails. If the upgrade is successful, delete the old configuration file and asynchronously push the upgrade success result to the gateway management platform.

[0091] 4. The gateway management platform receives the first message (execution result) and returns the first message to the operation management platform through the asynchronous message channel for the operation management personnel to view.

[0092] The above upgrade includes loading extended business plug-ins, which enables flexible loading of business plug-ins on the gateway side on demand, and can be flexibly adjusted according to different business scenarios of government and enterprises. For example, in emergency command scenarios, video conferencing plug-ins can be quickly loaded to meet real-time communication needs, improving resource utilization and system adaptability.

[0093] Through the above steps, a multifunctional gateway middleware management and control method based on lightweight asynchronous messages can be realized. With the gateway middleware as the core and the asynchronous message protocol stack, the gateway side service plug-in can be loaded flexibly on demand, the platform intensive management and control of various types of government-enterprise integration gateways can be realized, the standardized adaptation of gateways from multiple manufacturers can be realized, and the downstream devices can be uniformly connected. The simple and open intelligent management capability of the government-enterprise integration gateway can be constructed to support the centralized management and control of equipment and business mutual intelligence in the ICT network of small and medium-sized enterprises. It has powerful data processing capabilities and can efficiently integrate various types of data to provide a stable data transmission foundation for the entire system. Its openness facilitates interaction with other systems and creates conditions for realizing rich functions. Through the data regularly reported by the management plug-in, data analysis is performed to realize automatic optimization and fault warning, which comprehensively improves the management level and service quality of the gateway. The use of the asynchronous message protocol stack is an important measure for the application. The lightweight characteristics of asynchronous messages enable it to perform well in resource-constrained environments and ensure efficient communication between the gateway and the device. The downstream devices are uniformly connected, and both sensors and smart terminals can be seamlessly connected to the gateway. The centralized management of equipment and the unified processing of data are realized, which improves the integrity and reliability of the system. Finally, the simple and open intelligent management capability of the government-enterprise integration gateway is constructed. The simple operation interface makes it easy for managers to get started, and the open architecture facilitates integration with external systems. Specifically, the method embodiment of the present application has the following advantages:

[0094] (1) Breaking network boundaries and achieving seamless integration of various networks. Unifying protocol conversion, eliminating device communication barriers, and achieving linkage control between devices, greatly improving device compatibility and system integration, and promoting efficient and coordinated operation of the overall system.

[0095] (2) A common data exchange platform (i.e., gateway management platform) is built between different systems and applications to integrate and optimize the business links in different systems and achieve seamless integration of cross-system business processes.

[0096] (3) By loading business plug-ins on demand, the ICT convergence gateway can quickly adapt to the changing needs of different users and business scenarios, greatly reducing the time and cost of business adjustments.

[0097] (4) Establish a multi-level security protection mechanism, including identity authentication, access control, data encryption, etc. Strengthen the protection of user privacy data, standardize the data storage and transmission process, and ensure the security and reliability of ICT convergence gateway middleware.

[0098] An embodiment of the present application provides a non-volatile storage medium, in which a program is stored, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the following middleware control method: receiving a first control command sent by an operation management platform, and converting the first control command into a second control command in a preset format; sending the second control command to a control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in a gateway device, and the control plug-in is used to distribute the second control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second control command; receiving a first message sent by the control plug-in through the asynchronous message channel, and returning the first message to the operation management platform, wherein the first message includes the execution result.

[0099] An embodiment of the present application provides an electronic device, comprising: a memory and a processor, the processor being used to run a program stored in the memory, wherein the following middleware control method is executed when the program is running: receiving a first control command sent by an operation management platform, and converting the first control command into a second control command in a preset format; sending the second control command to a control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in a gateway device, and the control plug-in is used to distribute the second control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second control command; receiving a first message sent by the control plug-in through the asynchronous message channel, and returning the first message to the operation management platform, wherein the first message includes the execution result.

[0100] An embodiment of the present application provides a computer program product, including a computer program, which implements the following middleware management and control method when executed by a processor: receiving a first management and control command sent by an operation and management platform, and converting the first management and control command into a second management and control command in a preset format; sending the second management and control command to a management and control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in a gateway device, and the management and control plug-in is used to distribute the second management and control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second management and control command; receiving a first message sent by the management and control plug-in through the asynchronous message channel, and returning the first message to the operation and management platform, wherein the first message contains the execution result.

[0101] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0102] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0103] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0104] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0105] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0106] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A middleware management and control method, characterized in that: include: Receiving a first control command sent by the operation management platform, and converting the first control command into a second control command in a preset format; Sending the second control command to a control plug-in in the middleware through an asynchronous message channel, wherein the middleware runs in a gateway device, and the control plug-in is used to distribute the second control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second control command; Receive a first message sent by the management and control plug-in through an asynchronous message channel, and return the first message to the operation management platform, wherein the first message includes the execution result.

2. The middleware management and control method according to claim 1, characterized in that: The control command types of the first control command include query commands and control commands. When the control command type of the first control command is a query command, the execution result includes relevant information of the middleware corresponding to the query command, wherein the relevant information includes at least one of the following: middleware version, middleware running status.

3. The middleware management and control method according to claim 2, characterized in that: The operation management platform sends a first control command through an application programming interface; Receiving the first message sent asynchronously by the management and control plug-in, and returning the first message to the operation management platform includes: In a case where the control command type of the first control command is a query command, synchronously returning the first message to the operation management platform through an application programming interface; In the case where the control command type of the first control command is a control command, the first message is returned to the operation management platform through an asynchronous message channel.

4. The middleware management and control method according to claim 1, characterized in that: The method further comprises: Receiving a second message sent by the control plug-in through an asynchronous message channel, wherein the second message includes information about the middleware that the control plug-in regularly collects according to a preset period, and the information about the middleware includes at least one of the following: a middleware version and a middleware status; encapsulating the second message; The second message after encapsulation is returned to the operation management platform through an asynchronous message channel.

5. The middleware management and control method according to claim 4, characterized in that: The encapsulation processing of the second message includes: filtering the second message and converting the format of the second message.

6. The middleware management and control method according to claim 1, characterized in that: After receiving the first control command sent by the operation management platform, the method further includes: checking the authority of the first control command, and if the check passes, converting the first control command into a second control command in a preset format.

7. The middleware management and control method according to claim 1, characterized in that: The middleware includes a device adaptation interface, wherein the device adaptation interface is used to adapt the underlying devices of various manufacturers according to a standardized protocol.

8. A middleware management and control method, characterized in that: include: Receiving a second control command sent by an asynchronous message channel of the gateway management platform; Distributing the second control command to the underlying atomic capability of the gateway device for execution; Obtaining the execution result of the underlying atomic capability on the second control command; A first message is sent to the gateway management platform through an asynchronous message channel, wherein the first message includes the execution result.

9. The middleware management and control method according to claim 8, characterized in that: The method further comprises: Regularly collect information about the middleware according to a preset period, wherein the information about the middleware includes at least one of the following: a middleware version, a middleware status; The information of the middleware is sent to the gateway management platform through an asynchronous message channel.

10. A middleware management and control system, characterized in that: Including operation management platform, gateway management platform, gateway equipment, including: The operation management platform is used to send a first control command to the gateway management platform; The gateway management platform is used to convert the first control command into a second control command in a preset format; and send the second control command to the control plug-in in the middleware through an asynchronous message channel; The gateway device runs a middleware, and the control plug-in of the middleware is used to distribute the second control command to the underlying atomic capability of the gateway device, and obtain the execution result of the underlying atomic capability on the second control command; The gateway management platform is also used to receive a first message sent by the management and control plug-in through an asynchronous message channel, and return the first message to the operation management platform, wherein the first message includes the execution result.

11. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the middleware management and control method described in any one of claims 1 to 7 or any one of claims 8 to 9.

12. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program, when running, executes the middleware management and control method described in any one of claims 1 to 7 or any one of claims 8 to 9.

13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the middleware management and control method described in any one of claims 1 to 7 or any one of claims 8 to 9 is implemented.

Images