Gateway data processing method and system and electronic equipment

Abstract

The invention discloses a gateway data processing method and system and electronic equipment. The method comprises the steps that gateway data of an edge gateway are acquired, edge middleware is deployed in the edge gateway, and the edge middleware is used for supporting data transmission between the edge gateway and a cloud gateway management platform; and uploading the gateway data to a cloud gateway management platform through a message queue telemetering transmission protocol in the edge middleware, and processing the gateway data through the cloud gateway management platform. The technical problems of high network operation and maintenance difficulty, insufficient edge computing power and poor application deployment convenience of small and micro enterprises in related technologies are solved.

Description

Technical Field

[0001] The present application relates to the field of edge computing, and specifically, to a gateway data processing method, system and electronic device. Background Art

[0002] With the deepening of digital transformation, small and micro enterprises have an increasing demand for network infrastructure, especially in terms of network stability and bandwidth, and need to cope with the challenges of simultaneous access of multiple internal devices and efficient data transmission. Network solutions in related technologies often fail to meet such needs, especially in terms of signal coverage and network operation and maintenance. Small and micro enterprises usually lack professional IT teams and find it difficult to effectively manage and maintain complex network equipment, which limits their progress in digital upgrades.

[0003] The emergence of FTTR-B (Business Fiber to The Room) technology precisely focuses on the pain points of small and micro enterprises. It extends PON (Passive Optical Network) technology to every corner of the enterprise and uses the high bandwidth and low latency characteristics of optical fiber to provide small and micro enterprises with gigabit network coverage. However, with the surge in demand for AI intelligence and edge computing, simply providing high-speed networks is no longer enough to meet the expectations of small and micro enterprises for comprehensive computing services. Small and micro enterprises still face problems such as complex network operation and maintenance, insufficient computing power, and difficulty in deploying AI applications.

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

[0005] The embodiments of the present application provide a gateway data processing method, system and electronic device to at least solve the technical problems of high difficulty in network operation and maintenance, insufficient edge computing power and poor convenience in application deployment for small and micro enterprises in related technologies.

[0006] According to one aspect of an embodiment of the present application, a method for processing gateway data is provided, which is applied to an edge gateway, including: obtaining gateway data of the edge gateway, wherein the edge gateway is deployed with edge middleware, and the edge middleware is used to support data transmission between the edge gateway and a cloud gateway management platform; uploading the gateway data to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and processing the gateway data through the cloud gateway management platform.

[0007] Optionally, the edge gateway includes a gateway mainboard and a computing board. The edge middleware is deployed on the computing board. The gateway mainboard and the computing board transmit data with the cloud gateway management platform through the edge middleware. The computing board is used to enhance the edge computing capabilities of the edge gateway.

[0008] Optionally, the edge middleware includes a device service layer, a core service layer, a support service layer and an application service layer, wherein the device service layer is used to communicate with the edge gateway through a network interface, the core service layer is used to process gateway data and control commands of the cloud gateway management platform, the support service layer is used to monitor the operating status of the edge gateway, and the application service layer is used to configure applications selected by the cloud gateway management platform.

[0009] Optionally, the method also includes: receiving a control command from a cloud gateway management platform; sending the control command to a proxy component in an edge gateway through a control module in the edge middleware, wherein the control module is located in a core service layer of the edge middleware; processing the control command through the proxy component to obtain a processing result.

[0010] Optionally, executing the control command through the proxy component includes: converting the control command from an initial format to a target format, and processing the control command after the format conversion through the proxy component, wherein the target format is used to adapt to the application deployment environment on the computing board of the edge gateway.

[0011] Optionally, the topics subscribed to by the message queue telemetry transmission protocol include a first topic, a second topic and a third topic, wherein the first topic is used to upload the gateway data of the edge gateway to the edge middleware and the cloud gateway management platform, the second topic is used to send the control commands of the cloud gateway management platform to the edge gateway, and the third topic is used to return the processing results of the control commands by the edge gateway to the edge middleware and the cloud gateway management platform.

[0012] According to another aspect of an embodiment of the present application, a method for processing gateway data is provided, which is applied to a cloud gateway management platform, including: obtaining a control command from the cloud gateway management platform; sending the control command to an edge gateway through a message queue telemetry transmission protocol in an edge middleware, and processing the control command through the edge gateway to obtain a processing result, wherein the edge middleware is deployed in the edge gateway, and the edge middleware is used to support data transmission between the cloud gateway management platform and the edge gateway; and returning the processing result to the cloud gateway management platform.

[0013] According to another aspect of an embodiment of the present application, a gateway data processing system is provided, including an edge gateway and a cloud gateway management platform, wherein the edge gateway deploys edge middleware, uploads gateway data of the edge gateway to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and processes the gateway data through the cloud gateway management platform, wherein the edge middleware is used to support data transmission between the edge gateway and the cloud gateway management platform; the cloud gateway management platform is used to send control commands of the cloud gateway management platform to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and processes the control commands through the edge gateway to obtain processing results; and returns the processing results to the cloud gateway management platform.

[0014] According to another aspect of the embodiment of the present application, there is also provided an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the above-mentioned gateway data processing method.

[0015] According to another aspect of the embodiments of the present application, a non-volatile storage medium is further provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned gateway data processing method by running the computer program.

[0016] According to another aspect of the embodiments of the present application, a computer program product is also provided, including computer instructions, which implement the above-mentioned gateway data processing method when executed by a processor.

[0017] In an embodiment of the present application, a gateway data processing system includes an edge gateway and a cloud gateway management platform, wherein the edge gateway deploys edge middleware, uploads the gateway data of the edge gateway to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and processes the gateway data through the cloud gateway management platform, wherein the edge middleware is used to support data transmission between the edge gateway and the cloud gateway management platform; the cloud gateway management platform is used to send the control command of the cloud gateway management platform to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and processes the control command through the edge gateway to obtain the processing result; the processing result is returned to the cloud gateway management platform, thereby achieving the purpose of ensuring efficient data transmission and remote gateway management between the edge and the cloud through the edge middleware, thereby achieving the technical effect of enhancing the edge computing power and intelligent operation and maintenance of small and micro enterprises in digital transformation, and then solving the technical problems of high network operation and maintenance difficulty, insufficient edge computing power and poor application deployment convenience of small and micro enterprises in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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:

[0019] Figure 1 is a hardware structure diagram of a computer terminal for implementing a method for processing gateway data according to an embodiment of the present application;

[0020] Figure 2 is a flow chart of a method for processing gateway data according to an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of the architecture of an edge gateway according to an embodiment of the present application;

[0022] Figure 4 is a schematic diagram of an architecture of edge middleware according to an embodiment of the present application;

[0023] Figure 5 It is a schematic diagram of a communication process based on the MQTT protocol according to an embodiment of the present application;

[0024] Figure 6 is another schematic diagram of a communication process based on the MQTT protocol according to an embodiment of the present application;

[0025] Figure 7 This is another communication process diagram based on the MQTT protocol provided in an embodiment of the present application;

[0026] Figure 8 is a flowchart of another method for processing gateway data according to an embodiment of the present application;

[0027] Fig. 9 is a structural diagram of a gateway data processing device according to an embodiment of the present application;

[0028] Fig.10 It is a structural diagram of another gateway data processing device according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution 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 the present 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] First, some nouns or terms that appear in the process of explaining the embodiments of the present application are subject to the following explanations:

[0032] FTTR-B (Business Fiber to The Room): A network technology solution that aims to directly connect to each room within the enterprise through optical fiber to achieve gigabit network coverage to meet the enterprise's needs for high-speed and stable networks.

[0033] PON (Passive Optical Network): A fiber-optic access technology that uses optical cables and passive optical splitters to provide broadband connections from service providers to end users without electronic amplification or regeneration.

[0034] MQTT (Message Queuing Telemetry Transport): A lightweight publish / subscribe messaging protocol, mainly used in low-bandwidth, high-latency or unreliable networks, and suitable for the Internet of Things and edge computing scenarios.

[0035] JSON (JavaScript Object Notation): A lightweight data exchange format that is easy for people to read and write, and easy for machines to parse and generate. It is often used to transmit data in Web applications.

[0036] QoS (Quality of Service): It is used to provide data packet processing with different priorities, ensuring that key applications or services obtain the required bandwidth and other resources in shared network resources, reducing delays and packet loss rates.

[0037] VPN (Virtual Private Network): Used to establish a secure, dedicated network connection on a public network, providing remote access and data protection through data encryption and address translation.

[0038] EdgeX Foundry: An edge computing open source project hosted by the Linux Foundation, which aims to provide a universal and scalable edge computing platform to support interoperability between IoT devices and edge applications and simplify the development and deployment of edge computing.

[0039] K3S: A lightweight Kubernetes distribution developed by Rancher Labs, specifically for edge computing scenarios, providing a lightweight, efficient, and easy-to-deploy and manage Kubernetes environment.

[0040] Helm: A Kubernetes application deployment and management tool, similar to a Linux package manager, used to define, install, and manage Kubernetes applications.

[0041] Helm-Controller: Helm controller, a management component, is used to simplify the deployment and management of HelmChart in the K3S environment, automating the installation, update, and uninstallation of applications.

[0042] In order to solve the problem of insufficient edge gateway data processing capability in the related art, the present application embodiment provides a method for processing gateway data. The method can be run on Figure 1 In the computer terminal shown, the computer terminal is described below.

[0043] The gateway data processing method embodiment provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 FIG. 1 shows a hardware structure block diagram of a computer terminal for implementing a method for processing gateway data. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor 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 module 106 for communication functions connected via a wired and / or wireless network. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. Those skilled in the art can understand that Figure 1The 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 shown.

[0044] It should be noted that the one or more processors 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).

[0045] 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 method for processing gateway data in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizing the above-mentioned method for processing gateway data. 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, 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.

[0046] The transmission module 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 module 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 module 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0047] 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 .

[0048] It should be noted that, in some optional embodiments, the above Figure 1The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0049] In the above operating environment, an embodiment of the present application provides an embodiment of a method for processing gateway data. 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 the 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.

[0050] Figure 2 is a flow chart of a method for processing gateway data according to an embodiment of the present application, such as Figure 2 As shown, the method is applied to an edge gateway and includes the following steps:

[0051] Step S202, obtaining gateway data of the edge gateway, wherein the edge gateway deploys edge middleware, and the edge middleware is used to support data transmission between the edge gateway and the cloud gateway management platform.

[0052] In the above step S202, the data collection function of the edge gateway (such as the FTTR-B high-order converged gateway) is mainly supported by the EdgeX Foundry framework deployed on the edge gateway. EdgeX Foundry, as an edge middleware, is deployed on the computing board of the edge gateway and includes multiple service layers, among which the device service layer is responsible for collecting data from edge devices, sensors or actuators.

[0053] In this application, the FTTR-B high-order fusion gateway itself is regarded as an important "edge device". Its device service layer will collect relevant gateway mainboard data and computing board data regularly (such as every 60 seconds) or according to specific events (such as status changes). The gateway mainboard data may include gateway MAC address, gateway SN, gateway IP, gateway performance data, gateway WAN information, gateway online status, slave gateway information, Wi-Fi list and other data; the computing board data may include computing board performance data, computing board application list and other data.

[0054] Step S204, uploading the gateway data to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and processing the gateway data through the cloud gateway management platform.

[0055] In the above step S204, after the gateway data is collected, the MessageBus in the core service layer of EdgeX Foundry will transfer the gateway data from the device service layer to the core data service for storage and preliminary processing. For transmission to the cloud gateway management platform, the device service layer of EdgeX Foundry will use the MQTT protocol, which is a lightweight message queue telemetry transmission protocol suitable for data transmission of IoT devices, which can effectively save network resources and support disconnection reconnection and message persistence. Specifically:

[0056] The FTTR-B high-order fusion gateway encapsulates the collected gateway data into MQTT messages and publishes them to a predefined Topic. For example, gateway performance data may be published to the / gateway / report / m1 Topic, while the computing board data may be published to the / gateway / report / m2 Topic. At the same time, the cloud gateway management platform subscribes to the above Topics and receives the data uploaded by the FTTR-B high-order fusion gateway. Once the data arrives, the platform will perform a series of processing, including but not limited to:

[0057] Data parsing: Parse the payload of the MQTT message, which is usually in JSON format, and extract specific data fields such as id, method, timestamp, properties, code, errorMsg, result, etc.

[0058] Status monitoring and display: The extracted data is used to monitor the status of the FTTR-B high-order converged gateway and its slave gateways, including online status, performance data, network topology, etc., and displayed in real time in the management interface.

[0059] Remote maintenance and troubleshooting: Based on gateway data, the cloud management platform can perform remote maintenance operations, such as one-click detection and segmented speed measurement, to promptly identify and handle network problems.

[0060] Application management: manage applications deployed on the FTTR-B advanced converged gateway, including application download and deployment in the application market, remote configuration and update of applications, etc.

[0061] Through the above steps S202 to S204, the purpose of ensuring efficient data transmission and remote gateway management between the edge and the cloud through edge middleware is achieved, thereby achieving the technical effect of enhancing the edge computing power and intelligent operation and maintenance of small and micro enterprises in digital transformation, thereby solving the technical problems of high difficulty in network operation and maintenance, insufficient edge computing power and poor convenience of application deployment for small and micro enterprises in related technologies. The following is a detailed description.

[0062] Optionally, the edge gateway includes a gateway mainboard and a computing board. The edge middleware is deployed on the computing board. The gateway mainboard and the computing board transmit data with the cloud gateway management platform through the edge middleware. The computing board is used to enhance the edge computing capabilities of the edge gateway.

[0063] In the embodiment of the present application, the FTTR-B high-order fusion gateway enhances the computing power of the basic FTTR-B gateway device, and the whole includes two parts, the FTTR-B gateway mainboard and the X86 computing board, such as Figure 3 As shown: The architecture includes a 650W power supply, which supplies power to the X86 computing board and the FTTR-B gateway motherboard respectively; the X86 computing board is equipped with a 16-core CPU and 32GB memory, and is connected to the FTTR-B gateway motherboard through RJ45 1G and 2.5G network ports for network connection and remote management. The FTTR-B high-order converged gateway has 1 uplink optical port for easy access to optical fiber, 1 downlink optical port to connect to multiple slave gateways to achieve network coverage, 4 voice ports for easy telephone access, and two RJ45 1G network ports. The FTTR-B high-order converged gateway also provides other rich interfaces, including 1 DP, 2 HDMI, 1 COM, 6 USB 3.0 and additional RJ45 1G network ports. In terms of storage, it includes a 512GB M.2NVMe solid-state drive and an additional 512GB of NVMe storage expanded through 4 PCIe. In addition, the FTTR-B advanced converged gateway is also equipped with a PCIe x16 interface AI computing card to enhance computing power, and an 8TB HDD hard disk for large-capacity storage. The FTTR-B module contains an optical module, CPU, memory and motherboard, and interacts with the host through an RJ45 1G network port. The entire system is designed to provide high-performance network and computing support for small and micro enterprises.

[0064] It should be noted that the above-mentioned gateway motherboard and computing board both use the edge middleware (EdgeX Foundry) to communicate with the cloud gateway management platform for data transmission and control commands. Figure 3 As shown, interaction is carried out through the RJ45 1G and 2.5G network ports.

[0065] Optionally, the edge middleware includes a device service layer, a core service layer, a support service layer and an application service layer, wherein the device service layer is used to communicate with the edge gateway through a network interface, the core service layer is used to process gateway data and control commands of the cloud gateway management platform, the support service layer is used to monitor the operating status of the edge gateway, and the application service layer is used to configure applications selected by the cloud gateway management platform.

[0066] In the embodiment of the present application, the edge middleware (EdgeX Foundry) is composed of multiple microservices, including a device service layer (Device Services Layer), a core service layer (Core Services Layer), a supporting service layer (Supporting Services Layer) and an application service layer (Application Services Layer). Specifically:

[0067] The device service layer is used to provide support for multiple device communication protocols, such as MQTT, MODBUS, etc., to collect performance data and status information of the gateway mainboard and computing board, and format it into standardized JSON data for easy transmission and processing. The core service layer includes data storage (CORE DATA), command processing (COMMAND), metadata management (METADATA), and registration and configuration (REGISTRY&CONFIG). These services are responsible for storing data on the computing board, processing control commands from the cloud, managing and storing metadata of devices and services, and providing registration and configuration information for devices and services. The support service layer is used to provide functions such as rule engine, scheduling, alarm and notification, which further enhances the data processing and device management capabilities. The application service layer allows the deployment and operation of containerized applications, supports the lifecycle management of applications, and enables small and micro enterprises to easily deploy and run private applications or applications downloaded from the application market on the edge gateway.

[0068] Figure 4 is a schematic diagram of an edge middleware architecture according to an embodiment of the present application, such as Figure 4As shown: The "NORTHBOUND" INFRASTRUCTURE AND APPLICATIONS at the top are northbound infrastructure and applications, which refer to upper-layer applications and services that interact with EdgeXFoundry, such as the (cloud) gateway management platform. The loosely-coupled microservices framework in the middle framework is a loosely coupled microservices framework that allows each service to run and scale independently. Container Deployment is a container deployment, indicating that EdgeX Foundry's microservices can be deployed in containers for flexible deployment and management. Developer / Demo GUI is a graphical user interface provided for developers and demonstrations. Application Services Layer is the application service layer, in which CONFIGURABLE APPLICATION SERVICE is a configurable application service that allows users to customize applications according to their needs; APPLICATION SERVICE is an application service used to provide specific functions; SDK is a software development kit used to develop and integrate application services. The Supporting Services Layer is the supporting service layer, where RULES ENGINE is the rule engine used to define and execute business rules; SCHEDULING is the scheduling service used to manage and schedule tasks; ALERTS&NOTIFICATIONS is the alarm and notification service used to monitor and notify system status. The Core Services Layer is the core service layer, where CORE DATA is the core data service responsible for storing and retrieving device data; COMMAND is the command service used to send commands to devices; METADATA is the metadata service that stores description information about devices and services; REGISTRY&CONFIG is the registration and configuration service that manages the registration information of devices and services.Device Services Layer is the device service layer, where anycombination of standard or proprietary protocols via SDK is any combination of standard or proprietary protocols supported by SDK; for example, REST is an HTTP-based interface for device communication; OPC-UA is a communication protocol for industrial automation; MODBUS is a widely used serial communication protocol; BACNET is a protocol for building automation and control systems; ZIGBEE is a low-power wireless communication protocol; BLE is Bluetooth Low Energy, used for short-range wireless communication; MQTT is a message queue telemetry transmission, a lightweight message transmission protocol; SNMP is a simple network management protocol, used for network management; VIRTUAL is a virtual device service, used to simulate device behavior; +MORE indicates that other protocols are also supported. The "SOUTHBOUND" DEVICE, SENSORS AND ACTUATORS at the bottom is a southbound device, which refers to physical devices, sensors, and actuators connected to EdgeX Foundry, such as FTTR-B high-order converged gateways.

[0069] Optionally, the topics subscribed to by the message queue telemetry transmission protocol include a first topic, a second topic and a third topic, wherein the first topic is used to upload the gateway data of the edge gateway to the edge middleware and the cloud gateway management platform, the second topic is used to send the control commands of the cloud gateway management platform to the edge gateway, and the third topic is used to return the processing results of the control commands by the edge gateway to the edge middleware and the cloud gateway management platform.

[0070] In the embodiment of the present application, the Message Queue Telemetry Transport Protocol (MQTT) plays a key communication role in the FTTR-B high-order converged gateway management system. Through the subscription and publishing mechanism, it ensures efficient data transmission and control command processing between the edge gateway and the cloud gateway management platform. The following is a detailed description of the three topics subscribed by the MQTT protocol:

[0071] The first topic is the topic corresponding to the reported gateway data, which is usually defined as / gateway / report / $M, where $M is a variable, which can be m1 (representing the FTTR-B gateway motherboard) or m2 (representing the computing board). The gateway motherboard and computing board of the edge gateway regularly upload gateway data to the edge middleware and cloud gateway management platform through the first topic. These data may include device status, performance indicators, network information, Wi-Fi list, etc., and are reported regularly in a cycle of 60 seconds. Through this mechanism, the cloud management platform can monitor the status and performance of the edge gateway in real time, and provide data support for subsequent automated operation and maintenance and fault diagnosis.

[0072] The second topic is the topic corresponding to the control command, which is usually defined as / gateway / command / $M. Depending on the target component, $M can be m1 or m2. The cloud gateway management platform sends control commands to the edge gateway through the second topic. These commands can be operations such as creating Wi-Fi, configuring network parameters, obtaining device information, installing or updating applications. The control command is encapsulated in JSON format and contains all the information required to execute the instruction, such as command ID, method name, timestamp, attributes, etc. After receiving the command, the edge gateway will parse the command through the internal agent component (Agent) and perform the corresponding operation.

[0073] The third topic is the topic corresponding to the returned processing result, which is usually defined as / gateway / reply / $M. Similar to the first and second topics, $M can be m1 or m2 depending on the component of the response. When the edge gateway completes the processing of the control command issued by the cloud, it will return the processing result to the cloud gateway management platform through the third topic. The processing result is also encapsulated in JSON format, including fields such as command ID, processing result (such as success or failure status code), error message (if any), etc. By subscribing to the third topic, the cloud platform can obtain the status and results of command execution in a timely manner, thereby completing the closed loop of remote control and management.

[0074] In addition, the MQTT protocol also defines the id, method, timestamp, properties, code, errorMsg, and result fields to represent specific information. The description of the specific fields is shown in Table 1:

[0075] Table 1 Field Description

[0076]

[0077] Optionally, the above method also includes: receiving a control command from a cloud gateway management platform; sending the control command to a proxy component in an edge gateway through a control module in the edge middleware, wherein the control module is located in a core service layer of the edge middleware; processing the control command through the proxy component to obtain a processing result.

[0078] Furthermore, executing the control command through the proxy component includes: converting the control command from an initial format to a target format, and processing the control command after the format conversion through the proxy component, wherein the target format is used to adapt to the application deployment environment on the computing board of the edge gateway.

[0079] In the embodiment of the present application, it also includes a control command processing flow between the FTTR-B high-order converged gateway and the cloud gateway management platform, which reflects the efficient transmission and execution capabilities of control commands from the cloud to the edge in edge computing. The key to this process lies in the close collaboration between the COMMAND module (control module) of the edge middleware EdgeX Foundry and the proxy component on the computing board, as well as the flexible conversion of the control command format, which ensures that the control commands can be executed correctly and the processing results are accurately returned to the cloud, providing small and micro enterprises with simple and intelligent network and application management capabilities. Through this mechanism, gateway devices can not only cope with network-level management needs, but also flexibly deploy and run AI smart applications, greatly improving the comprehensive service capabilities of edge gateways. The following is combined with Figure 5 and Figure 6 The above contents are explained.

[0080] Figure 5 is a communication flow diagram based on the MQTT protocol provided in an embodiment of the present application, such as Figure 5 As shown in the figure, the FTTR-B mainboard and the computing board in the FTTR-B high-order converged gateway are two device nodes M1 and M2 respectively, and communicate with EdgeX Foundry through the MQTT protocol in the EdgeX Foundry device service layer (Device Service). The MQTT Broker is a message middleware responsible for receiving and forwarding messages. For example, the FTTR-B device regularly (such as every 60 seconds) reports its status information to the Core Data of the core service layer through the Topic / gateway / report / SM (here SM=M1, for the data of the FTTR-B mainboard) subscribed to the MQTT protocol, such as MAC address, SN, IP, performance data, etc. The computing board also reports its performance data and application list to the Core Data of the core service layer through Topic / gateway / report / SM (here SM=M2, for the data of the computing board). When the cloud gateway management platform sends a control command to EdgeX Foundry, the Command service in EdgeX Foundry sends the command to the corresponding device through the subscribed Topic / gateway / command / SM. After receiving the command, the device sends a response back to EdgeX Foundry through Topic / gateway / reply / SM to complete the command execution and feedback.

[0081] Figure 6 is another communication flow diagram based on the MQTT protocol provided in an embodiment of the present application, such as Figure 6As shown, the Command module receives a control command (such as an application installation command) from the cloud gateway management platform, which contains detailed information about the application, such as id, method, timestamp, attributes, etc. The control command is sent to the MQTTBroker through the MQTT protocol, and then received by the agent component Agent in the edge gateway. As part of the edge gateway, the Agent is responsible for listening to the Topic / gateway / command / m2 corresponding to the control command. At the same time, the Agent converts the control command from the initial JSON format to the Helm command format (i.e., the above-mentioned target format) to adapt to the K3S cluster environment of the computing board, and sends it to the Helm-Controller for processing. After receiving the command, the Helm-Controller parses the command information and triggers the watch mechanism to monitor changes in the Helmchart CRDs. Once a change is detected, the job.batch execution is triggered through the onChange mechanism, thereby deploying the specified application on the K3S cluster. Finally, after the application is deployed, Helm-Controller or Agent will also feedback the processing results to the cloud. The results include application deployment status, possible error information, etc., and are also sent to the cloud gateway management platform via the MQTT protocol via the / gateway / reply / m2 Topic.

[0082] Figure 7 This is another communication flow diagram based on the MQTT protocol provided in an embodiment of the present application, such as Figure 7 As shown in the figure, the (cloud) gateway management platform communicates with EdgeX Foundry via the MQTT protocol. The gateway management platform provides a variety of functions, including gateway details, slave gateway management, network topology display, performance details, QoS (quality of service), VPN (virtual private network), LAN&WAN (local area network and wide area network) configuration, Wi-Fi management, application market, and application management. These functions interact with EdgeX Foundry's Configurable Application Service and Application Service through MQTT Broker to achieve remote monitoring and management of FTTR-B high-order converged gateways, as well as application deployment and lifecycle management, thereby providing comprehensive network and computing power support for small and micro enterprises.

[0083] In the embodiment of the present application, the advanced network functions and edge computing capabilities of the FTTR-B high-order converged gateway are fully integrated, and by deploying the EdgeX Foundry edge middleware on the computing board, efficient cloud management of gateway data and automatic deployment of applications are achieved. Specifically, the present application adopts a unique dual-motherboard architecture, that is, the combination of the FTTR-B motherboard and the X86 computing board, which communicates at high speed through the RJ45 2.5G network port, enhancing the computing power and network performance of edge devices. With the help of the MQTT protocol, the gateway device can regularly upload status and performance data to the cloud in JSON format, and receive control commands from the cloud, realizing cloud-edge collaboration. In addition, through the integration of the Agent component and the Helm-Controller, the commands issued by the cloud are automatically converted into application deployment actions on the computing board, which greatly simplifies the application deployment process and improves operation and maintenance efficiency.

[0084] Through the processing method and system of gateway data in the embodiment of this application, the stability and bandwidth of the network of small and micro enterprises are significantly improved, the application scenarios of edge computing are expanded, and the operation and maintenance complexity of network and computing resources is reduced, so that enterprises can focus on core business without having to invest too much resources in the management of IT infrastructure. Through the cloud gateway management platform, enterprises can remotely monitor and maintain network equipment, realize visual management of network topology, Wi-Fi optimization, one-click detection, segmented speed measurement, etc. At the same time, the application market function supports enterprises to download and deploy applications on demand, meet the needs of AI intelligent applications and private applications, and improve the digital transformation efficiency and business innovation capabilities of small and micro enterprises as a whole.

[0085] Figure 8 is a flow chart of a method for processing gateway data according to an embodiment of the present application, such as Figure 8 As shown, the method is applied to a cloud gateway management platform and includes the following steps:

[0086] Step S802: Obtain control commands from the cloud gateway management platform.

[0087] In the above step S802, the acquisition of control commands usually starts from the management interface or API call of the cloud gateway management platform, which is triggered by the system administrator or the automated operation and maintenance system. The control commands can be operations such as creating a Wi-Fi network, configuring network parameters, obtaining basic device status, and managing application lifecycles. These commands are constructed in JSON format on the cloud platform, containing necessary information such as specific command type, target device identifier, timestamp, command parameters, etc., to ensure the clarity and executability of the commands.

[0088] Step S804, sending the control command to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and processing the control command through the edge gateway to obtain the processing result, wherein the edge middleware is deployed in the edge gateway, and the edge middleware is used to support data transmission between the cloud gateway management platform and the edge gateway.

[0089] In the above step S804, in the cloud gateway management platform, after the control command is processed, it is published to a predefined Topic, such as / gateway / command / $M, through the MQTT protocol, where $M is a variable, which is replaced according to the different control targets (such as FTTR-B or computing board) to ensure that the command can be received by the correct target component. After EdgeX Foundry on the edge gateway receives the control command, the Command service module will parse and process these commands to obtain the processing results. Specifically, for the FTTR-B high-order fusion gateway, its Command service can interpret the methods in the control command (such as appInstall) and convert them into corresponding operations. Among them, the appInstall command may involve obtaining the application installation file from the cloud, and then deploying it in a container on the computing board through the Helm-Controller component. During the processing process, it is necessary to interact with multiple internal components, such as the AI ​​computing card of the computing board, other service layers of the edge middleware, etc., to perform a series of operations to complete the instructions in the control command.

[0090] Step S806, returning the processing result to the cloud gateway management platform.

[0091] In the above step S806, once the edge gateway completes the processing of the control command, its response result will be encapsulated as an MQTT message, including fields such as id (corresponding to the id in the control command, identifying the source of the response), code (response code, indicating the result of command execution), and result (specific processing result), and sent back to the cloud gateway management platform through the MQTT protocol. Specifically, the response result can be published to a predefined Topic, such as / gateway / reply / m1 or / gateway / reply / m2, depending on whether the response is from the FTTR-B high-order fusion gateway or the computing board. The cloud gateway management platform subscribes to these Topics to receive response messages, parses the payload in JSON format, extracts the id to match the original control command, and thus confirms which control commands have been responded to. For example, the code and result fields are used to evaluate the status and results of command execution. A code of 0 may indicate successful execution, while other non-zero values ​​may indicate some kind of error or exception.

[0092] Through the above steps S802 to S806, the purpose of ensuring efficient data transmission and remote gateway management between the edge and the cloud through edge middleware is achieved, thereby achieving the technical effect of enhancing the edge computing power and intelligent operation and maintenance of small and micro enterprises in digital transformation, and further solving the technical problems of high difficulty in network operation and maintenance, insufficient edge computing power and poor convenience in application deployment for small and micro enterprises in related technologies.

[0093] According to an embodiment of the present application, a gateway data processing system is provided, including an edge gateway and a cloud gateway management platform, wherein the edge gateway deploys edge middleware, uploads gateway data of the edge gateway to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and processes the gateway data through the cloud gateway management platform, wherein the edge middleware is used to support data transmission between the edge gateway and the cloud gateway management platform; the cloud gateway management platform is used to send control commands of the cloud gateway management platform to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and processes the control commands through the edge gateway to obtain processing results; and returns the processing results to the cloud gateway management platform.

[0094] It should be noted that the gateway data processing system of the embodiment of the present application can be used to execute the gateway data processing method provided in the embodiment of the present application, which will not be described in detail here.

[0095] According to an embodiment of the present application, a gateway data processing device is provided. It should be noted that the gateway data processing device of the embodiment of the present application can be used to execute the gateway data processing method provided in the embodiment of the present application. The gateway data processing device provided in the embodiment of the present application is introduced below.

[0096] Fig. 9 1 is a structural diagram of a gateway data processing device provided according to an embodiment of the present application. Fig. 9 As shown, the device is applied to an edge gateway, including:

[0097] A first acquisition module 902 is used to acquire gateway data of an edge gateway, wherein the edge gateway deploys edge middleware, and the edge middleware is used to support data transmission between the edge gateway and the cloud gateway management platform;

[0098] The first processing module 904 is used to upload the gateway data to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and process the gateway data through the cloud gateway management platform.

[0099] Through the first acquisition module 902 and the first processing module 904 in the above-mentioned gateway data processing device, the purpose of ensuring efficient data transmission and remote gateway management between the edge and the cloud through the edge middleware is achieved, thereby achieving the technical effect of enhancing the edge computing power and intelligent operation and maintenance of small and micro enterprises in digital transformation, and further solving the technical problems of high difficulty in network operation and maintenance, insufficient edge computing power and poor convenience in application deployment for small and micro enterprises in related technologies.

[0100] The gateway data processing device provided in the embodiment of the present application also includes a second processing module 906, which is used to receive control commands from the cloud gateway management platform; send the control commands to the agent component in the edge gateway through the control module in the edge middleware, wherein the control module is located in the core service layer of the edge middleware; process the control commands through the agent component to obtain processing results.

[0101] In the gateway data processing device provided in an embodiment of the present application, the second processing module is also used to convert the control command from an initial format to a target format, and process the control command after format conversion through a proxy component, wherein the target format is used to adapt to the application deployment environment on the computing board of the edge gateway.

[0102] Fig.10 1 is a structural diagram of a gateway data processing device provided according to an embodiment of the present application. Fig.10 As shown, the device is applied to a cloud gateway management platform, including:

[0103] The second acquisition module 1002 is used to obtain control commands from the cloud gateway management platform;

[0104] The third processing module 1004 is used to send the control command to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and process the control command through the edge gateway to obtain a processing result, wherein the edge middleware is deployed in the edge gateway, and the edge middleware is used to support data transmission between the cloud gateway management platform and the edge gateway;

[0105] The return module 1006 is used to return the processing result to the cloud gateway management platform.

[0106] Through the second acquisition module 1002, the third processing module 1004 and the return module 1006 in the above-mentioned gateway data processing device, the purpose of ensuring efficient data transmission and remote gateway management between the edge and the cloud through the edge middleware is achieved, thereby achieving the technical effect of enhancing the edge computing power and intelligent operation and maintenance of small and micro enterprises in digital transformation, and further solving the technical problems of high difficulty in network operation and maintenance, insufficient edge computing power and poor convenience in application deployment for small and micro enterprises in related technologies.

[0107] An embodiment of the present application also provides an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the above-mentioned gateway data processing method.

[0108] It should be noted that the above electronic equipment is used to execute Figure 2 The gateway data processing method shown in the figure, therefore the relevant explanations and instructions in the above gateway data processing method are also applicable to the electronic device and will not be repeated here.

[0109] An embodiment of the present application further provides a non-volatile storage medium, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned gateway data processing method by running the computer program.

[0110] It should be noted that the above non-volatile storage medium is used to execute Figure 2 The gateway data processing method shown in the figure, therefore the relevant explanations in the above gateway data processing method are also applicable to the non-volatile storage medium, and will not be repeated here.

[0111] An embodiment of the present application also provides a computer program product, including computer instructions, which implement the above-mentioned gateway data processing method when executed by a processor.

[0112] It should be noted that the above-mentioned computer program product is used to execute Figure 2 The method for processing gateway data shown in the figure, therefore the relevant explanations in the above-mentioned method for processing gateway data are also applicable to the computer program product, and will not be repeated here.

[0113] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0114] 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.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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 is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server or 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, RandomAccess Memory), mobile hard disk, disk or CD-ROM and other media that can store program codes.

[0119] 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 method for processing gateway data, characterized in that: Applied to edge gateways, including: Acquire gateway data of an edge gateway, wherein the edge gateway deploys edge middleware, and the edge middleware is used to support data transmission between the edge gateway and a cloud gateway management platform; The gateway data is uploaded to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and the gateway data is processed by the cloud gateway management platform.

2. The method according to claim 1, characterized in that The edge gateway includes a gateway mainboard and a computing board. The edge middleware is deployed on the computing board. The gateway mainboard and the computing board transmit data with the cloud gateway management platform through the edge middleware. The computing board is used to enhance the edge computing capability of the edge gateway.

3. The method according to claim 1, characterized in that The edge middleware includes a device service layer, a core service layer, a support service layer and an application service layer, wherein the device service layer is used to communicate with the edge gateway through a network interface, the core service layer is used to process the gateway data and the control commands of the cloud gateway management platform, the support service layer is used to monitor the operating status of the edge gateway, and the application service layer is used to configure the application selected by the cloud gateway management platform.

4. The method according to claim 1, characterized in that The method further comprises: Receiving control commands from the cloud gateway management platform; Sending the control command to the proxy component in the edge gateway through a control module in the edge middleware, wherein the control module is located in the core service layer of the edge middleware; The control command is processed by the proxy component to obtain a processing result.

5. The method according to claim 4, characterized in that Executing the control command through the proxy component includes: The control command is converted from an initial format to a target format, and the control command after the format conversion is processed by the proxy component, wherein the target format is used to adapt to the application deployment environment on the computing board of the edge gateway.

6. The method according to claim 1, characterized in that The topics subscribed by the message queue telemetry transmission protocol include a first topic, a second topic and a third topic, wherein the first topic is used to upload the gateway data of the edge gateway to the edge middleware and the cloud gateway management platform, the second topic is used to send the control command of the cloud gateway management platform to the edge gateway, and the third topic is used to return the processing result of the control command by the edge gateway to the edge middleware and the cloud gateway management platform.

7. A method for processing gateway data, characterized in that: Applied to cloud gateway management platform, including: Obtain control commands from the cloud gateway management platform; The control command is sent to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and the control command is processed by the edge gateway to obtain a processing result, wherein the edge middleware is deployed in the edge gateway, and the edge middleware is used to support data transmission between the cloud gateway management platform and the edge gateway; The processing result is returned to the cloud gateway management platform.

8. A gateway data processing system, characterized in that: Including edge gateway and cloud gateway management platform, among which, The edge gateway deploys edge middleware, uploads the gateway data of the edge gateway to the cloud gateway management platform through the message queue telemetry transmission protocol in the edge middleware, and processes the gateway data through the cloud gateway management platform, wherein the edge middleware is used to support data transmission between the edge gateway and the cloud gateway management platform; The cloud gateway management platform is used to send the control command of the cloud gateway management platform to the edge gateway through the message queue telemetry transmission protocol in the edge middleware, and process the control command through the edge gateway to obtain the processing result; and return the processing result to the cloud gateway management platform.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store program instructions; The processor is connected to the memory and is used to execute the gateway data processing method described in any one of claims 1 to 6 or claim 7.

10. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the gateway data processing method described in any one of claims 1 to 6 or claim 7 by running the computer program.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the gateway data processing method described in any one of claims 1 to 6 or claim 7 is implemented.

Images