Edge server data management method and device, equipment and storage medium

Abstract

The invention provides an edge server data management method and device, equipment and a storage medium, and the method is executed through an edge server and comprises the steps that corresponding channel information is initialized according to data to be acquired, and the channel information comprises a physical channel, a logic channel and a data type; acquiring data of the terminal equipment through the physical channel, and storing the data in a cache; storing the data in the cache into a corresponding logic channel according to the data type; and providing data support for the cloud according to a communication protocol configured in the edge server and a data strategy associated with the communication protocol, so that the cloud forwards the data in the logic channel. According to the invention, the problem of interface difference in the interaction process of industrial data and Internet of Things data can be solved, the real-time performance of data interaction is improved, and the diversity of data management is enriched.

Description

Technical Field

[0001] The present application relates to the field of industrial cloud service technology, and in particular to an edge server data management method and apparatus, equipment, and storage medium. Background Art

[0002] With the rapid development of industrialization, more and more manufacturers are in urgent need of data interaction between industrial data and IoT data to analyze and monitor the working status of terminal equipment in real time and conduct reverse control. However, there are large differences between industrial data and general IoT data in terms of data interface and data real-time performance, which leads to challenges in data interaction. Industrial data generally adopts protocols such as EasyCAT (Ethernet for Control Automation Technology), Modbus, and OPCUA (Open Platform Communications Unified Architecture), while IoT data generally adopts protocols such as MQTT (Message Queuing Telemetry Transport), HTTP (HyperText Transfer Protocol), and COAP (Constrained Application Protocol). Industrial data has high requirements for delay and acquisition rate, some of which are even around 1 millisecond. The delay of IoT data is within an acceptable range of less than 200ms, so it is more difficult to transmit industrial data with higher frequency on the Internet. At the same time, the data interaction process has different requirements for different data. Some data requires real-time performance, while some data requires continuous and loss-free performance. Although the existing technology has solved some of the above problems to a certain extent, it still has shortcomings in real-time performance, interface richness and data management diversity. Summary of the invention

[0003] In view of this, the present application proposes an edge server data management method and device, equipment, and storage medium to solve the interface difference problem in the interaction process between industrial data and Internet of Things data, improve the real-time performance of data interaction, and enrich the diversity of data management.

[0004] In a first aspect, the present application provides an edge server data management method, which is executed by an edge server, and the method includes:

[0005] Initialize corresponding channel information according to the data to be acquired, where the channel information includes a physical channel, a logical channel, and a data type;

[0006] Acquire the data of the terminal device through the physical channel and store it in the cache;

[0007] Classifying the data in the cache according to the data type and storing them in corresponding logical channels respectively;

[0008] Data support is provided to the cloud according to the communication protocol configured in the edge server and the data policy associated with the communication protocol, so that the cloud forwards the data in the logical channel.

[0009] From the above, the edge server data management method provided by the present application realizes efficient and orderly management of data in the edge server through the steps of initializing channel information, acquiring and caching data, classifying and storing data, and providing data support to the cloud. Among them, the physical channel in the channel information represents the physical path of data transmission. The edge server can obtain the data of the terminal device through the physical channel. The logical channel is a logical path divided for different data types or business scenarios on the basis of the physical channel. The edge server can classify the acquired data according to the data type and store them in the corresponding logical channel respectively. The edge server can also provide data support to the cloud through the logical channel according to its configured communication protocol and data strategy, so that the cloud can forward the data in the logical channel to provide it to the application end. Through this application, it is ensured that data can be accurately and timely transmitted to the cloud, providing strong support for data processing and analysis in the cloud. The method has the advantages of high efficiency, flexibility and reliability, and is suitable for a variety of application scenarios and needs.

[0010] Optionally, the channel information further includes acquisition frequency, channel association information and channel association algorithm, and after acquiring the data of the terminal device through the physical channel and storing it in the cache, the method further includes:

[0011] classifying the data in the cache into high-frequency data and low-frequency data according to the acquisition frequency;

[0012] storing the high-frequency data in the cache to a local file according to the channel association information and the channel association algorithm;

[0013] The low-frequency data in the cache is stored in a local file and a real-time database according to the channel association information and the channel association algorithm.

[0014] From the above, this method not only considers the physical and logical properties of the channel, but also introduces the acquisition frequency and channel association algorithm, so that different types of data can be processed more finely. Specifically, the acquisition cycle or frequency of the data can be defined by the acquisition frequency to distinguish high-frequency data from low-frequency data. The logic of data processing and storage can also be defined by the channel association algorithm, and the storage method of data in local files and databases can be guided by the channel association information. According to the acquisition frequency, the edge server can divide the data in the cache into high-frequency data and low-frequency data. For high-frequency data, due to its high acquisition frequency, real-time data interaction is not required. It can be stored locally according to the channel association information and channel association algorithm for subsequent data analysis. For low-frequency data, it can be stored in local files and real-time databases according to the channel association information and channel association algorithm, so that it can be called through the real-time database when needed for further analysis. By introducing the acquisition frequency, channel association information and channel association algorithm, the data management of the edge server can be more perfect, providing more comprehensive support for different application scenarios.

[0015] Optionally, the configured communication protocol includes at least one of the following:

[0016] MQTT protocol, configuration information includes Broker server address and port number, MQTT communication protocol version, authentication method, user name and password;

[0017] HTTP protocol, configuration information includes communication port number, communication protocol version, authentication method and user name;

[0018] OPCUA protocol, configuration information includes communication port number, communication protocol version, authentication method and user name;

[0019] COAP protocol, configuration information includes communication port number, communication protocol version, authentication method and user name.

[0020] From the above, the edge server can be configured with multiple communication protocols to support multiple communication interfaces. Specifically, the MQTT protocol is a lightweight message transmission protocol based on the publish / subscribe model. The HTTP protocol is an application layer protocol used to transmit hypertext on the Web or transmit data in the Internet of Things. The OPC UA protocol is a communication protocol for the industrial automation field, which aims to provide secure and reliable data exchange and interoperability. The CoAP protocol is a lightweight application layer protocol designed specifically for the Internet of Things and is suitable for resource-constrained devices. By configuring these communication protocols and their related information, the edge server can flexibly transmit and interact with the cloud or other servers to meet the diverse needs of Internet of Things applications.

[0021] Optionally, each communication protocol is associated with only one data policy, which includes a real-time policy or a continuity policy.

[0022] From the above, according to the communication protocol configured above, appropriate data strategies can be customized for different communication protocols according to the characteristics of the data and transmission requirements. The data strategy includes a real-time strategy or a continuity strategy. The real-time strategy emphasizes the immediacy and accuracy of the data, and the continuity strategy focuses on the integrity and continuity of the data. Through the configured communication protocol and data strategy, the edge server can manage and transmit data more effectively to meet the needs of different application scenarios.

[0023] Optionally, the cloud forwarding the data in the logical channel includes:

[0024] The cloud acts as a gateway and forwards the data in the logical channel to the user end in an active push or response manner.

[0025] From the above, in the IoT architecture, the cloud usually acts as a bridge connecting the edge server and the user end, that is, the gateway, responsible for receiving, processing and forwarding data from the edge server to ensure that the data can be accurately delivered to the user end. The edge server can provide data support to the cloud through the configured communication protocol and data strategy. The cloud can process the data in the logical channel appropriately and send it to the user end by actively pushing or responding, thereby meeting the diverse needs of IoT applications.

[0026] Optionally, the forwarding of the data in the logical channel to the user end in an active push or response manner includes:

[0027] According to the configured MQTT protocol or OPC UA protocol, forward the data in the logical channel to the user end in an active push manner; and / or,

[0028] According to the configured HTTP protocol or COAP protocol, the data in the logical channel is forwarded to the user end in a response manner.

[0029] From the above, in actual applications, the cloud can choose the appropriate forwarding strategy based on factors such as data characteristics, user requirements, and network conditions. For example, for data with high real-time requirements, you can choose to use MQTT or OPC UA protocol for active push; for data obtained on demand, you can choose to use HTTP or CoAP protocol for response.

[0030] Optionally, also include:

[0031] The user end configures the communication protocol and data policy through a Web program, so that the cloud performs forwarding of the data according to the configured communication protocol and data policy.

[0032] From the above, the user side configures the communication protocol and data policy functions through the Web program, so that the system can be flexibly configured according to different application scenarios and needs. This not only enables the system to adapt to different application scenarios and needs, but also lowers the system's usage threshold and improves the system's efficiency and performance.

[0033] In a second aspect, the present application provides an edge server data management device, including:

[0034] An initialization module, used to initialize corresponding channel information according to the data to be acquired, the channel information including physical channel, logical channel, and data type;

[0035] An acquisition module, used for acquiring data of a terminal device through the physical channel and storing the data in a cache;

[0036] A processing module, used for classifying the data in the cache according to the data type, and storing them in corresponding logical channels respectively;

[0037] The sending module is used to provide data support to the cloud according to the communication protocol configured in the edge server and the data policy associated with the communication protocol, so that the cloud can forward the data in the logical channel.

[0038] In a third aspect, the present application provides a computing device, the computing device comprising:

[0039] processor;

[0040] A memory for storing one or more programs;

[0041] When the one or more programs are executed by the processor, the processor implements the above-mentioned edge server data management method.

[0042] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned edge server data management method when executed by a computer.

[0043] These and other aspects of the present application will become more apparent from the following description of the embodiment(s). BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 A flowchart of an edge server data management method provided in an embodiment of the present application;

[0045] Figure 2 A schematic diagram of a data flow from a terminal to an edge server provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of converting a physical channel and a logical channel provided in an embodiment of the present application;

[0047] Figure 4 A schematic diagram of a data flow from a data source to an application program provided in an embodiment of the present application;

[0048] Figure 5 A structural diagram of an edge server data management device provided in an embodiment of the present application;

[0049] Figure 6 A structural diagram of a computing device provided in an embodiment of the present application.

[0050] It should be understood that the size and shape of each block diagram in the above structural diagram are for reference only and should not constitute an exclusive interpretation of the embodiments of the present application. The relative positions and inclusion relationships between the blocks presented in the structural diagram are only schematic representations of the structural associations between the blocks, and do not limit the physical connection methods of the embodiments of the present application. DETAILED DESCRIPTION

[0051] The technical solution provided by the present application is further described below with reference to the accompanying drawings and examples. It should be understood that the system structure and business scenarios provided in the examples of the present application are mainly to illustrate the possible implementation methods of the technical solution of the present application and should not be interpreted as the only limitation on the technical solution of the present application. It is known to those of ordinary skill in the art that with the evolution of the system structure and the emergence of new business scenarios, the technical solution provided by the present application is also applicable to similar technical problems.

[0052] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present application. In case of any inconsistency, the meaning described in this specification or the meaning derived from the contents recorded in this specification shall prevail. In addition, the terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0053] The embodiment of the present application proposes an edge server data management method to solve the interface difference problem in the interaction process between industrial data and Internet of Things data, improve the real-time performance of data interaction, and enrich the diversity of data management.

[0054] like Figure 1 As shown, an edge server data management method provided in an embodiment of the present application can be executed by an edge server. The edge server serves as a bridge between a terminal device and the cloud. It is not only responsible for collecting data from the terminal device, but also responsible for the preliminary processing, conversion and transmission of the data, thereby realizing data interaction between the terminal device, the edge server and the cloud. Figure 1As shown, the method includes:

[0055] S110: Initialize corresponding channel information according to the data to be acquired.

[0056] In this step, before obtaining the data of the terminal device, the channel information between the terminal device, the edge server and the cloud can be initialized first. The channel information may include physical channels, logical channels and data types. The physical channel is the smallest unit used when the terminal device and the edge server interact with each other. It represents a specific collection point, including basic information such as channel number, data type, point location, and collection frequency. The edge server can collect data from the terminal device through the physical channel for subsequent processing. The logical channel is an identifier used when the edge server interacts with the cloud. It has a specific meaning for the upper-layer application of the cloud and can help the application better understand and process the data. The edge server encapsulates and converts the data of the physical channel through the logical channel to make it conform to the data format and requirements of the cloud application. The data type is used to identify the content or format of the data, such as temperature data, humidity data, image data, etc. The edge server can classify the acquired data according to the data type for subsequent further storage or forwarding.

[0057] In some embodiments, the initialized channel information also includes acquisition frequency, channel association information and channel association algorithm. Specifically, the acquisition frequency can be used to define the data acquisition period or frequency to distinguish high-frequency data from low-frequency data. The channel association algorithm can also be used to define the logic of data processing and storage, and the channel association information can be used to guide the storage method of data in local files and real-time databases.

[0058] S120: Acquire data of the terminal device through the physical channel and store it in a cache.

[0059] Based on the above-mentioned initialized physical channel, the edge server can obtain data from the terminal device (such as sensors, cameras, etc.) through the physical channel, and in order to improve the efficiency of data processing, the obtained data can be first stored in the cache. The cache has the characteristics of fast reading and writing speed and moderate capacity, and can temporarily store a large amount of data for subsequent processing.

[0060] S130: Classify the data in the cache according to the data type, and store them in corresponding logical channels respectively.

[0061] Based on the above initialized data types, the edge server can classify the data in the cache according to the data type, and store the classified data in the corresponding logical channels respectively, to ensure that the data can be stored and managed in an orderly and efficient manner.

[0062] In some embodiments, based on the acquisition frequency, channel association information and channel association algorithm in the above-mentioned channel information, the edge server can also classify the data in the cache into high-frequency data and low-frequency data according to the acquisition frequency. For high-frequency data, due to its high acquisition frequency, no real-time data interaction is required, and it can be locally stored according to the channel association information and the channel association algorithm for subsequent data analysis. For low-frequency data, it can be stored in local files and real-time databases respectively according to the channel association information and the channel association algorithm, so that it can be called through the real-time database when needed for further analysis.

[0063] S140: Providing data support to the cloud according to the communication protocol configured in the edge server and the data policy associated with the communication protocol, so that the cloud forwards the data in the logical channel.

[0064] In this step, the edge server also configures multiple communication protocols and associates a data strategy for each communication protocol. Based on the configured communication protocols and data strategies, the edge server transmits the data in the logical channel to the cloud, providing data support for the cloud so that the cloud can forward, process and analyze the data according to business needs.

[0065] The edge server data management method provided in the embodiment of the present application realizes efficient and orderly management of data in the edge server through the steps of initializing channel information, acquiring and caching data, classifying and storing data, and providing data support to the cloud. The physical channel in the channel information represents the physical path of data transmission. The edge server can obtain the data of the terminal device through the physical channel. The logical channel is a logical path divided for different data types or business scenarios on the basis of the physical channel. The edge server can classify the acquired data according to the data type and store them in the corresponding logical channel respectively. The edge server can also provide data support to the cloud through the logical channel according to the communication protocol and data strategy configured by it, so that the cloud can forward the data in the logical channel to provide it to the application end. Through this application, it is ensured that data can be accurately and timely transmitted to the cloud, providing strong support for data processing and analysis in the cloud. The method has the advantages of high efficiency, flexibility and reliability, and is suitable for a variety of application scenarios and needs.

[0066] Refer to the following Figure 2-Figure 4 The edge server data management method provided in the embodiment of the present application is described in detail.

[0067] Figure 2 FIG. 1 is a schematic diagram of a data flow from a terminal to an edge server provided in an embodiment of the present application, referring to FIG. Figure 2As shown, the data stream interaction end includes a terminal device 210, an edge server 220 and a cloud 230. The terminal device 210 communicates with the edge server 220 through a physical channel, and the edge server 220 communicates with the cloud 230 through a logical channel.

[0068] Before the data flow interaction, the channel information between the edge server 220 and the terminal device 210, and between the edge server 220 and the cloud 230 is configured in advance and initialized. The initialized channel information includes the physical channel, the logical channel, the data type, the acquisition frequency, the channel association information and the channel association algorithm. The physical channel is the smallest unit used when the terminal device 210 and the edge server 220 interact with each other for data. It represents the specific acquisition point, including the basic information such as the channel number, the data type, the point location, and the acquisition frequency. The logical channel is the identifier used when the edge server 220 interacts with the cloud 230 for data. The data type is used to identify the content or format of the data. The acquisition frequency defines the acquisition period or frequency of the data to distinguish between high-frequency data and low-frequency data. The channel association algorithm defines the logic of data processing and storage, and guides the storage method of data in local files and real-time databases through channel association information.

[0069] After completing the initialization of the channel information, the edge server 220 can obtain the data in the terminal device 210 through the physical channel and store it in the cache for subsequent processing.

[0070] In some embodiments, for the data in the cache, the edge server 220 may perform data storage processing according to the acquisition frequency, channel association information, and channel association algorithm in the channel information. The edge server 220 may classify the data in the cache into high-frequency data and low-frequency data according to the acquisition frequency. For high-frequency data (such as vibration data acquired at high speed), due to its high acquisition frequency, no real-time data interaction is required, and local storage may be performed according to the channel association information and the channel association algorithm to ensure fast access and real-time processing of high-frequency data. For low-frequency data (such as monitoring and management data acquired at low speed), it may be stored in a local file and a real-time database respectively according to the channel association information and the channel association algorithm. The real-time database provides a more durable and scalable storage solution, which is convenient for subsequent data analysis and processing. For the low-frequency data, the edge server 220 may also be divided into high-real-time data and high-continuity data according to different needs. High-real-time data pays more attention to the real-time nature of the data and obtains the state of the data faster, while high-continuity data pays more attention to the data information in each transition state can be obtained.

[0071] In some embodiments, Figure 3As shown, after the edge server 220 obtains the data of each collection point of the terminal device 210 through the physical channel, it is stored in its cache. For the data in the cache, the edge server 220 can also classify the data in the cache according to the data type (for example, fan temperature, fan speed and fan power generation), and store the classified data in the corresponding logical channels respectively, and forward the data in each logical channel to the cloud 230 according to the configured data interface (communication protocol and data strategy). In terms of data interface, the edge server can provide multiple communication protocols, and associate a specific data strategy with each communication protocol. The communication protocol and its configuration information include:

[0072] MQTT (Message Queuing Telemetry Transport) protocol is a lightweight message transmission protocol based on publish / subscribe mode, which is widely used in the field of Internet of Things. Its configuration information includes:

[0073] Broker server address and port number: specify the IP address and port number of the MQTT Broker (message broker) for establishing connections and transmitting messages;

[0074] MQTT communication protocol version: Select the version of the MQTT protocol, such as MQTT 3.1.1 or MQTT 5.0, to ensure compatibility and feature support;

[0075] Authentication method: Set the authentication method used to verify the client identity, such as username and password, TLS / SSL certificate, etc.

[0076] Username and Password: Provide a username and password for authentication, ensuring that only authorized clients can connect to the Broker server.

[0077] HTTP (HyperText Transfer Protocol) is an application layer protocol used to transmit hypertext and other content on the Web. In the Internet of Things, HTTP is also commonly used for data transmission. Its configuration information includes:

[0078] Communication port number: Specify the port number that the HTTP server listens on. The default value is 80 (HTTP) or 443 (HTTPS).

[0079] Communication protocol version: Select the HTTP protocol version, such as HTTP / 1.1 or HTTP / 2, to optimize performance and compatibility;

[0080] Authentication method: Set the authentication method used to verify the identity of the client or server, such as basic authentication, digest authentication, or OAuth;

[0081] Username: Provide a username for authentication, ensuring that only authorized clients can access the server.

[0082] OPCUA (OLE for Process Control Unified Architecture) protocol is a communication protocol for industrial automation, designed to provide secure, reliable data exchange and interoperability. Its configuration information includes:

[0083] Communication port number: Specify the port number that the OPC UA server listens on, usually 4840;

[0084] Communication protocol version: Select the version of the OPC UA protocol to ensure compatibility and functional support;

[0085] Authentication method: Set the authentication method used to verify the identity of the client or server, such as certificate authentication, user name and password, etc.

[0086] Username: Provide a username for authentication, ensuring that only authorized clients can access the server.

[0087] COAP (Constrained Application Protocol) is a lightweight application layer protocol designed for the Internet of Things. It is based on the REST architecture and is suitable for devices with limited resources. Its configuration information includes:

[0088] Communication port number: specify the port number that the CoAP server listens on, usually 5683;

[0089] Communication protocol version: Select the version of the CoAP protocol to ensure compatibility and function support;

[0090] Authentication method: Set the authentication method used to verify the identity of the client or server, such as DTLS (Datagram Transport Layer Security) certificate authentication;

[0091] Username: Although the CoAP protocol itself does not directly support username and password authentication, a similar authentication mechanism can be implemented at the application layer. The username is listed in this configuration information to be consistent with other protocols and to prompt developers to consider using the username when implementing authentication at the application layer.

[0092] In this embodiment, each communication protocol is associated with only one data policy based on its characteristics, data requirements, network conditions, and other factors. The data policy refers to the rules or methods that define how to process and transmit data. In the edge server data management scenario, the data policy can include real-time policy and continuity policy. The data policies associated with the above communication protocols are as follows:

[0093] MQTT protocol: Due to its low overhead, low latency, and easy scalability, the MQTT protocol is often associated with real-time strategies to ensure that data with high real-time requirements, such as sensor data, can be transmitted to the cloud for processing as quickly as possible;

[0094] HTTP protocol: The HTTP protocol is suitable for transmitting large blocks of data or files, and supports persistent connections and error handling mechanisms. Therefore, it is often associated with continuity strategies to ensure data integrity and reliability.

[0095] OPCUA protocol: The OPCUA protocol is designed for industrial automation and provides strong security and interoperability. Depending on the characteristics and requirements of the data, the OPCUA protocol can be associated with real-time strategies or continuity strategies to meet the needs of different application scenarios.

[0096] CoAP protocol: The CoAP protocol is suitable for resource-constrained IoT devices and supports a simple request / response model. Since the CoAP protocol is usually used to transmit small data packets and status information, it is often associated with real-time strategies to ensure the timeliness and accuracy of data.

[0097] Based on the communication protocol and data strategy configured above, the edge server 220 can send the data in the logical channel to the cloud 230, and provide data support for the cloud 230, so that the cloud 230 can act as a gateway and select a suitable forwarding strategy according to factors such as the characteristics of the data, the needs of the user end, and network conditions. For example, for data with high real-time requirements, you can choose to use the MQTT protocol or the OPCUA protocol for active push; and for data obtained on demand, you can choose to use HTTP or COAP protocol for response. Among them, the active push method means that after the cloud receives the data sent by the edge server, it immediately forwards it to the user end without waiting for the user end's request. This method is suitable for application scenarios with high real-time requirements, such as real-time monitoring, remote control, etc. Through active push, the user end can obtain the latest data in real time, so as to respond or adjust in time. The response method means that after the cloud receives the request from the user end, it obtains the corresponding data from the edge server according to the content of the request and forwards it to the user end. This method is suitable for scenarios where data is obtained on demand, such as data query, historical data analysis, etc. Through the response method, the user end can obtain the required data according to actual needs, avoiding unnecessary data transmission and resource waste.

[0098] Figure 4 The data flow diagram from a data source to an application provided by an embodiment of the present application is shown. In the edge server data management system, the user can configure the communication protocol and data strategy through the Web program so that the edge server provides data support to the cloud according to the configured communication protocol and data strategy, and finally reaches the application end. Through the Web program interface, the user can select a suitable communication protocol from the predefined protocol list according to actual needs, such as MQTT protocol, OPCUA protocol, HTTP protocol or COAP protocol, etc. After selecting the protocol, the user needs to further set the relevant parameters of the communication protocol, such as server address, port number, authentication information, etc. These parameters will ensure that the communication between the user end and the cloud can proceed smoothly. After the configuration of the communication protocol is completed, the user can select a suitable data strategy according to the characteristics and needs of the data, such as real-time strategy or continuity strategy. The real-time strategy emphasizes the immediacy and accuracy of the data and is suitable for time-sensitive data; while the continuity strategy focuses on the integrity and continuity of the data and is suitable for data that needs to be stored and analyzed for a long time.

[0099] After the user completes the configuration of the communication protocol and data policy through the Web program, the edge server will establish a connection with the cloud according to the communication protocol configured by the user, and provide data support to the cloud according to the data policy associated with the communication protocol, so that the cloud can forward the data as a gateway. For real-time policies, the cloud will forward the data to the user as soon as possible; for continuity policies, the cloud will ensure the integrity and sequence of the data, and retransmit or reissue it when necessary. Exemplarily, the edge server can provide data support for the cloud according to the configured MQTT protocol and real-time policy, OPCUA protocol and continuity policy, so that the cloud can push the data provided by the edge server to the application side by active push, and can also provide data support for the cloud according to the configured HTTP protocol and real-time policy, COAP protocol and continuity policy, so that the cloud can send the data provided by the edge server to the application side by response.

[0100] In summary, the edge server data management method provided in the embodiment of the present application realizes efficient and orderly management of data in the edge server through the steps of initializing channel information, acquiring and caching data, classifying and storing data, and providing data support to the cloud. The method has the advantages of high efficiency, flexibility and reliability, and is suitable for a variety of application scenarios and needs. In addition, the method also provides a user-friendly Web program interface to facilitate the user to flexibly configure the communication protocol and data strategy, thereby providing great flexibility and configurability for the edge server data management system, which not only enables the system to adapt to different application scenarios and needs, but also reduces the use threshold of the system, improves the efficiency and performance of the system, and thus meets the interaction needs of industrial data and Internet of Things data in industrial scenarios.

[0101] like Figure 5 As shown, the embodiment of the present application provides an edge server data management device, which can be used to implement the above Figure 1-Figure 4 Any of the steps shown and their optional embodiments. Figure 5 As shown, the device includes an initialization module 410, an acquisition module 420, a processing module 430 and a sending module 440;

[0102] Among them, the initialization module 410 is used to initialize the corresponding channel information according to the data to be acquired, and the channel information includes a physical channel, a logical channel, and a data type; the acquisition module 420 is used to acquire the data of the terminal device through the physical channel and store it in a cache; the processing module 430 is used to classify the data in the cache according to the data type, and store them in corresponding logical channels respectively; the sending module 440 is used to provide data support to the cloud according to the communication protocol configured in the edge server and the data policy associated with the communication protocol, so that the cloud can forward the data in the logical channel.

[0103] It should be understood that the device or module in the embodiment of the present application can be implemented by software, for example, it can be implemented by a computer program or instruction having the above functions, and the corresponding computer program or instruction can be stored in a memory inside the terminal, and the processor reads the corresponding computer program or instruction inside the memory to implement the above functions. Alternatively, the device or module in the embodiment of the present application can also be implemented by hardware. Alternatively, the device or module in the embodiment of the present application can also be implemented by a combination of a processor and a software module.

[0104] It should be understood that the processing details of the device or module in the embodiment of the present application can refer to Figure 1-Figure 4 The related descriptions of the illustrated embodiment and related extended embodiments will not be repeated in the embodiments of the present application.

[0105] Figure 6 5 is a structural diagram of a computing device 500 provided in an embodiment of the present application. The computing device 500 includes: a processor 510 , a memory 520 , a communication interface 530 , and a bus 540 .

[0106] It should be understood that Figure 6 The communication interface 530 in the computing device 500 shown may be used to communicate with other devices.

[0107] The processor 510 may be connected to a memory 520. The memory 520 may be used to store the program code and data. Therefore, the memory 520 may be a storage unit inside the processor 510, or an external storage unit independent of the processor 510, or a component including a storage unit inside the processor 510 and an external storage unit independent of the processor 510.

[0108] Optionally, the computing device 500 may further include a bus 540. The memory 520 and the communication interface 530 may be connected to the processor 510 via the bus 540. The bus 540 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus 540 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 The fact that only one line is used in the diagram does not mean that there is only one bus or only one type of bus.

[0109] It should be understood that in the embodiment of the present application, the processor 510 may adopt a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. Alternatively, the processor 510 may adopt one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiment of the present application.

[0110] The memory 520 may include a read-only memory and a random access memory, and provides instructions and data to the processor 510. A portion of the processor 510 may also include a nonvolatile random access memory. For example, the processor 510 may also store information on the device type.

[0111] When the computing device 500 is running, the processor 510 executes the computer-executable instructions in the memory 520 to perform the operating steps of the above method.

[0112] It should be understood that the computing device 500 according to the embodiment of the present application can correspond to the corresponding subjects in the methods according to the embodiments of the present application, and the above-mentioned other operations and / or functions of each module in the computing device 500 are respectively for realizing the corresponding processes of each method of the present embodiment. For the sake of brevity, they will not be repeated here.

[0113] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0114] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

[0117] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0118] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0119] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, it is used to execute the above method, which includes at least one of the solutions described in the above embodiments.

[0120] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive lists) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing programs, which can be used by instruction execution systems, devices or devices or used in combination with them.

[0121] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0122] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0123] Computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).

[0124] It should be noted that the embodiments described in the present application are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application usually described and shown in the drawings can be arranged and designed in various different configurations. Therefore, the above detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0125] The words "first, second, third, etc." or module A, module B, module C and other similar terms in the specification and claims are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that the specific order or sequence can be interchanged where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0126] In the above description, the numbers representing the steps involved do not necessarily mean that the steps will be executed. Intermediate steps may be included or replaced by other steps. The order of the previous and next steps may be interchanged or executed simultaneously if permitted.

[0127] The term "comprising" as used in the description and claims should not be interpreted as being limited to what is listed thereafter; it does not exclude other elements or steps. Therefore, it should be interpreted as specifying the presence of the features, integers, steps or components mentioned, but does not exclude the presence or addition of one or more other features, integers, steps or components and groups thereof. Therefore, the expression "a device comprising means A and B" should not be limited to a device consisting of components A and B only.

[0128] The "one embodiment" or "embodiment" mentioned in this specification means that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment of the present application. Therefore, the terms "in one embodiment" or "in an embodiment" appearing in various places in this specification do not necessarily refer to the same embodiment, but may refer to the same embodiment. In addition, in the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.

[0129] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present application is described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may also include more other equivalent embodiments without departing from the concept of the present invention, all of which belong to the protection scope of the present invention.

Claims

1. A method for managing edge server data, characterized in that: Executed by an edge server, the method includes: Initialize corresponding channel information according to the data to be acquired, where the channel information includes a physical channel, a logical channel, and a data type; Acquire the data of the terminal device through the physical channel and store it in the cache; Classifying the data in the cache according to the data type and storing them in corresponding logical channels respectively; Data support is provided to the cloud according to the communication protocol configured in the edge server and the data policy associated with the communication protocol, so that the cloud forwards the data in the logical channel.

2. The method according to claim 1, characterized in that: The channel information also includes acquisition frequency, channel association information and channel association algorithm. After acquiring the data of the terminal device through the physical channel and storing it in the cache, it also includes: classifying the data in the cache into high-frequency data and low-frequency data according to the acquisition frequency; storing the high-frequency data in the cache to a local file according to the channel association information and the channel association algorithm; The low-frequency data in the cache is stored in a local file and a real-time database according to the channel association information and the channel association algorithm.

3. The method according to claim 1, characterized in that The configured communication protocols include at least one of the following: MQTT protocol, configuration information includes Broker server address and port number, MQTT communication protocol version, authentication method, user name and password; HTTP protocol, configuration information includes communication port number, communication protocol version, authentication method and user name; OPCUA protocol, configuration information includes communication port number, communication protocol version, authentication method and user name; COAP protocol, configuration information includes communication port number, communication protocol version, authentication method and user name.

4. The method according to claim 1 or 3, characterized in that: Each communication protocol is associated with only one data policy, which includes a real-time policy or a continuity policy.

5. The method according to claim 3, characterized in that: The cloud forwarding the data in the logical channel includes: The cloud acts as a gateway and forwards the data in the logical channel to the user end in an active push or response manner.

6. The method according to claim 5, characterized in that The forwarding of the data in the logical channel to the user end in an active push or response manner includes: According to the configured MQTT protocol or OPC UA protocol, forward the data in the logical channel to the user end in an active push manner; and / or, According to the configured HTTP protocol or COAP protocol, the data in the logical channel is forwarded to the user end in a response manner.

7. The method according to claim 5 or 6, characterized in that: Also includes: The user end configures the communication protocol and data policy through a Web program, so that the cloud performs forwarding of the data according to the configured communication protocol and data policy.

8. An edge server data management device, characterized in that: include: An initialization module, used to initialize corresponding channel information according to the data to be acquired, the channel information including physical channel, logical channel, and data type; An acquisition module, used for acquiring data of a terminal device through the physical channel and storing the data in a cache; A processing module, used for classifying the data in the cache according to the data type, and storing them in corresponding logical channels respectively; The sending module is used to provide data support to the cloud according to the communication protocol configured in the edge server and the data policy associated with the communication protocol, so that the cloud can forward the data in the logical channel.

9. A computing device, characterized in that include: processor; A memory for storing one or more programs; When the one or more programs are executed by the processor, the processor implements an edge server data management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, an edge server data management method as described in any one of claims 1 to 7 is implemented.

Images