Multi-source heterogeneous data access method and system based on device description file, device and medium

Abstract

The invention discloses a multi-source heterogeneous data access method and system based on a device description file, a device and a medium, the device description file adopts a YAML format and is composed of device basic information, device resource information, device command information and core command information, a device service template is designed based on the device description file, and the core command information is designed based on the device service template. The template extracts common links related to equipment access, provides a null interface for processing logic related to the equipment, and fills a null function according to a specific communication protocol when the access equipment is different, so that the rapid access of the specific equipment is completed. The multi-source heterogeneous data access method based on the device description file is formed, the problems of repeated development, long construction period and the like caused by diverse types of underlying devices and data isomerism in existing same-type system applications are solved, the development difficulty of the system is reduced, and the construction speed and robustness of the system are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of edge computing Internet of Things edge device access, and relates to a multi-source heterogeneous data access method, system, device and medium based on device description files. Background Art

[0002] With the rapid development of information technology, especially the booming of cloud computing, big data, artificial intelligence and other technologies, edge computing technology, as a bridge connecting the physical world and the digital world, has become increasingly important and has a greater application value. Edge computing effectively reduces data transmission latency, improves data processing efficiency, and enhances data security and privacy protection by pushing computing, storage, and application services to the edge of the network, that is, near the device or data source. The maturity and widespread application of this technology are profoundly changing all walks of life. From smart manufacturing, smart cities, smart transportation to telemedicine, agricultural monitoring and many other fields, we have witnessed the changes brought about by edge computing.

[0003] However, with the explosive growth in the number of edge computing IoT devices, there are many types of edge devices, including sensors, cameras, smart meters, mobile terminals, etc. Each device has its own unique communication protocol, data format and interface standard, which requires a lot of customized development work when the device is connected to the system, increasing the complexity and cost of access. Different application scenarios have different requirements for device access. For example, in the field of intelligent manufacturing, device access needs to meet the requirements of high real-time and high reliability; while in the field of smart cities, more attention is paid to large-scale connection of devices and efficient transmission of data. This scenario difference puts higher requirements on the flexibility and scalability of device access.

[0004] Therefore, how to quickly and efficiently connect a large number of edge computing IoT devices in applications in different fields and scenarios to the system has become a key issue that needs to be solved urgently. Summary of the invention

[0005] In response to the problems existing in the prior art, the present invention provides a multi-source heterogeneous data access method based on device description files, which can realize the rapid access function of different types of terminal devices in the edge field, and can be used for the construction of cloud-edge systems in smart cities, smart factories, etc., ultimately reducing construction costs.

[0006] The present invention is achieved through the following technical solutions: A multi-source heterogeneous data access method based on device description files, comprising: Based on the access and interaction methods of IoT devices, summarize the commonalities of multi-source heterogeneous data access processing, design device abstract models, and define device description files; Extract common information based on device description files and establish device service templates; Based on the device service template, the common links involved in device access are extracted. When the access devices are different, empty functions with different functions are filled to complete the rapid access of specific devices, thereby realizing the access of multi-source heterogeneous data.

[0007] Preferably, the device description file adopts YAML format.

[0008] Preferably, the device description file includes basic device information, device resource information, device command information and core command information.

[0009] Preferably, the design process of the device abstract model is: The physical devices of the Internet of Things are abstracted into device abstract models that include objects, resources, and commands. Objects are represented as the basic description of the device, including the operating status and parameters of the device. Resources are defined as the information that the device can provide to the outside and the process of exchanging information with the outside. Commands are defined as commands that the device can respond to.

[0010] Preferably, the access mode and interaction mode of the Internet of Things device include UART, MODBUS, BLE, SPI, CAN and MQTT.

[0011] Preferably, the specific process of establishing the device service template is: Extract common information based on device description files, including service registration, data registration, acquisition, and application configuration function information. By reading device description file information, convert the collected device data into a new format and send it to the system's data processing center, thereby establishing a device service template. Preferably, the specific process of completing the quick access of a specific device is: For different types of underlying devices, the device service template extracts the same functional codes related to device access to form a fixed template program, and the remaining different functions provide empty functions. When the access devices are different, the above empty functions are filled in according to specific communication protocols and device drivers to complete the rapid access of specific devices.

[0012] A multi-source heterogeneous data access system based on device description files, comprising: The device abstract model design module is used to summarize the common features of multi-source heterogeneous data access processing based on the access and interaction methods of IoT devices, design the device abstract model, and thus define the device description file; A device service establishment module is used to extract common information based on the device description file and establish a device service template; The device data processing module is used to extract the common links involved in device access based on the device service template. When the access devices are different, empty functions with different functions are filled to complete the rapid access of specific devices, thereby realizing the access of multi-source heterogeneous data.

[0013] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the multi-source heterogeneous data access method based on a device description file are implemented.

[0014] A computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the multi-source heterogeneous data access method based on a device description file.

[0015] Compared with the prior art, the present invention has the following beneficial technical effects: The present invention provides a multi-source heterogeneous data access method based on a device description file. Through a device abstract model and a device description file, the common features of various types of Internet of Things devices are deeply analyzed. The model can cover the access requirements of most devices, realize the standardization and automation of device access, and greatly reduce repeated development work. Based on the device description file, the common links in the device access process are extracted, and a general device service template is designed for these common links. Based on the device service template, the common links involved in device access are extracted. When the access devices are different, empty functions of different functions are filled to complete the rapid access of specific devices, thereby realizing the access of multi-source heterogeneous data and forming a multi-source heterogeneous data access method based on device description files. When a new device needs to be accessed, the method of the present invention only needs to fill in the empty functions or interfaces in the service template according to the specific information of the device. In this way, specific devices can be quickly accessed without writing code from scratch. The standardized access method reduces the system's failure points caused by device differences and improves the system's stability and reliability. It effectively solves the problems of repeated development and long construction cycles caused by the diverse types of underlying devices and heterogeneous data in existing similar system applications, reduces the difficulty of system development, and improves the system construction speed and robustness. It can achieve fast access to different types of end devices in the edge field, which can be used for the construction of cloud-edge-end systems in smart cities, smart factories, etc., and ultimately reduce construction costs. It can not only promote the rapid construction and efficient operation of the Internet of Things system, but also promote the innovation of Internet of Things technology and the expansion of application scenarios, laying a solid foundation for building a more intelligent, convenient and efficient Internet of Things world.

[0016] Furthermore, the use of YAML format for device description files not only improves the readability and maintainability of configuration files, but also greatly promotes the standardization and automation of the device access process.

[0017] Furthermore, the unified access template framework and standardized management processes improve the stability and reliability of the system and facilitate subsequent maintenance and expansion.

[0018] Furthermore, the standardization of device description files promotes interoperability between devices from different manufacturers and models, laying a solid foundation for building large-scale and diversified Internet of Things systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a flow chart of the multi-source heterogeneous data access method of the present invention; Figure 2 It is a schematic diagram of an abstract model of a device of the present invention; Figure 3 It is a flow chart of device access of the present invention; DETAILED DESCRIPTION The present invention is further described in detail below in conjunction with specific embodiments, which are intended to explain the present invention rather than to limit it.

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

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which the present invention belongs. The terms used herein in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The term "and / or" used herein includes any and all combinations of one or more of the related listed items.

[0022] A multi-source heterogeneous data access method based on device description files, such as Figure 1As shown, the device description file adopts the YAML format, which consists of basic device information, device resource information, device command information, and core command information. The device service template is designed based on the device description file. The template extracts the common links involved in device access and provides an empty interface for the device-related processing logic. When the access device is different, the empty function is filled according to the specific communication protocol to complete the rapid access of the specific device. A multi-source heterogeneous data access method based on the device description file is formed.

[0023] 1. Device Description File Analyze the access and interaction methods of typical IoT devices, such as UART, MODBUS, BLE, SPI, CAN, MQTT, etc., summarize the common features required for multi-source heterogeneous data access, design device abstract models, and define device description files.

[0024] The device abstract model is as follows Figure 2 As shown in the figure, a typical IoT physical device is abstracted into a device model that includes objects, resources, and commands, where "objects" are the basic description of the device, including the device's operating status (readable / writable), parameters (type, such as uint, float64, bool, string, binary...; default value; unit; valid range; maximum value; minimum value), and other information (encoding type, etc.); "resources" define the information that the device can provide to the outside world and how to exchange information with the outside world; "commands" define the commands that the device can respond to.

[0025] The device description file is defined according to the device abstract model. The device description file adopts the YAML format, and the content is shown in Table 1. The file consists of basic device information, device resource information, device command information, and core command information.

[0026] The basic device information describes the basic information of the device, such as the name, manufacturer, model name, etc., and determines the unique name of this type of device in the system. The device resource information describes the sensor data or configurable information provided by this type of device, and marks its type, read and write characteristics, and how to obtain resources. The device command information describes the available commands of the device, which can be accessed through the API to obtain or set the device. The core command information is used for the initialization, status query, and configuration update functions of the device to ensure that the device responds to basic management instructions as expected; Table 1 Device description file format

[0027] 2. Equipment Service Template In order to enable different types of devices to quickly access the edge computing system, it is necessary to implement device microservices corresponding to the device type. The microservice is written and generated according to the device service template. The device service template is the basic framework of the device microservice. It extracts common information based on the device description file and has functions such as service registration, data registration, acquisition, and application configuration. By reading the device description file information, the collected device data is formatted and sent to the system data processing center to establish the device service template. The relationship between physical devices, device description files, device service templates, and device microservices is as follows: Figure 3 As shown in the figure. Based on the above device description file, a set of device service templates is designed. This template abstracts the common steps in the device access process, such as device discovery, authentication, data parsing, command issuance and execution feedback, etc., forming a set of standardized access processes. At the same time, a series of empty interfaces or hook functions are reserved in the template for inserting processing logic closely related to specific device types.

[0028] The device service template has the following features: 1. Register the device microservice to the system; 2. Configure devices, i.e. load and manage physical devices; 3. Update and notify the system of the current operating status of the device (whether it is online, whether it can communicate, etc.); 4. Regularly check if the device configuration has changed and apply the new configuration when appropriate; 5. Get device data and pass it to the system; 6. Receive and respond to device commands.

[0029] For different types of underlying devices, the device service template extracts the same functional codes related to device access to form a fixed template program, and provides empty functions for the remaining different functions. When the access devices are different, the above empty functions are filled in according to specific communication protocols, device drivers, etc., so as to complete the rapid access of specific devices. When a new device needs to be connected, first write or modify the corresponding YAML description file according to the characteristics of the device to clarify all its necessary configuration information and operation interfaces. Then, according to the description file, fill in the communication protocol, data parsing rules and command processing logic specific to the device by implementing the empty interface in the template.

[0030] The multi-source heterogeneous data access method based on device description files of the present invention reduces the need to repeatedly write code for different devices through template and modular design, and significantly reduces the development workload. Device access becomes fast and simple, and only a small amount of adaptation code needs to be written, which greatly shortens the time from project planning to deployment. The unified access template framework and standardized management process improve the stability and reliability of the system and facilitate subsequent maintenance and expansion. The standardization of device description files promotes interoperability between devices of different manufacturers and models, and lays a solid foundation for building large-scale and diversified Internet of Things systems.

[0031] A multi-source heterogeneous data access system based on device description files, comprising: The device abstract model design module is used to summarize the common features of multi-source heterogeneous data access processing based on the access and interaction methods of IoT devices, design the device abstract model, and thus define the device description file; A device service establishment module is used to extract common information based on the device description file and establish a device service template; The device data processing module is used to extract the common links involved in device access based on the device service template. When the access devices are different, empty functions with different functions are filled to complete the rapid access of specific devices, thereby realizing the access of multi-source heterogeneous data.

[0032] An embodiment of the present invention provides a terminal device, which includes: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps in the above-mentioned dynamic scene image deblurring method are implemented; or when the processor executes the computer program, the functions of each module in the above-mentioned dynamic scene image deblurring system are implemented.

[0033] The computer program may be divided into one or more modules / units, and the one or more modules / units are stored in the memory and executed by the processor to accomplish the present invention.

[0034] The terminal device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The terminal device may include, but is not limited to, a processor and a memory.

[0035] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0036] The memory may be used to store the computer programs and / or modules, and the processor implements various functions of the terminal device by running or executing the computer programs and / or modules stored in the memory and calling the data stored in the memory.

[0037] If the module / unit integrated in the terminal device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.

[0038] Based on such understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing related hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned dynamic scene image deblurring method can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc.

[0039] The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals. In another embodiment of the present invention, the present invention further provides a storage medium, specifically a computer-readable storage medium (Memory), which is a memory device in a computer device for storing programs and data. It can be understood that the computer-readable storage medium here can include both built-in storage media in the computer device and, of course, extended storage media supported by the computer device. The computer-readable storage medium provides a storage space, which stores the operating system of the terminal. In addition, one or more instructions suitable for being loaded and executed by the processor are also stored in the storage space, and these instructions can be one or more computer programs (including program codes). It should be noted that the computer-readable storage medium here can be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk memory. One or more instructions stored in the computer-readable storage medium can be loaded and executed by the processor; Example 2: MODBUS type temperature sensor device access; Assume that the temperature sensor manufacturer is "XXX", the measurement range is -55°C to 125°C, supports Modbus TCP communication, and has high or low temperature alarms. The registers are shown in Table 2: Table 2 Temperature sensor registers

[0040] According to the actual situation of the device, write the device description file. The main contents are shown in Table 3.

[0041] Table 3 Device description file format

[0042] The reading and setting of the upper and lower alarm limits and alarm mode of the device depend on the specific register definition. Therefore, the underlying logic of this function belongs to the special logic related to the device. The setting and reading functions of specific registers should be implemented in the empty function. Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0043] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0044] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0045] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0046] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

[0047] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any ordinary technician in the industry can smoothly implement the present invention as shown in the drawings and described above. However, any equivalent changes, modifications and evolutions made by technicians familiar with the profession without departing from the scope of the technical solution of the present invention using the technical content disclosed above are all equivalent embodiments of the present invention. At the same time, any equivalent changes, modifications and evolutions made to the above embodiments based on the essential technology of the present invention are still within the protection scope of the technical solution of the present invention.

Claims

1. A multi-source heterogeneous data access method based on device description files, characterized in that: include, Based on the access and interaction methods of IoT devices, summarize the commonalities of multi-source heterogeneous data access processing, design device abstract models, and define device description files; Extract common information based on device description files and establish device service templates; Based on the device service template, the common links involved in device access are extracted. When the access devices are different, empty functions with different functions are filled to complete the rapid access of specific devices, thereby realizing the access of multi-source heterogeneous data.

2. The multi-source heterogeneous data access method based on device description files according to claim 1, characterized in that: The device description file adopts the YAML format.

3. The multi-source heterogeneous data access method based on device description files according to claim 1, characterized in that: The device description file includes basic device information, device resource information, device command information and core command information.

4. The multi-source heterogeneous data access method based on device description files according to claim 1, characterized in that: The design process of the device abstract model is: The physical devices of the Internet of Things are abstracted into device abstract models that include objects, resources, and commands. Objects are represented as the basic description of the device, including the operating status and parameters of the device. Resources are defined as the information that the device can provide to the outside and the process of exchanging information with the outside. Commands are defined as commands that the device can respond to.

5. The multi-source heterogeneous data access method based on device description files according to claim 1, characterized in that: The access and interaction methods of IoT devices include UART, MODBUS, BLE, SPI, CAN and MQTT.

6. The multi-source heterogeneous data access method based on device description files according to claim 1, characterized in that: The specific process of establishing a device service template is as follows: Common information is extracted based on the device description file, including service registration, data registration, acquisition and application configuration functional information. By reading the device description file information, the collected device data is converted into a format and sent to the system's data processing center, thereby establishing a device service template.

7. The multi-source heterogeneous data access method based on device description files according to claim 1, characterized in that: The specific process of completing the quick access of a specific device is as follows: For different types of underlying devices, the device service template extracts the same functional codes related to device access to form a fixed template program, and the remaining different functions provide empty functions. When the access devices are different, the above empty functions are filled in according to specific communication protocols and device drivers to complete the rapid access of specific devices.

8. A multi-source heterogeneous data access system based on device description files, based on the multi-source heterogeneous data access method based on device description files according to any one of claims 1 to 7, characterized in that: include, The device abstract model design module is used to summarize the common features of multi-source heterogeneous data access processing based on the access and interaction methods of IoT devices, design the device abstract model, and thus define the device description file; A device service establishment module is used to extract common information based on the device description file and establish a device service template; The device data processing module is used to extract the common links involved in device access based on the device service template. When the access devices are different, empty functions with different functions are filled to complete the rapid access of specific devices, thereby realizing the access of multi-source heterogeneous data.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the multi-source heterogeneous data access method based on the device description file as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the multi-source heterogeneous data access method based on a device description file as described in any one of claims 1 to 7 are implemented.

Images