A data center component design method suitable for edge computing

Abstract

The application discloses a data center component design method suitable for edge computing, and comprises the following steps: constructing a data channel between an APP container and a data center; the data interaction channel is a message mode interaction channel or an API interface mode interaction channel; constructing a management module and a database contained in the data center according to different business requirements; the management module comprises a permission management module, a model interaction and management module, a device interaction and management module, a fixed value interaction and management module and a data interaction and management module; the database comprises a real-time database and a historical database; the real-time database and the historical database are connected with each module in the management module respectively. The application can realize data interaction decoupling, data interaction between applications through the data center, avoid private communication, realize data interaction decoupling and reduce interaction management complexity.

Description

Technical Field

[0001] This invention belongs to the field of power distribution Internet of Things technology, and specifically relates to a data center component design method suitable for edge computing. Background Technology

[0002] With the State Grid Corporation's need to build a power Internet of Things (IoT), higher requirements are being placed on existing equipment connection and access methods, data interaction methods, and capabilities. It is necessary to fully utilize modern information technologies such as mobile internet and artificial intelligence, as well as advanced communication technologies, across all aspects of the power system to achieve ubiquitous connectivity and human-machine interaction, creating a smart service system characterized by comprehensive status perception, efficient information processing, and convenient and flexible applications.

[0003] However, most devices are currently operating offline. Furthermore, each type of terminal differs significantly in terms of communication interfaces, communication resource requirements, computing power, and security capabilities. To support energy internet services and new internet services, even more types and numbers of terminals will be incorporated into the full-service power internet of things for management.

[0004] With the massive increase in the amount of data being accessed and the data becoming more diverse, and the lack of decoupling between applications and data in existing terminals, data sharing and integration among advanced applications on current terminals is difficult, resulting in low data reliability and data access performance, and difficulties in application upgrades and maintenance. Summary of the Invention

[0005] To address the aforementioned issues, this invention proposes a data center component design method suitable for edge computing, which enables data interaction decoupling. Applications interact with each other through the data center, avoiding private communication, thus reducing the complexity of interaction management.

[0006] To achieve the above-mentioned technical objectives and effects, the present invention is implemented through the following technical solution:

[0007] A data center component design method suitable for edge computing includes:

[0008] Establish a data channel between the APP container and the data center; the data interaction channel is either a message-mode interaction channel or an API interface-mode interaction channel.

[0009] Based on different business needs, the data center includes management modules and databases. The management modules include a permission management module, a model interaction and management module, a device interaction and management module, a setpoint interaction and management module, and a data interaction and management module. The database includes a real-time database and a historical database. The real-time database and the historical database are respectively connected to each module in the management modules.

[0010] Optionally, when the data interaction channel is a message-based interaction channel, the construction of the data channel between the APP container and the data center includes the following steps:

[0011] Create message processing subprocesses and business processing subthreads. The subprocesses and subthreads interact with each other through message queues. Create a main process to manage and monitor the subprocesses and subthreads.

[0012] Each message processing subprocess, upon receiving a JSON message from the APP container, first stores the JSON message in a buffer pool, then parses the JSON message corresponding to its business logic, and sends the parsed business data BLOB to the corresponding business processing sub-thread via a message queue for subsequent business processing. Each business processing sub-thread performs its corresponding business processing, generates a processing result structure BLOB, and sends it to the corresponding message processing subprocess. Each message processing subprocess assembles a JSON string based on the received data and finally returns the result to the APP container.

[0013] Optionally, the data center component design method further includes:

[0014] Establishing a SOCKET connection between each application container and the data center includes the following steps:

[0015] Each APP container acts as a client and establishes a SOCKET connection with the MQTT BROKER outside the APP container. The SOCKET connection is based on the multi-container bridging mechanism of the APP container itself. The APP container virtualizes a container bridge in the MQTT BROKER. When an APP container starts, it will be assigned an IP address called Container-IP according to the network segment of the container bridge. At the same time, the container bridge is set as the default gateway for each container.

[0016] Optionally, when the data interaction channel is an API interface mode interaction channel, the construction of the data channel between the APP container and the data center includes the following steps:

[0017] When each app container is created, the cross-container shared directory is specified by specifying the cross-container shared directory parameter in the container creation command;

[0018] When the service is started in the data center, a file is created in the cross-container shared directory to store the database in the data center.

[0019] Optionally, the real-time database uses a hash index as the indexing mechanism for the real-time database, and uses a static linked list to manage and allocate memory offset addresses during real-time database operations. The position index allocated by the static linked list during real-time database operations is mapped to the hash table of the real-time database, and the position index of the corresponding static linked list is stored in the hash table.

[0020] Optionally, the real-time database uses POSIX-standard file-mapped shared memory, which uses disk files for caching and synchronizes the disk files with the shared memory.

[0021] Optionally, the model interaction and management module includes:

[0022] The model setting unit is used to store the model name, attribute name, data type, minimum value, maximum value, step size, reporting identifier, and user-defined information of the model into the model information table, and return the setting results to the APP container.

[0023] The model query unit is used to query all the settings information of the corresponding model based on the model name provided by the application, and return the query results to the APP container.

[0024] The model deletion unit is used to delete the record in the model information table according to the model name to be deleted provided by the APP container, and also delete the corresponding model data in the device information table and real-time data table. Finally, the setting result is returned to the APP container.

[0025] Optionally, the device interaction and management module includes:

[0026] The device registration unit is used to store device information provided by the application, such as model name, device port, device address, custom description, device manufacturer ID, whether data is reported, and application name, into the device information table; it is also used to generate a unique identifier for the device based on the model name, device port, device address, and custom description, and store it in the device information table. After generating the unique identifier for the device, it retrieves all data attribute names of the model by querying the model table, and writes the unique identifier for the device and all attribute names as key-value pairs into the real-time data table.

[0027] The device unique identifier query unit is used to query the unique identifier of the corresponding device based on the device model name, device port, device address and custom description provided by the APP container, and return the query result to the APP container.

[0028] The device registration relationship query unit is used to read all records in the device information table, classify and combine the query records by device model and device port, and return them to the APP container.

[0029] Optionally, the setpoint interaction and management module includes:

[0030] The setting unit first determines the identity of the APP container. If it is not the data generator, the request is rejected. If it has setting permissions, the unique device identifier, setting name, value, and data type information provided by the APP container are written into the setting table, and the writing result is returned to the APP container.

[0031] The fixed value query unit is used to query the fixed value table based on the device unique identifier and fixed value name provided by the APP container as filter conditions, and return the query results to the APP container.

[0032] The fixed value deletion unit is used to first determine the identity of the APP container. If it is not the data generator, the request is rejected. If it has the setting permission, the data center deletes the corresponding record in the fixed value table based on the device unique identifier and fixed value name provided by the application as filtering conditions, and returns the deletion result to the APP container.

[0033] Optionally, the data interaction and management module includes a real-time data interaction and management module, an event data interaction and management module, and a frozen data interaction and management module;

[0034] The real-time data interaction and management module includes:

[0035] The real-time data writing unit first determines the identity of the APP container. If it is not the data generator, the request is rejected. If it has write permissions, it writes the device unique identifier, attribute name, value, data quality, and timestamp provided by the APP container into the real-time data table and returns the writing result to the APP container.

[0036] The real-time data query unit is used to query the real-time data table based on the device unique identifier and attribute name provided by the APP container, and return the query results to the APP container.

[0037] The event data interaction and management module includes:

[0038] The event logging unit is used to write the device unique identifier, event name, collection start time, collection end time, event start time, event end time, event source, whether the event needs to be actively reported, and event type provided by the APP container into the event logging table, and return the writing result to the APP container.

[0039] The event log query unit is used to query the event log table by using the time range of the event collection or occurrence provided by the application as a filter condition, and return the query results to the APP container.

[0040] The frozen data interaction and management module includes:

[0041] The freeze record writing unit is used to write the device unique identifier, freeze type, collection start time, collection end time, freeze time, attribute name, and attribute value provided by the APP container into the freeze record table, and return the writing result to the APP container.

[0042] The freeze record query unit is used to query the freeze record table by using the time range of collection or occurrence of the freeze provided by the APP container, the freeze type, and the query time interval as filtering conditions, and then returning the query results to the APP container.

[0043] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0044] This invention proposes a data center component design method, device, and system suitable for edge computing, which can achieve data interaction decoupling, allowing applications to interact with each other through the data center, avoiding private communication, and reducing the complexity of interaction management.

[0045] This invention proposes a data center component design method, device, and system suitable for edge computing, which can realize centralized data management, avoid the establishment of private databases by each application, ensure data security performance, and improve data usage efficiency and data interaction efficiency.

[0046] This invention proposes a data center component design method, device and system suitable for edge computing, which can achieve (3) data management standardization, standardization and normalization of the interfaces provided by the data center to the application, and improve management efficiency.

[0047] This invention proposes a data center component design method, device, and system suitable for edge computing, which can improve data interaction performance. For edge computing applications with high data refresh real-time requirements, API interfaces can be directly called, avoiding message format conversion and effectively improving the efficiency of data interaction. Attached Figure Description

[0048] To make the content of this invention easier to understand, the invention will be further described in detail below with reference to specific embodiments and accompanying drawings, wherein:

[0049] Figure 1 This is a diagram of the overall architecture of a data center according to an embodiment of the present invention;

[0050] Figure 2 This is a diagram of a data center message mode multi-process architecture according to an embodiment of the present invention;

[0051] Figure 3 This is a flowchart illustrating the message interaction process of a data center message mode according to an embodiment of the present invention.

[0052] Figure 4 This is a flowchart illustrating the data center initialization process according to an embodiment of the present invention.

[0053] Figure 5 This is a flowchart illustrating the device registration process according to an embodiment of the present invention. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the scope of protection of the invention.

[0055] The application principle of the present invention will be described in detail below with reference to the accompanying drawings.

[0056] To address the massive data access required by the power Internet of Things (IoT) and alleviate the load on cloud data processing while improving data real-time performance, the concept of edge computing has been proposed. Edge computing refers to applications initiating computation at the edge, closer to the object or data source, resulting in faster network service responses and meeting the industry's basic needs in real-time business, application intelligence, security, and privacy protection. Furthermore, to adapt to the data management requirements suitable for edge computing, this invention proposes an embedded data center design method. Based on a unified object modeling approach, a high-performance data center is designed, supporting cross-container interaction between applications through a unified data center. This method deconstructs the data interaction between edge computing applications, standardizes data interaction methods, and improves data interaction efficiency, data management capabilities, and data security.

[0057] The present invention provides a data center component design method suitable for edge computing, comprising the following steps:

[0058] Step (1) Construct a data channel between the APP container and the data center; the data interaction channel is a message-mode interaction channel or an API interface-mode interaction channel;

[0059] Step (2) Based on different business needs, construct the management modules and database contained in the data center. The management modules include a permission management module, a model interaction and management module, a device interaction and management module, a setpoint interaction and management module, and a data interaction and management module. The database includes a real-time database and a historical database. The real-time database and the historical database are respectively connected to each module in the management module. See details. Figure 1 .

[0060] In one specific embodiment of the present invention, when the data interaction channel is a message-mode interaction channel, the construction of the data channel between the APP container and the data center includes the following steps:

[0061] Create message processing subprocesses and business processing subthreads. The subprocesses and subthreads interact with each other through message queues. Create a main process to manage and monitor the subprocesses and subthreads.

[0062] Each message processing subprocess, upon receiving a JSON message from the APP container, first stores the JSON message in a buffer pool, then parses the JSON message corresponding to its business logic, and sends the parsed business data BLOB to the corresponding business processing sub-thread via a message queue for further business processing. Each business processing sub-thread performs its corresponding business processing, generates a processing result structure BLOB, and sends it to the corresponding message processing subprocess. Each message processing subprocess assembles a JSON string based on the received data and finally returns the result to the APP container. This approach ensures a reasonable and balanced message processing load across the subprocesses, maximizing the overall performance and reliability of the data center. The message processing flow is as follows: Figure 3 As shown.

[0063] Furthermore, the data center component design method also includes:

[0064] Establishing a SOCKET connection between each application container and the data center includes the following steps:

[0065] Each APP container acts as a client and establishes a SOCKET connection with the MQTT BROKER outside the APP container. The SOCKET connection is based on the multi-container bridging mechanism of the APP container itself. The APP container virtualizes a container bridge in the MQTT BROKER. When an APP container starts, it will be assigned an IP address called Container-IP according to the network segment of the container bridge. At the same time, the container bridge is set as the default gateway for each container.

[0066] As can be seen, when the data interaction channel is a message-based interaction channel, the data center exists as an independent service, and the JSON-based message content has good readability and isolation. The data center adopts a multi-process architecture, with each process handling different message types. Simultaneously, a real-time database based on shared memory is used for real-time data processing, improving overall processing efficiency. Furthermore, the message mode uses the MQTT protocol. Based on the MQTT publish-subscribe mechanism, applications and the data center interact with each other through an MQTT forwarding broker, enabling cross-container interaction between applications and the data center.

[0067] Since MQTT clients receive messages through callback functions and business processing requires I / O calls, exhibiting latency, message processing and business processing need to be asynchronously decoupled. Message processing and business processing are handled by different processes and threads. Communication between the message process and the business thread is achieved by transmitting structure sequences through a message queue, avoiding the latency caused by parsing and assembling JSON strings. Furthermore, the main process monitors and manages child processes and threads to ensure the program's robustness under abnormal conditions.

[0068] The data center categorizes messages into six types based on business logic: model, device, setpoint, real-time data (electricity meter real-time data, LTU real-time data, other device real-time data, etc.), event, and freeze. Sub-processes are designed to handle different message types according to the volume and frequency of messages sent by the app. Since most model and device message processing occurs during app initialization, model, device, and setpoint messages are processed by the same independent sub-process. Real-time data is processed by a separate sub-process, and event and freeze messages are each processed by a separate sub-process. The sub-process architecture is as follows: Figure 2 As shown.

[0069] The message transmission protocol uses MQTT (Message Queuing Telemetry Transport), a lightweight communication protocol based on the publish / subscribe model, built on top of TCP / IP. MQTT is a low-overhead, low-bandwidth instant messaging protocol. The message content format uses JSON (JavaScript Object Notation), a lightweight data-interchange format. It uses a text format completely independent of programming languages ​​to store and represent data. JSON has a concise and clear hierarchical structure, is easy to read and write, and is also easy for machines to parse and generate, effectively improving network transmission efficiency.

[0070] Message exchange between the data center and various applications is accomplished through the host machine's MQTT BROKER forwarding broker. The MQTT BROKER forwarding broker is based on SOCKET connections. Each application, acting as a client, establishes a SOCKET connection with the MQTT BROKER outside the container. This network connection is based on the container's own multi-container bridging mechanism. Each container virtualizes a container bridge on the host machine. When a container starts, it is assigned an IP address, called the Container-IP, based on the container bridge's network segment. The container bridge is also the default gateway for each container. Because containers within the same host machine all connect to the same bridge, containers can communicate directly with each other and with the host machine through their Container-IPs. Therefore, the MQTT BROKER is not constrained by container isolation. Furthermore, according to the MQTT protocol's publish / subscribe mechanism, as long as each application establishes a SOCKET connection with the MQTT BROKER, cross-container message forwarding can be performed between applications via the MQTT BROKER, enabling cross-container data exchange between applications.

[0071] In one specific embodiment of the present invention, when the data interaction channel is an API interface mode interaction channel, the construction of the data channel between the APP container and the data center includes the following steps:

[0072] When each app container is created, the cross-container shared directory is specified by specifying the cross-container shared directory parameter in the container creation command;

[0073] When the data center service starts, a file is created in the cross-container shared directory to store the database. This database file can then be accessed by applications within each container. Therefore, when applications call the data center API, they can interact across containers via the shared database file, enabling cross-container sharing of real-time database data. Because this mode eliminates the message transmission process, it significantly improves the data center's processing performance and application access efficiency.

[0074] As can be seen, when the data interaction channel is the API interface mode, by specifying a shared directory when creating the container and sharing the shared memory space of each APP container with the host machine, the APP containers can achieve cross-container data interaction and storage functions by directly calling the API interface.

[0075] Both the message mode interaction channel and the API interface mode interaction channel use a real-time database based on shared memory for real-time data processing. In the API mode, a shared memory and host machine sharing switch parameter is added to the container creation command to enable cross-container shared memory access, thereby realizing the sharing of real-time library data based on shared memory space among containers.

[0076] In one specific embodiment of the present invention, the real-time database uses a hash index as the indexing mechanism for the real-time database, and uses a static linked list to manage and allocate memory offset addresses during real-time database operations. By mapping the position index allocated by the static linked list during real-time database operations to the hash table of the real-time database, and storing the position index of the static linked list corresponding to the record in the hash table, when accessing a record, the real-time database finds the index value corresponding to the record from the hash table, and then directly calculates the memory address by multiplying the index by the length of each record.

[0077] The real-time database uses file-mapped shared memory based on the POSIX standard. The POSIX standard shared memory uses disk files for caching and synchronizes the disk files with the shared memory, thereby achieving power-off data preservation of real-time data. This method greatly improves the speed and performance of data exchange and meets the data storage needs in different scenarios.

[0078] In one specific embodiment of the present invention, the model interaction and management module includes:

[0079] The model setting unit stores the model name, property name, data type, minimum value, maximum value, step, report flag, and user-defined information in the model information table, and returns the setting results to the APP container. During model setting, the data center converts the record to be set and the existing record in the database into hash values ​​and compares them. If the record to be written is exactly the same as the existing record, the database write operation will not be performed, thus improving processing performance.

[0080] The model query unit is used to query all the settings information of the corresponding model based on the model name (model) provided by the application, and return the query results to the APP container;

[0081] The model deletion unit is used to delete the record in the model information table according to the model name (model) to be deleted provided by the APP container, and also delete the corresponding model data in the device information table and real-time data table. Finally, the setting result is returned to the APP container.

[0082] In one specific embodiment of the present invention, the device interaction and management module includes:

[0083] The device registration unit stores device information provided by the APP container, including the model name, device port, device address, custom description, device manufacturer ID, data reporting status (reportflag), and application name, into the device information table. It also generates a unique device identifier (devid) based on the model name, device port, device address, and custom description, and stores it in the device information table. After generating the unique device identifier, it queries the model table to retrieve all data attribute names for that model, and writes the unique device identifier and all attribute names as key-value pairs into the real-time data table. See [link to relevant documentation]. Figure 4 ;

[0084] The device unique identifier query unit is used to query the device unique identifier (devid) of the corresponding device based on the device model name (model), device port (port), device address (addr), and custom description (desc) provided by the APP container, and return the query result to the APP container;

[0085] The device registration relationship query unit is used to read all records in the device information table, classify and combine the query records by device model and device port, and return them to the APP container.

[0086] In one specific embodiment of the present invention, the fixed value interaction and management module includes:

[0087] The value setting unit is used to first determine the identity of the APP container. If it is not the data generator, the request is rejected. If it has the setting permission, it writes the unique identifier (devid), value name (paraname), value, and data type information provided by the APP container into the value table and returns the writing result to the APP container.

[0088] The value query unit is used to query the value table based on the device unique identifier (devid) and value name (paraname) provided by the APP container as filter conditions, and return the query results to the APP container.

[0089] The fixed value deletion unit first determines the identity of the APP container. If it is not the data generator, the request is rejected. If it has the setting permission, the data center deletes the corresponding record in the fixed value table based on the device unique identifier (devid) and fixed value name (paraname) provided by the application, and returns the deletion result to the APP container.

[0090] In one specific embodiment of the present invention, the data interaction and management module includes a real-time data interaction and management module, an event data interaction and management module, and a frozen data interaction and management module;

[0091] The real-time data interaction and management module includes:

[0092] The real-time data writing unit first determines the identity of the APP container. If it is not the data generator, the request is rejected. If it has write permissions, it writes the device unique identifier (devid), property name (propertyname), value (value), data quality (quality), and timestamp (timestamp) provided by the APP container into the real-time data table and returns the writing result to the APP container.

[0093] The real-time data query unit is used to query the real-time data table based on the device unique identifier (devid) and attribute name (propertyname) provided by the APP container, and return the query results to the APP container.

[0094] The event data interaction and management module includes:

[0095] The event logging unit is used to write the device unique identifier (devid), event name (eventname), collection start time (startgathertime), collection end time (endgathertime), event start time (starttime), event end time (endtime), event source (occuretime), whether the event needs to be actively reported (reportflag), and event type (eventtype) provided by the APP container into the event logging table, and return the writing results to the APP container;

[0096] The event log query unit is used to query the event log table by using the time range of the event collection or occurrence provided by the application as a filter condition, and return the query results to the APP container.

[0097] The frozen data interaction and management module includes:

[0098] The freeze record writing unit is used to write the device unique identifier (devid), freeze type (frozentype), collection start time (startgathertime), collection end time (endgathertime), freeze time (frozentime), attribute name (propertyname), and attribute value (value) provided by the APP container into the freeze record table, and return the writing result to the APP container.

[0099] The freeze record query unit is used to query the freeze record table by using the time range of collection or occurrence of the freeze provided by the APP container, the freeze type, and the query time interval as filtering conditions, and then returning the query results to the APP container.

[0100] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A data center component design method suitable for edge computing, characterized in that, include: Establish a data channel between the APP container and the data center; the data channel is either a message-mode interaction channel or an API interface-mode interaction channel. Based on different business needs, the data center includes management modules and databases. The management modules include a permission management module, a model interaction and management module, a device interaction and management module, a setpoint interaction and management module, and a data interaction and management module. The database includes a real-time database and a historical database. The real-time database and the historical database are respectively connected to each module in the management modules. When the data channel is a message-based interaction channel, the construction of the data channel between the APP container and the data center includes the following steps: Create message processing subprocesses and business processing subthreads. The subprocesses and subthreads interact with each other through message queues. Create a main process to manage and monitor the subprocesses and subthreads. Each message processing subprocess, upon receiving a JSON message from the APP container, first stores the JSON message in a buffer pool, then parses the JSON message corresponding to its business, and sends the parsed business data BLOB to the corresponding business processing sub-thread through a message queue for subsequent business processing. Each business processing sub-thread performs the corresponding business processing, generates a processing result structure BLOB, and sends it to the corresponding message processing subprocess. Each message processing subprocess assembles a JSON string based on the received data and finally returns the result to the APP container. When the data channel is an API interface interaction channel, the construction of the data channel between the APP container and the data center includes the following steps: When each app container is created, the cross-container shared directory is specified by specifying the cross-container shared directory parameter in the container creation command; When the service is started in the data center, a file is created in the cross-container shared directory to store the database in the data center.

2. The data center component design method for edge computing according to claim 1, characterized in that: The data center component design method also includes: Establishing a SOCKET connection between each application container and the data center includes the following steps: Each APP container acts as a client and establishes a SOCKET connection with the MQTT BROKER outside the APP container. The SOCKET connection is based on the multi-container bridging mechanism of the APP container itself. The APP container virtualizes a container bridge in the MQTT BROKER. When an APP container starts, it will be assigned an IP address called Container-IP according to the network segment of the container bridge. At the same time, the container bridge is set as the default gateway for each container.

3. The data center component design method for edge computing according to claim 1, characterized in that: The real-time database uses a hash index as its indexing mechanism and employs a static linked list to manage and allocate memory offset addresses during real-time database operations. This is achieved by mapping the position index of the static linked list allocated during real-time database operations to the hash table of the real-time database and storing the corresponding position index of the static linked list in the hash table.

4. The data center component design method for edge computing according to claim 1, characterized in that: The real-time database uses POSIX-standard file-mapped shared memory, which uses disk files for caching and synchronizes the disk files with the shared memory.

5. The data center component design method for edge computing according to claim 1, characterized in that, The model interaction and management module includes: The model setting unit is used to store the model name, attribute name, data type, minimum value, maximum value, step size, reporting identifier, and user-defined information of the model into the model information table, and return the setting results to the APP container. The model query unit is used to query all the settings information of the corresponding model based on the model name provided by the application, and return the query results to the APP container. The model deletion unit is used to delete the record in the model information table according to the model name to be deleted provided by the APP container, and also delete the corresponding model data in the device information table and real-time data table. Finally, the setting result is returned to the APP container.

6. The data center component design method for edge computing according to claim 1, characterized in that, The device interaction and management module includes: The device registration unit is used to store device information provided by the application, such as model name, device port, device address, custom description, device manufacturer ID, whether data is reported, and application name, into the device information table; it is also used to generate a unique identifier for the device based on the model name, device port, device address, and custom description, and store it in the device information table. After generating the unique identifier for the device, it retrieves all data attribute names of the model by querying the model table, and writes the unique identifier for the device and all attribute names as key-value pairs into the real-time data table. The device unique identifier query unit is used to query the device unique identifier of the corresponding device based on the device model name, device port, device address and custom description provided by the APP container, and return the query result to the APP container. The device registration relationship query unit is used to read all records in the device information table, classify and combine the query records by device model and device port, and return them to the APP container.

7. A data center component design method suitable for edge computing according to claim 1, characterized in that, The fixed-value interaction and management module includes: The setting unit first determines the identity of the APP container. If it is not the data generator, the request is rejected. If it has setting permissions, the unique device identifier, setting name, value, and data type information provided by the APP container are written into the setting table, and the writing result is returned to the APP container. The fixed value query unit is used to query the fixed value table based on the device unique identifier and fixed value name provided by the APP container as filter conditions, and return the query results to the APP container. The fixed value deletion unit is used to first determine the identity of the APP container. If it is not the data generator, the request is rejected. If it has the setting permission, the data center deletes the corresponding record in the fixed value table based on the device unique identifier and fixed value name provided by the application as filtering conditions, and returns the deletion result to the APP container.

8. A data center component design method suitable for edge computing according to claim 1, characterized in that, The data interaction and management module includes a real-time data interaction and management module, an event data interaction and management module, and a frozen data interaction and management module. The real-time data interaction and management module includes: The real-time data writing unit first determines the identity of the APP container. If it is not the data generator, the request is rejected. If it has write permissions, it writes the device unique identifier, attribute name, value, data quality, and timestamp provided by the APP container into the real-time data table and returns the writing result to the APP container. The real-time data query unit is used to query the real-time data table based on the device unique identifier and attribute name provided by the APP container, and return the query results to the APP container. The event data interaction and management module includes: The event logging unit is used to write the device unique identifier, event name, collection start time, collection end time, event start time, event end time, event source, whether the event needs to be actively reported, and event type provided by the APP container into the event logging table, and return the writing result to the APP container. The event log query unit is used to query the event log table by using the time range of the event collection or occurrence provided by the application as a filter condition, and return the query results to the APP container. The frozen data interaction and management module includes: The freeze record writing unit is used to write the device unique identifier, freeze type, collection start time, collection end time, freeze time, attribute name, and attribute value provided by the APP container into the freeze record table, and return the writing result to the APP container. The freeze record query unit is used to query the freeze record table using the time range of collection or occurrence of the freeze provided by the APP container, the freeze type, and the query time interval as filtering conditions, and then return the query results to the APP container.

Images