[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN116208480A - Edge gateway system - Google Patents

Edge gateway system Download PDF

Info

Publication number
CN116208480A
CN116208480A CN202211698893.2A CN202211698893A CN116208480A CN 116208480 A CN116208480 A CN 116208480A CN 202211698893 A CN202211698893 A CN 202211698893A CN 116208480 A CN116208480 A CN 116208480A
Authority
CN
China
Prior art keywords
edge
information
data
gateway system
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211698893.2A
Other languages
Chinese (zh)
Inventor
朱杰
张倍先
李璟
姚林林
罗金龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Intelligent Building Technology Co ltd
Original Assignee
Beijing Intelligent Building Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Intelligent Building Technology Co ltd filed Critical Beijing Intelligent Building Technology Co ltd
Priority to CN202211698893.2A priority Critical patent/CN116208480A/en
Publication of CN116208480A publication Critical patent/CN116208480A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/084Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses an edge gateway system. Comprising the following steps: at least one edge node and an edge manager, the edge manager comprising: the system comprises a basic management module and an edge management module, wherein the basic management module is used for monitoring hardware information of an edge gateway system; the edge management module comprises: the edge equipment management sub-module is used for managing equipment information and configuration information of the edge equipment; the edge service management sub-module is used for configuring the edge node capacity, the northbound forwarding rule, the alarm rule and the scene linkage triggering rule. The cloud edge coordination and equipment management method and device solve the technical problem that heterogeneous equipment cannot be docked in the related technology, and cloud edge coordination and equipment management are achieved.

Description

Edge gateway system
Technical Field
The present application relates to the field of edge computing technologies, and in particular, to an edge gateway system.
Background
The intelligent park construction utilizes new generation information and communication technology to sense, monitor, analyze, control and integrate resources of each key link of the park, and on the basis, intelligent response to various demands is realized, so that the whole operation of the park has self-organizing, self-operating and self-optimizing capabilities.
But because the rapid development of wisdom garden for to the management of wisdom garden, temporarily not have still relevant technique can cooperate through cloud limit and carry out effective management to edge equipment, thereby reduce the occupation resource and the consumption of edge calculation.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the application provides an edge gateway system, which at least solves the technical problems that heterogeneous equipment cannot be docked in the related technology, and cloud edge coordination and equipment management are realized.
According to an aspect of the embodiments of the present application, there is provided an edge gateway system, including: at least one edge node and an edge manager, the edge manager comprising: the system comprises a basic management module and an edge management module, wherein the basic management module is used for monitoring hardware information of an edge gateway system; the edge management module comprises: the edge equipment management sub-module is used for managing equipment information and configuration information of the edge equipment; the edge service management sub-module is used for configuring the edge node capacity, the northbound forwarding rule, the alarm rule and the scene linkage triggering rule.
Optionally, the base management module includes: the system login unit is used for responding to a login request sent by the client and logging in the edge gateway system, wherein the login request comprises the following steps: access address, login user name information and login password information of the edge gateway system.
Optionally, the base management module further comprises: the system inquiry unit is used for inquiring the first data of the utilization rate of the central processing unit of the edge gateway system, the second data of the utilization rate of the memory and the third data of the utilization rate of the disk, and displaying the system version information, the process monitoring information and the equipment overview information of the edge gateway system.
Optionally, the edge device management submodule includes: the data acquisition unit is used for acquiring data resources from the edge equipment; managing a user-configurable device template in accordance with the data resource, wherein configuring the device template comprises: template name and update time; managing a user-settable cloud channel according to a preset heterogeneous protocol, wherein setting the cloud channel comprises: channel name, protocol type, and enablement status; and configuring the edge equipment based on the equipment template and the cloud channel.
Optionally, the edge device management sub-module further includes: the data processing unit is used for analyzing the equipment template to obtain a corresponding data cleaning strategy and data conversion rule script, and cleaning and converting the data resource according to the data cleaning strategy and the data conversion rule script to obtain target resource data; and analyzing the target resource data, and uploading an analysis result to the cloud server.
Optionally, the edge service management submodule includes: a management unit for checking the network information of the edge node; setting login password information of an edge gateway system; setting a restarting service of an edge gateway system; setting a network time protocol server of an edge gateway system according to the time zone in which the edge node is positioned; backing up configuration information; and managing address information and account information of the cloud server configurable by the user, wherein the account information comprises: server port, user name information and login password information of cloud server; the drive service device is managed according to a heterogeneous protocol.
Optionally, the edge service management sub-module further comprises: a storage management unit, configured to configure a storage capability of the edge node; inquiring target log information according to a preset log inquiring condition.
Optionally, the edge service management sub-module further comprises: the rule engine unit is used for managing the north configuration and setting corresponding north forwarding rules, and the north forwarding rules comprise: rule name, device template, northbound action, and configuration enablement status.
Optionally, the edge service management sub-module further comprises: the alarm management unit is used for checking the name, the alarm grade and the alarm processing result of the edge equipment with the alarm event; configuring an alarm storage rule, wherein the alarm storage rule comprises: the alarm identification clearing period, the alarm identification being an ignored interval period and the alarm repeat notification period.
Optionally, the edge service management sub-module further comprises: the scene linkage unit is used for responding to a scene setting instruction of a user and managing a scene starting state; managing user-configurable scene linkage trigger actions; a user configurable linkage execution time period for a particular scene is managed.
In the embodiment of the application, the edge node in the edge gateway system carries the core of the edge computing service, and the edge manager is responsible for unified management of the edge node and supporting the real-time closed-loop control service. An edge manager in an edge gateway system includes: the system comprises a basic management module and an edge management module, wherein the basic management module is used for monitoring hardware information of an edge gateway system; the edge management module comprises: the edge equipment management sub-module is used for managing equipment information and configuration information of the edge equipment; the edge service management sub-module is used for configuring the edge node capacity, the northbound forwarding rule, the alarm rule and the scene linkage triggering rule. Therefore, the edge gateway system is used as a conversion center for connecting the edge equipment and the cloud channel, so that massive heterogeneous equipment can be connected and managed, and the technical problem that cloud edge coordination and equipment management are realized because the heterogeneous equipment cannot be connected in the related technology is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
FIG. 1 is a schematic diagram of an alternative edge gateway system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an alternative edge gateway system login interface, according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a system query interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 4 is a device template interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 5 is a channel setup interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 6 is a device setup interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 7 is a network management interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 8 is a password setup interface for an alternative edge gateway system according to an embodiment of the present application
FIG. 9 is a restart setup interface for an alternative edge gateway system according to an embodiment of the present application;
FIG. 10 is a time setting interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 11 is a restart setup interface for an alternative edge gateway system according to an embodiment of the present application;
FIG. 12 is a remote configuration interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 13 is a restart setup interface for an alternative edge gateway system according to an embodiment of the present application;
FIG. 14 is a log setup interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 15 is a log view interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 16 is a northbound configuration interface of an alternative edge gateway system in accordance with an embodiment of the present application;
FIG. 17 is a rule configuration interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 18 is an alert viewing interface of an alternative edge gateway system according to an embodiment of the present application;
FIG. 19 is an alternative alert configuration interface for an edge gateway system according to an embodiment of the present application;
FIG. 20 is a scene setup interface of an alternative edge gateway system according to an embodiment of the present application;
fig. 21 is an action group interface of an alternative edge gateway system according to an embodiment of the present application.
Detailed Description
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and the accompanying drawings are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For a better understanding of the embodiments of the present application, some nouns or translations of terms that appear during the description of the embodiments of the present application are explained first as follows:
edge node: any node with computing resources and network resources between a data generation source and a cloud computing center; or an open platform integrating network, computing, storage, and application core capabilities on the side closer to the object or data source. The edge node is initiated at the edge side, accelerates the network service response, and meets the basic requirements in the aspects of real-time service, application intelligence, security, privacy protection and the like.
OPC (Object Linking and Embedding for Process Control) protocol: is an application of microsoft corporation's object connection and embedding technology in process control. The OPC specification was developed based on OLE/COM/DCOM technology and established a unified standard for the development of object-oriented industrial automation software in C/S mode, in which a method for automated data real-time exchange between PC-based clients is defined. After the OPC standard is adopted, the driver is not developed by a software developer any more, but the hardware developer packages each hardware device driver and each communication program into a data server which can independently run or run in an embedded mode according to the characteristics of hardware.
Modbus protocol: a general-purpose language for use in electronic controllers. Through this protocol, communication can be made between controllers, between controllers via a network, and other devices. The Modbus protocol is called a universal industrial standard, and control equipment produced by different manufacturers can be connected with an urban industrial network for centralized monitoring.
SDN (Soft Defined Network, software defined network): the aim is to improve network control by enabling enterprises and service providers to quickly respond to changing business needs. The typical SDN architecture includes three layers, an application layer, a control layer, and an infrastructure layer, respectively, wherein the application programs include typical network applications and functions used by organizations, such as load balancing, intrusion detection, etc.; the control layer represents centralized SDN controller software, acting as the brain of the SDN; the basic setting layer consists of physical switches in the network, forwarding network traffic to the switches. These three layers enable north and south Application Programming Interfaces (APIs) to communicate.
Scene linkage: the method is a visual programming method for developing automated business logic in a rule engine, linkage rules among devices can be defined in a visual mode, and the rules are deployed on the cloud or edge section of an Internet of things platform.
Example 1
According to the embodiment of the application, the edge gateway system is provided, and can be used as a conversion middle station for connecting edge equipment and a cloud channel, so that massive heterogeneous equipment can be configured, monitored and checked on edge nodes; meanwhile, data information of the edge equipment is collected and managed in real time, and remote configuration management, alarm log management, heterogeneous protocol driving management, scene linkage management and the like are carried out on the edge equipment.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
Fig. 1 is a schematic structural diagram of an alternative edge gateway system according to an embodiment of the present application, and as shown in fig. 1, the edge gateway system 10 includes: at least one edge node 11 and an edge manager 12, wherein,
the edge nodes 11 are deployed as hardware entities on the edge devices, and are used for responding to a query request of a cloud user and acquiring data resources from the edge devices by adopting an OPC data acquisition protocol, wherein each edge device is provided with at least one edge node.
The edge node 11 deployed on the edge device may be a front end processor of the edge device, or may be a power supply device, a machine room rack, a security device, a network device, or the like.
Specifically, the edge node 11 further includes an edge cloud server, which is configured to provide computing power to the edge node, and the edge cloud server and the central cloud server (i.e. cloud servers) adopt a unified network architecture and interface, for example, when siemens PLC is adopted, RS485 or RS232 may be selected.
In general, RS485 has several advantages over RS 232:
(1) RS232 is one of computer communication interfaces, and the physical structure is fixed, and generally appears in the form of 9 pins (DB-9) or 25 pins (DB-25); the RS485 has no specific physical shape and can be set according to the actual condition of engineering;
(2) The signal level value of the RS232 transmission level signal interface is higher, the chip of the interface circuit is easy to be damaged, and the signal level value is not compatible with the TTL (Transistor-Transistor Logic) level, so that an additional level conversion circuit is required to be added to connect with the TTL circuit; the interface signal level of the RS485 is lower than that of the RS232, so that a chip of an interface circuit is not easy to damage, the level is compatible with the TTL level, and the interface signal level is convenient to directly connect with the TTL circuit;
(3) The maximum standard value of the transmission distance of RS232 is 15 meters, and the maximum wireless transmission distance of RS485 is 1200 meters;
(4) The RS232 interface allows connection of only one transceiver on the bus, while the RS485 interface allows connection of how many 128 transceivers on the bus.
Therefore, an RS485 interface structure is preferably adopted in the embodiment of the present application.
Further, since the interface protocol Modbu can support the electrical structure of RS485, the interface protocol can select Modbu.
It should be noted that, the number of edge nodes may be adaptively configured according to practical application needs, which is not limited in the embodiment of the present application.
Edge manager 12 may drive or invoke edge node 11. Typically, the presentation core of edge manager 12 is software, and in this embodiment, edge manager 12 may directly encapsulate computing resources, network resources, and storage resources of edge node 11, providing an invocation interface so that the resources of edge node 11 may be used in a manner such as code download, network policy configuration, and database operations.
Alternatively, the resources of the edge node 11 are functionally packaged into functional modules, which are combined or invoked by the edge manager 12 in a model-driven business orchestration manner.
In the embodiment of the application, the edge manager 12 is constructed by adopting the SDN, so that network management and automatic operation and maintenance are realized. As shown in fig. 1, the edge manager 12 includes a base management module 121 and an edge management module 122.
Specifically, the basic management module 121 is mainly responsible for monitoring hardware information of the edge gateway system; and the edge management module 122 may be specifically divided into: an edge device management submodule 1221 and an edge service management submodule 1222, wherein the edge device management submodule 1221 is mainly responsible for managing device information and configuration information of an edge device; the edge service management sub-module 1222 is configured for configuring the edge node storage capability, the northbound forwarding rule, the alarm rule, and the scene linkage triggering rule.
Edge manager 12 of the edge gateway system will be described in detail below with particular reference to software operations.
Specifically, the base management module 121 includes: and the system login unit is used for responding to a login request sent by the client and logging in the edge gateway system. Wherein the login request includes: access address, login user name information and login password information of the edge gateway system.
FIG. 2 is a schematic diagram showing an alternative edge gateway system login interface, where when a user needs to access the edge gateway system, an access address may be input on a browser interface, and the user may view the login interface shown in FIG. 2, where the user needs to correctly input user name information and login password information at the same time, and click a login button after the input is completed to enter the edge gateway system for operation; if the user cannot log in the system correctly, the system cannot be used normally.
If the user logs in the edge gateway system for the first time, the user related information is input for registration, and a login password is set, so that the user can log in to enter the system directly next time.
After logging in the system, the system directly enters a main interface of the edge gateway system, a plurality of core functions of the software are displayed in the main interface, and a user can perform operations such as checking, creating, editing, importing, exporting, deleting and the like according to the needs of the user.
In addition, the basic management module 121 further includes: the system inquiry unit is used for inquiring the first data of the utilization rate of the central processing unit of the edge gateway system, the second data of the utilization rate of the memory and the third data of the utilization rate of the disk, and displaying the system version information, the process monitoring information and the equipment overview information of the edge gateway system.
Fig. 3 shows a system query interface of an alternative edge gateway system, and detailed information of the edge gateway system can be checked in real time through a system query unit as shown in fig. 3. Such as CPU utilization, memory utilization, disk utilization; the system information such as software version, machine architecture, construction time and the like can be directly checked, and CPU utilization rate and memory utilization rate corresponding to different process names, the total quantity of edge equipment examples, the total quantity of online edge equipment and the number of enabled cloud channels can be directly checked.
After learning the system details, the user may link and manage the mass network edge devices, such as sensors, instrumentation, controllers, etc., through the edge management module 122.
In order to achieve stable and reliable connection of the edge devices of the mass network and accurate transmission of the data resources, the edge devices (also referred to as southbound devices) need to be acquired by the data acquisition unit of the edge device management sub-module 1221 and the attribute update of the edge devices is completed.
The data acquisition unit acquires data resources from the edge device through a southbound interface protocol (OpenFlow protocol, OF protocol), and sends the data resources to the cloud server after preprocessing the data resources through the data processing unit, and the cloud server can collect and analyze the data resources from each edge node 11 to form a data lake. Data may be divided into main data, business data (also referred to as behavior data), and metadata according to the different characteristics and roles of the data. Wherein, the main data is data describing basic attribute aspects of the service data, and has relatively stable characteristics. The main data can be repeatedly used by a plurality of users in the platform and exist in a plurality of heterogeneous application systems; the business data is data formed by the behavior of a business entity in the system, and the business data is data generated by a business body by using related business; metadata is data describing data, and generally refers to key system data related to definition, target definition, conversion rules and the like of related data generated in a system construction process, for example, description of data in various aspects of data such as relationship, service, structure, definition, storage, constraint, safety and the like.
The data acquisition unit manages a user-configurable device template according to the data resources, wherein configuring the device template comprises: template name and update time; managing a user-settable cloud channel according to a preset heterogeneous protocol, wherein setting the cloud channel comprises: channel name, protocol type, and enablement status; and configuring the edge equipment based on the equipment template and the cloud channel.
Fig. 4 shows an optional device template interface of the edge gateway system, where, as shown in fig. 4, a user may create, edit, delete, import or export a device template on the interface to complete setting of related attributes of a device, where configuring the device template includes: template name and update time.
Fig. 5 illustrates a channel setting interface of an optional edge gateway system, where, as shown in fig. 5, in order to flexibly adapt to various industrial devices and protocols, a user may create, edit, delete, import or export a channel configuration on the interface, and complete setting of relevant properties of a cloud channel, where setting the cloud channel includes: the cloud channel defines the connection mode of heterogeneous protocols.
The device template can be configured by collecting the data resources of the edge devices, and meanwhile, the corresponding cloud channels are configured on the channel setting interface, so that the configuration of the edge devices can be completed by corresponding a specific edge device through the device template and the cloud channels. The edge device may be, but is not limited to, various sensors, instruments, controllers, and the like.
Fig. 6 illustrates an alternative device setup interface of the edge gateway system, where, as shown in fig. 6, a user may create, edit, delete, import or export device settings at the interface according to the device template and cloud channel settings, and support viewing or operating configuration information of the device at the interface.
In addition, the edge device management submodule 1221 further includes an edge device management submodule further includes a data processing unit.
The data processing unit is used for analyzing the equipment template to obtain a corresponding data cleaning strategy and data conversion rule script, and cleaning and converting the data resource according to the data cleaning strategy and the data conversion rule script to obtain target resource data; and analyzing the target resource data, and uploading an analysis result to the cloud server.
Specifically, in order to realize the edge autonomous capability of the intelligent park, that is, when the network is unstable and the edge cloud server of the edge node 11 is not connected with the cloud server to some extent, the data processing unit performs real-time analysis processing on the data resource acquired by the edge node 11, and continues to normally execute local business logic; and when the connection between the edge cloud server and the cloud server is restored, uploading the analysis result to the cloud server, and completing the synchronization of the data and the state.
Further, in order to realize the edge computing capability of the edge gateway, ensure that various applications can be run on the edge node, realize real-time local processing of data resources, and respond timely, real-time monitoring of the intelligent park application is required by the edge service management sub-module 1222.
Specifically, the edge service management submodule 1222 includes a management unit therein. The management unit is used for checking the network information of the edge node; setting login password information of an edge gateway system; setting a restarting service of an edge gateway system; setting a network time protocol server of an edge gateway system according to the time zone in which the edge node is positioned; backing up configuration information; and managing address information and account information of the cloud server configurable by the user, wherein the account information comprises: server port, user name information and login password information of cloud server; the drive service device is managed according to a heterogeneous protocol.
Fig. 7 shows an alternative network management interface of the edge gateway system, as shown in fig. 7, where a user may view network information of each edge node, for example, IP addresses corresponding to enp s0 as edge nodes are: 10.229.259.145; the subnet mask is: 255.255.255.0; the IPv6 address is: 1930:97:7c80:5787; the MAC address is: e8:6a:64:b8:79:96.
Fig. 8 shows an alternative password setup interface for the edge gateway system, where a user may set login password information for the edge gateway system and click a "save" button to upload the password to the cloud server, as shown in fig. 8.
Fig. 9 shows an alternative interface for setting up restart of the edge gateway system, where, as shown in fig. 9, a user may restart the edge gateway service by manually clicking on the "execute restart" button, and may directly view the start time of a specific restart of the system at this interface.
Fig. 10 illustrates an alternative edge gateway system time setting interface, as shown in fig. 10, where a user may set a network time protocol server of the edge gateway system according to a time zone in which an edge node is located, click a "save" button, and upload time configuration information to a cloud server. For example, when the target Time zone is Beijing, chongqing, uluji, and the current system Time is 2022-09-30, the user may select the system Time type to be NTP (Network Time Protocol ) or RTC (Real-Time Clock) type, and configure the corresponding Time server and port number, so as to complete the setting of the system Time.
FIG. 11 illustrates an alternative edge gateway system restart setup interface, as shown in FIG. 11, where a user may manually click a "download backup" button to backup edge gateway system configuration information; in addition, the configuration to be restored can be selected from the system database, and the backup configuration information can be uploaded.
Fig. 12 shows a remote configuration interface of an alternative edge gateway system, as shown in fig. 12, where a user may select whether to perform remote configuration through an "on" or "off" button, where the remote configuration includes a product configuration and a device configuration, and the user may select the content of the desired configuration according to the need. In addition, address information, server ports, cloud server user name information, login password information and device temporary token suffixes of the cloud server are required to be set.
Fig. 13 shows an optional interface for setting up restarting of the edge gateway system, as shown in fig. 13, where a user may create, edit, and delete driving service devices of heterogeneous protocols, and view the running states and import times of the driving service devices through the interface.
Meanwhile, the edge service management submodule 1222 also includes a storage management unit. The storage management unit is used for configuring the storage capacity of the edge node; inquiring target log information according to a preset log inquiring condition.
In addition, the storage management unit can be used for storing a device template, cloud channel configuration, scene linkage event log and the like which are set by the user.
FIG. 14 illustrates an alternative log setup interface for an edge gateway system, where a user may turn on or off the log storage capability of an edge node and set a threshold for disk usage of the system, and the system may alert when the disk usage of the system exceeds a preset threshold.
Fig. 15 illustrates an alternative log view interface for an edge gateway system through which a user may query log information by device type, log name, time period, as shown in fig. 15.
In order that the management end can remotely monitor all client devices supporting the network management protocol on the network, and meanwhile, the polling mode of trapping guidance is not increased too much, the client must actively report an abnormal event, and after the report of the abnormal event is obtained, the management end can further analyze the cause of the abnormal event by querying the related agent, so in the embodiment of the present application, the edge service management sub-module 1222 further includes a rule engine unit. The rule engine unit is used for managing the northbound configuration and setting corresponding northbound forwarding rules, and the northbound forwarding rules comprise: rule name, device template, northbound action, and configuration enablement status.
Fig. 16 illustrates an alternative north-bound configuration interface for an edge gateway system, through which a user may set the type of cloud server that the edge gateway system is connected to, as shown in fig. 16.
Fig. 17 illustrates an alternative rule configuration interface for an edge gateway system through which a user may create, edit, and delete northbound forwarding rules, as shown in fig. 17.
Generally, when an abnormal situation occurs in the edge device, the abnormal information needs to be actively reported through a responsive alarm prompt, and therefore, in the embodiment of the present application, the edge service management submodule 1222 further includes an alarm management unit. The alarm management unit is used for checking the name, alarm grade and alarm processing result of the edge equipment with the alarm event; configuring an alarm storage rule, wherein the alarm storage rule comprises: the alarm identification clearing period, the alarm identification being an ignored interval period and the alarm repeat notification period.
FIG. 18 illustrates an alternative alert viewing interface for an edge gateway system through which a user may view the alert time, alert device name, alert level, and alert processing results of an abnormal alert prompt, as illustrated in FIG. 18.
FIG. 19 illustrates an alternative alert configuration interface for an edge gateway system through which a user may set alert flags as ignored interval periods, alert repetition notification periods, and purge periods, as shown in FIG. 19, to complete the configuration of team alert rules.
Further, scene linkage deployed at the edge instance can quickly respond to local messages, and can also normally operate in a network disconnection environment. Thus, in the present embodiment, the edge service management sub-module 1222 further includes: the scene linkage unit is used for responding to a scene setting instruction of a user and managing a scene starting state; managing user-configurable scene linkage trigger actions; a user configurable linkage execution time period for a particular scene is managed.
Fig. 20 shows a scene setting interface of an alternative edge gateway system, through which, as shown in fig. 20, a user can create, edit or delete a specific scene, for example, when setting a scene name to work, the user can set the scene type as a rule triggering type, that is, once the user triggers a preset rule, the user determines that the corresponding scene is work.
Fig. 21 illustrates an alternative action group interface for an edge gateway system, through which a user may create, edit, or delete trigger actions for scene linkage, as shown in fig. 21.
In the embodiment of the application, the edge node in the edge gateway system has the functions of storage, calculation and the like, so that the function of cloud service is extended to the edge equipment, and the coverage range of the cloud service is expanded by cooperation between the cloud server and the edge node. The edge manager is responsible for unified management of the edge nodes and supporting real-time closed-loop control services. An edge manager in an edge gateway system includes: the system comprises a basic management module and an edge management module, wherein the basic management module is used for monitoring hardware information of an edge gateway system; the edge management module comprises: the edge equipment management sub-module is used for managing equipment information and configuration information of the edge equipment; the edge service management sub-module is used for configuring the edge node capacity, the northbound forwarding rule, the alarm rule and the scene linkage triggering rule. Therefore, the edge gateway system is used as a conversion center for connecting the edge equipment and the cloud channel, so that massive heterogeneous equipment can be connected and managed, and the technical problem that cloud edge coordination and equipment management are realized because the heterogeneous equipment cannot be connected in the related technology is solved.
In the embodiments provided in the present application, it should be understood that the disclosed technology may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of units may be a logic function division, and there may be another division manner in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution, in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application and are intended to be comprehended within the scope of the present application.

Claims (10)

1. An edge gateway system, comprising: at least one edge node and an edge manager, the edge manager comprising: a base management module and an edge management module, wherein,
the basic management module is used for monitoring hardware information of the edge gateway system;
the edge management module comprises: the edge equipment management sub-module is used for managing equipment information and configuration information of the edge equipment; the edge service management sub-module is used for configuring the edge node energy storage capacity, the northbound forwarding rule, the alarm rule and the scene linkage triggering rule.
2. The system of claim 1, wherein the base management module comprises: the system login unit is used for responding to a login request sent by the client and logging in the edge gateway system, wherein the login request comprises the following steps: access address, login user name information and login password information of the edge gateway system.
3. The system of claim 1, wherein the base management module further comprises: and the system inquiry unit is used for inquiring the first data of the utilization rate of the central processing unit of the edge gateway system, the second data of the utilization rate of the memory and the third data of the utilization rate of the disk, and displaying the system version information, the process monitoring information and the equipment overview information of the edge gateway system.
4. The system of claim 1, wherein the edge device management submodule comprises: the data acquisition unit is used for acquiring data resources from the edge equipment; managing a user-configurable device template according to the data resource, wherein configuring the device template comprises: template name and update time; managing a user-settable cloud channel according to a preset heterogeneous protocol, wherein setting the cloud channel comprises: channel name, protocol type, and enablement status; and configuring the edge equipment based on the equipment template and the cloud channel.
5. The system of claim 4, wherein the edge device management sub-module further comprises: the data processing unit is used for analyzing the equipment template to obtain a corresponding data cleaning strategy and a data conversion rule script, and cleaning and converting the data resource according to the data cleaning strategy and the data conversion rule script to obtain target resource data; and analyzing the target resource data, and uploading an analysis result to a cloud server.
6. The system of claim 5, wherein the edge service management submodule comprises: a management unit, configured to view network information of the edge node; setting login password information of the edge gateway system; setting a restarting service of the edge gateway system; setting a network time protocol server of the edge gateway system according to the time zone in which the edge node is located; backing up the configuration information; and managing address information and account information of the cloud server which can be configured by a user, wherein the account information comprises: the cloud server comprises a server port, user name information and login password information of the cloud server; the drive service device is managed according to a heterogeneous protocol.
7. The system of claim 1, wherein the edge service management sub-module further comprises: a storage management unit, configured to configure a storage capability of the edge node; inquiring target log information according to a preset log inquiring condition.
8. The system of claim 1, wherein the edge service management sub-module further comprises: the rule engine unit is used for managing the northbound configuration and setting corresponding northbound forwarding rules, and the northbound forwarding rules comprise: rule name, device template, northbound action, and configuration enablement status.
9. The system of claim 1, wherein the edge service management sub-module further comprises: the alarm management unit is used for checking the name, the alarm grade and the alarm processing result of the edge equipment with the alarm event; configuring an alarm storage rule, wherein the alarm storage rule comprises: the alarm identification clearing period, the alarm identification being an ignored interval period and the alarm repeat notification period.
10. The system of claim 1, wherein the edge service management sub-module further comprises: the scene linkage unit is used for responding to a scene setting instruction of a user and managing a scene starting state; managing user-configurable scene linkage trigger actions; a user configurable linkage execution time period for a particular scene is managed.
CN202211698893.2A 2022-12-28 2022-12-28 Edge gateway system Pending CN116208480A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211698893.2A CN116208480A (en) 2022-12-28 2022-12-28 Edge gateway system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211698893.2A CN116208480A (en) 2022-12-28 2022-12-28 Edge gateway system

Publications (1)

Publication Number Publication Date
CN116208480A true CN116208480A (en) 2023-06-02

Family

ID=86515352

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211698893.2A Pending CN116208480A (en) 2022-12-28 2022-12-28 Edge gateway system

Country Status (1)

Country Link
CN (1) CN116208480A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108353090A (en) * 2015-08-27 2018-07-31 雾角系统公司 Edge intelligence platform and internet of things sensors streaming system
KR102075791B1 (en) * 2019-04-10 2020-03-02 주식회사 와이드티엔에스 System For Prosessing Fast Data Using Linking IoT Device In Edge Computing
CN113868081A (en) * 2021-09-22 2021-12-31 山东电力研究院 Edge computing frame for power grid internet of things management platform and working method thereof

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108353090A (en) * 2015-08-27 2018-07-31 雾角系统公司 Edge intelligence platform and internet of things sensors streaming system
KR102075791B1 (en) * 2019-04-10 2020-03-02 주식회사 와이드티엔에스 System For Prosessing Fast Data Using Linking IoT Device In Edge Computing
CN113868081A (en) * 2021-09-22 2021-12-31 山东电力研究院 Edge computing frame for power grid internet of things management platform and working method thereof

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李世豪: "《面向电力物联的边缘计算框架设计初探》", 电力信息与通信技术, vol. 18, no. 12, 15 December 2020 (2020-12-15), pages 51 - 58 *

Similar Documents

Publication Publication Date Title
CN104699759B (en) A kind of data base automatic operation and maintenance method
CN105282772B (en) Wireless network datacom device monitoring system and apparatus monitoring method
US11226614B2 (en) Use of a smart node in a universal, smart system for monitoring industrial processes
US20080098454A1 (en) Network Management Appliance
CN110659109B (en) System and method for monitoring openstack virtual machine
CN207638691U (en) A kind of digitlization workshop network and data exchange system
CN103716173A (en) Storage monitoring system and monitoring alarm issuing method
CN103973815A (en) Method for unified monitoring of storage environment across data centers
CN114244676A (en) Intelligent IT integrated gateway system
CN104637265A (en) Dispatch-automated multilevel integration intelligent watching alarming system
CN106027674A (en) Technology architecture of "Internet & smart manufacturing"
Corradi et al. SIRDAM4. 0: A support infrastructure for reliable data acquisition and management in industry 4.0
CN215071803U (en) Online monitoring system of transformer substation
CN115037600A (en) Low-power-consumption Internet of things platform supporting long connection, equipment and management method thereof
CN114510391A (en) Monitoring management system integrating infrastructure
CN111711695B (en) Distributed equipment management system based on cloud platform
CN117112459A (en) Multi-device distributed data acquisition system construction and method
CN116208480A (en) Edge gateway system
WO2016091141A1 (en) Method and apparatus for information collection
CN113381880B (en) Internet of things equipment management method, device and system
CN109116815A (en) One kind is based on MQTT injection molding machine management system, method and storage medium
CN100410876C (en) Uniform exploitation method for security soft based on RMI standard
CN117950591B (en) Gateway storage management method and device, electronic equipment and storage medium
De Moura et al. Industrial Internet of Things: device management architecture proposal
CN117938617B (en) Device management method, device, computer device and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination