CN114265823A - A visualization integration system and method for IoT devices based on mapping files - Google Patents

Abstract

The invention relates to a mapping file-based visual integration system and method for Internet of things equipment, belongs to the technical field of intelligent Internet of things construction, and solves the problems that the existing Internet of things equipment integration mode is poor in flexibility and expandability and users cannot view results. The visualization integration system includes: the cloud file system is used for storing the mapping file of the Internet of things equipment; the mapping file includes: the required option, equipment access interface information; optional items: the equipment accesses a webpage link of the operation interface; the mapping file analysis system executes: analyzing the content of the mapping file; analyzing equipment target data; the form system is used for obtaining a form template matched with the equipment access interface information and storing equipment target data into the form template to form data; the form data is also fed back to a mapping file analysis system; and the visual display interface is used for visually displaying the form data and the equipment access operation interface linked to the webpage link.

Description

A visualization integration system and method for IoT devices based on mapping files

technical field

The invention relates to the technical field of intelligent IoT construction, in particular to a visualization integration system and method for IoT devices based on a mapping file.

Background technique

In the field of smart IoT construction, there are many types of hardware devices with networking capabilities. The huge equipment groups come from different hardware manufacturers, each with its own unique software environment and data backend. But on the whole, the methods for general users to access IoT devices are similar, and the basic system model for accessing IoT devices is shown in Figure 1. In this system model, three components are mentioned:

1. [Internet of Things device] located in a specific device installation environment

2. Internet-based [device access data platform], generally provided by device manufacturers

3. [Device Access Operation Interface] provided to end users

[Internet of Things devices] produced by device manufacturers are immutable objects with fixed functions that are provided to users as final stable products. Although most of the equipment is put into use after purchase, there may be a process of equipment installation and maintenance in a specific environment, but these contents are relatively clear because of their simplicity, users can handle them by themselves, or they belong to the responsibility of equipment manufacturers. The shaped entity elements.

In the process of accessing the [Internet of Things device], the end user actually directly faces the [device access operation interface]; before accessing the interface, an Internet-based [device access data platform] is generally needed to achieve the goal of Device basic function management. The biggest difference between these two elements and the device is that the device is a physical entity, and the two are essentially software services.

It is true that equipment manufacturers will both [device access data platform] and [device access operation interface] as the supporting functions of [Internet of Things device] products, or provide them directly or indirectly to users to achieve a closed loop of the "Internet of Things" system; However, in this link, the [device access operation interface] that the end user comes into contact with is not only provided by the manufacturer. In the prior art, a closed loop of the "Internet of Things" system can be formed in various ways, and the main implementation is shown in FIG. 2 .

In the actual application process, a user may need to purchase a variety of physical devices, which is inevitable; but as a software service, it is not as simple as "the more the better". The situation of this problem is: in a single IoT device environment, the device manufacturer can directly provide a device access operation interface to the end user, which is generally satisfied for users who use a single device; even if the user uses multiple, A variety of equipment, but the equipment is provided by the same manufacturer, so the equipment access operation interface provided by the equipment manufacturer can also include these equipment together. The coexistence of multiple types of IoT devices from different manufacturers will make the end user face the situation that multiple devices access the operation interface, as shown in Figure 3. If the IoT device environment where the user is located is no longer a single device, not just using devices from one manufacturer, but multiple types of devices from different device manufacturers, in order to access multiple devices running in the same device installation environment For networked devices, users may need to access and use multiple sets of different [device access operation interfaces] at the same time, which undoubtedly brings great inconvenience to users' daily use. In this case, the need for a "unified" [device access interface] has become the most anticipated goal of such users.

Provide a unified device access interface for end users to manage multi-manufacturer and various types of IoT devices, which can be started in the following ways:

1. Based on the SDK provided by the manufacturer, the user develops an interface that meets their own needs, (raising the user's application technology threshold)

2. Seek an integrator focusing on the integration business to provide customized services to assist in the solution (users need to pay extra high funds)

3. Seek an existing, flexible and extensible integration platform for relatively simple custom integration to achieve the goal (the user needs to pay less additional funds to achieve the goal)

The common point of the above three methods is "do not use the equipment originally provided by the manufacturer to access the operation interface", and instead customize it through different channels. Only in this way can the problem of how to "unify" the access operations of devices from different manufacturers can be solved. User self-research and integrators are essentially the same - someone needs to integrate equipment from different manufacturers, or they can do it themselves, or pay someone to do it. As a result, the end user has to pay more costs. And an existing "integration platform" unifies the technology and improves the reusability of development investment, and the end user only needs to spend a very small fee - compared with self-research and all entrusted integration consultation Customized - This is undoubtedly the most end-user friendly solution. However, how to obtain a flexible and scalable IoT device integration method is an urgent problem to be solved. In addition, a large amount of data will be generated after the integration of IoT devices. How to facilitate users to view the integration data of IoT devices is also a problem that needs to be considered.

SUMMARY OF THE INVENTION

In view of the above analysis, the embodiments of the present invention aim to provide a visualization integration system and method for IoT devices based on a mapping file, so as to solve the problems of poor flexibility and poor scalability of the existing IoT device integration methods and to facilitate users to view question.

In one aspect, the present invention provides a visualization integration system for IoT devices based on a mapping file, including:

The cloud file system is used to store the mapping file of the Internet of Things device; wherein, a mapping file indicates a single Internet of Things device, including: required item, device access interface information; optional item: a web page link for the device to access the operation interface;

To map the file parsing system, execute:

Mapping file content parsing, used to parse out the contents of the mapping file;

The device target data analysis associated with the mapping file based on the device access interface information is used to obtain device target data;

a form system for obtaining a form template matching the device access interface information, storing the device target data in the form template to form form data; and feeding back the form data to the mapping file parsing system;

The visual display interface is used to visually display the form data, and the device access operation interface to which the webpage link is linked.

On the basis of the above scheme, the present invention has also made the following improvements:

Further, in the visual display interface, layout one or more file display windows;

Each file display window is bound to a mapping file, and the file display window is used to display the form data and device access operation interface obtained by parsing the bound mapping file.

Further, the device access interface information includes an access interface address, security verification information, device identification information, and a data format of the access interface; the device identification information includes a device type unique identifier and a device unique identifier.

Further, the web page link is linked to the corresponding device access operation interface based on the security verification information and the device unique identifier.

Further, based on the device target data parsing associated with the mapping file implemented by the device access interface information, execute:

sending the parsed data format to the form system, so that the form system obtains a form template matching the data format based on the data format;

Obtain the device target data of the IoT device according to the parsed access interface address, security verification information and device identification information, and send the device target data to the form system.

Further, the data format of the access interface includes:

A data structure, used to describe the key fields involved in the device target data of the IoT device;

The unique identifier of the data structure is used to uniquely identify the data structure based on the unique identifier of the device type.

Further, the form system obtains a form template matching the device access interface information, including:

According to the unique identifier of the data structure, the form system queries whether a form template with the unique identifier of the same data structure is stored in the form system,

If stored, record the form template as a form template matching the data format;

If not stored, create a new form template according to the unique identifier of the data structure, set the key fields in the new form template according to the data structure, and record the form template with the key fields set as matching the The device accesses the form template of the data format in the interface information.

Further, the device access interface information also includes data state alarm information; the data state alarm information includes an alarm field and an alarm condition of each alarm field; wherein,

Setting one or more key fields in the data structure as the alarm field;

Corresponding alarm conditions are respectively set for each alarm field; if the device target data stored in the form template meets the alarm conditions, the form system also generates corresponding alarm information;

In the visual display interface, the alarm information is visually displayed in the form of special marks.

Further, get device target data by doing the following:

Read the access interface address, and link to the device access interface platform;

generating a device interface request using the security verification information and the device unique identifier; the device interface request is used to query device data of the current Internet of Things device;

If the device interface request is successful, the mapping file parsing system obtains the device data from the device access interface platform, and extracts the device target data from the device data;

If the device interface request is wrong, and the prompt device does not exist or the permission is invalid, the current IoT device is marked as invalid, and the parsing of the device target data is interrupted;

Otherwise, the current Internet of Things device is marked as offline, and the acquired latest device data in the offline state of the current Internet of Things device is used as the device target data.

On the other hand, a visualization integration method for IoT devices based on a mapping file is provided, including:

Store the mapping file in the cloud file system; a mapping file indicates a single IoT device, including: required item, device access interface information; optional item: web page link for the device to access the operation interface;

When the mapping file parsing system detects a new mapping file in the cloud file system, execute:

Content analysis of the mapping file to parse out the contents of the mapping file;

The device target data parsing associated with the mapping file implemented based on the device access interface information to obtain device target data;

The form system obtains a form template matching the data format based on the device access interface information, stores the device target data in the form template, and forms form data; and feeds back the form data to the mapping file for parsing system;

The visual display interface visually displays the form data; if the mapping file includes a web page link of the device access operation interface, the device access operation interface linked to the web page link is also visually displayed.

Compared with the prior art, the present invention can achieve at least one of the following beneficial effects:

The visualization integration system and method for IoT devices based on a mapping file provided by the embodiments of the present invention have the following beneficial effects:

1. Strong flexibility and scalability; by designing a mapping file for indicating the device access interface information of a single IoT device, and using the mapping file parsing system, the device target data of the IoT device can be obtained, and the device target data of the IoT device can be obtained. The acquired device target data is stored in the form system. Therefore, the visualization integration system in this embodiment has strong flexibility and scalability.

2. By visually displaying the form, it is convenient for the user to know the form data in time. At the same time, if the mapping file includes the webpage link of the device access operation interface, the device access operation interface linked to the webpage link can also be displayed visually, which is convenient for the user to access the operation interface from the device. The device accesses the operation interface to obtain more real-time and more comprehensive device data;

3. It is convenient to manage mapping files; on the one hand, a unified mapping file organization format is set, so that different equipment manufacturers can generate mapping files of IoT devices according to the agreed format; on the other hand, IoT devices can be managed in the form of files, specifically , uploading and storing a mapping file, that is, establishing a connection with the IoT device indicated by the mapping file; deleting a mapping file, that is, disconnecting the connection with the IoT device indicated by the mapping file;

4. By enriching the content of the mapping file, and making full use of the mapping file in the process of obtaining and storing the target data of the device in cooperation with the mapping file parsing system and the form system, it can realize the confirmation of the valid/invalid status of the device and the offline/online status of the device The confirmation of the equipment target data and whether the early warning is required, thus enriching the functions of the IoT device visualization integration system. It should be noted that, after obtaining the device target data, based on the device target data, the follow-up work such as device target data analysis and processing and visual display can also be performed, thereby effectively expanding the functions and usage scenarios of the IoT device visualization integration system;

5. The implementation process is simple and efficient, which can minimize the access cost of IoT devices; in addition, the visualized integration system is highly customizable and can achieve the best integration effect at a lower cost.

In the present invention, the above technical solutions can also be combined with each other to achieve more preferred combination solutions. Additional features and advantages of the invention will be set forth in the description which follows, and some of the advantages may become apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by means of particularly pointed out in the description and drawings.

Description of drawings

The drawings are for the purpose of illustrating specific embodiments only and are not to be considered limiting of the invention, and like reference numerals refer to like parts throughout the drawings.

Figure 1 shows the basic system model for accessing IoT devices;

Figure 2 shows the main implementation methods for forming a closed loop of the "Internet of Things" system;

Figure 3 is a schematic diagram of a situation in which multiple types of IoT devices from different manufacturers coexist, so that the end user is faced with multiple devices accessing the operation interface;

4 is a schematic structural diagram of an integrated system for visualization of IoT devices based on a mapping file provided in Embodiment 1 of the present invention;

Fig. 5 is the work flow chart that the mapping file parsing system and the form system cooperate to realize the acquisition and storage of device target data;

Fig. 6 is a display method of the visual display interface;

FIG. 7 is a flowchart of a method for visualizing and integrating IoT devices based on a mapping file according to Embodiment 1 of the present invention.

Detailed ways

The preferred embodiments of the present invention are specifically described below with reference to the accompanying drawings, wherein the accompanying drawings constitute a part of the present application, and together with the embodiments of the present invention, are used to explain the principles of the present invention, but are not used to limit the scope of the present invention.

Example 1

A specific embodiment of the present invention discloses a visualization integration system for IoT devices based on a mapping file. The schematic diagram of the structure of the visualization integration system is shown in FIG. 4 , and the visualization integration system includes:

The cloud file system is used to store a mapping file of the Internet of Things device; wherein, a mapping file indicates a single Internet of Things device, including: a required item, device access interface information; an optional item: a web page link for the device to access the operation interface;

To map the file parsing system, execute:

Mapping file content parsing, used to parse out the contents of the mapping file;

The device target data analysis associated with the mapping file based on the device access interface information is used to obtain device target data;

a form system for obtaining a form template matching the device access interface information, storing the device target data in the form template to form form data; and feeding back the form data to the mapping file parsing system;

The visual display interface is used to visually display the form data, and the device access operation interface to which the webpage link is linked.

Compared with the prior art, the visualized integration system for IoT devices based on a mapping file provided in this embodiment, on the one hand, uses a mapping file designed to indicate device access interface information of a single IoT device, and uses the mapping file to parse the system. system, so that the device target data of the IoT device can be obtained, and the obtained device target data can be stored in the form system. Therefore, the visual integration system in this embodiment has strong flexibility and scalability; and the implementation process is simple and efficient, so the access cost of IoT devices can be reduced to the greatest extent; in addition, the visual integration system can be The high degree of customization can achieve the best integration effect at a lower cost; on the other hand, through the visual display of the form, it is convenient for users to know the form data in time. The webpage link can also visually display the device access operation interface to which the webpage link is linked, so that the user can obtain more real-time and more comprehensive device data from the device access operation interface.

The mapping file is the core of implementing the solution in this embodiment. Therefore, the mapping file is first described as follows:

When manufacturers of IoT devices want to access IoT devices through the "device access data platform", they need to record the device access interface information: manufacturers must follow a given network data interface (which may also contain corresponding network protocol information). ), in conjunction with the parameters connected to the IoT device, can connect to the corresponding IoT device. In the mapping file, the manufacturer needs to record the device access interface information. In order to enable different IoT devices produced by different manufacturers to record the device access interface information in a relatively simple and unified way, the device access interface information in the mapping file must also be provided in a uniform and agreed format (for example, provided as JSON text) and contains the following:

1. Device access interface information (required), including:

(1) Access interface configuration information, including: mandatory items: access interface address and security verification information; optional items: specified device data parameters; among them,

The access interface address must be unified with a more general and security-capable network protocol (eg httpspost); through the access interface address, the device access interface platform of the IoT device can be linked.

The security verification information is used to access the device access interface platform. Exemplarily, the security verification information can be a user access key, or an access token is generated based on the security verification information and the device unique identifier, so as to improve the access efficiency of the device access interface platform;

Specify the device data parameters to indicate the parameter requirements of the device target data to be extracted, such as collecting data within a certain period of time, collecting data exceeding a certain threshold, etc.

(2) Equipment identification information, including equipment type unique identification and equipment unique identification; wherein,

Device type unique identifier, used to uniquely identify the device type of the current IoT device;

The device unique identifier is used to uniquely identify the identification information of the device itself of the IoT device under the current device type;

The device type unique identifier and the device unique identifier are both uniquely set by the manufacturer. Through the device type unique identifier and the device unique identifier, an IoT device can be distinguished from other IoT devices.

(3) The data format of the access interface, including:

A data structure, used to describe the key fields involved in the device target data of the IoT device;

The unique identifier of the data structure is used to uniquely identify the data structure based on the unique identifier of the device type.

In addition, to further expand the functions of the visual integration system, the device access interface information can also include the following:

(4) Data state alarm information; the data state alarm information includes an alarm field and an alarm condition of each alarm field; wherein,

Setting one or more key fields in the data structure as the alarm field;

Set corresponding alarm conditions for each alarm field;

(5) access cycle;

The mapping file parsing system periodically parses the mapping file according to the access cycle;

2. The web link of the device to access the operation interface;

In the computer field, through a web browser, a web application program with complex functions can be implemented on a web page. If the hardware manufacturer develops such a web application-based access operation "interface" for the device, then this part of the data is recorded in the mapping file in the form of a web page link. When the cloud file system that stores the mapping file displays the mapping file online , you can directly refer to this operation "interface" through this link to directly provide the user with the management access function of the device. The web page link of the "interface" must also be matched with the marking parameters of the device and other data including but not limited to security verification information such as user access keys. Generally, the web page link is linked to the corresponding device access operation interface based on the security verification information and the device unique identifier.

Since not all hardware manufacturers provide an "interface" to the base Web application for their devices, this part of the data is optional in the mapping file. If this information is not recorded in a mapping file, the function of displaying content online is not supported when the mapping file is stored in the cloud file system.

The above-mentioned device access interface information is the information to be provided by the hardware manufacturer to create a corresponding "mapping file" for its device. The contents in the device access interface information will be organized by some relatively simple structures (eg, text files in JSON format), so as to be convenient for hardware manufacturers to fill in. That is, the content in the mapping file is organized according to the agreed format.

Here, the mapping files stored in the cloud file system are also described as follows:

The mapping file of an IoT device, as a computer file, needs a file system to manage it at the file level in the overall system. Since IoT devices must be connected through the Internet to achieve their functions, this file system must also be a cloud file system. In the cloud file system, a device mapping file represents an actual physical hardware device - as long as the end user uploads and stores a valid device mapping file to the cloud disk, he can connect and manage access to the hardware device in the cloud file system ( Unless the device corresponding to the mapping file is offline or the mapping file itself has incorrect data).

As a cloud file system, the system has basic file management functions. At the same time, it also supports the online display function of files: that is, it does not need to be downloaded, and can be opened directly in the cloud file system. In this method, the integrated and docked hardware devices in the management platform are the same as the management of each file in the file system:

Upload and store a mapping file, that is, establish a connection with the IoT device indicated by the mapping file;

Deleting a mapping file means disconnecting the IoT device indicated by the mapping file;

Open a mapping file, open the console of a device and perform real-time control (requires the corresponding interface in the mapping file).

The file online display function can be used to display other files other than the mapping file, but it is not the focus of this method; the focus of this embodiment is that the result of parsing the mapping file can be displayed online, that is, the visual display interface in this embodiment is displayed. Function. If the mapping file also includes web page links, it is also possible to visually display the device access operation interface linked to the web page link—this requires a mapping file mapped to a certain device, recording valid web application links, and It has the identification and safety identification information of the real online running equipment.

In this embodiment, when the mapping file parsing system detects that a new mapping file is added to the cloud file system, the mapping file parsing system starts parsing it; when the mapping file parsing system monitors the mapping file stored in the cloud file system When deleted, the parsing of the deleted mapping file is stopped; specifically, the mapping file parsing system parses the mapping file by performing the following operations:

1. Content analysis of the mapping file, which is used to parse out the contents of the mapping file; specifically,

The mapping file parsing system parses out the contents of the mapping file by performing the following operations:

Perform format verification on the mapping file according to the agreed format;

If the format verification is passed, the contents in the mapping file are parsed;

Otherwise, an error is reported, and the parsing of the mapping file is aborted.

2. The device target data analysis associated with the mapping file implemented based on the device access interface information is used to obtain the device target data; including:

(1) Sending the parsed data format to the form system, so that the form system can obtain a form template matching the data format; this process is relatively simple and will not be described further.

(2) Obtain the device target data of the IoT device according to the parsed access interface configuration information and device identification information, and send the device target data to the form system; specifically,

Get device target data by doing the following:

Read the access interface address, and link to the device access interface platform;

generating a device interface request using the security verification information and the device unique identifier; the device interface request is used to query device data of the current Internet of Things device;

If the device interface request is successful, the mapping file parsing system acquires the device data from the device access interface platform, and extracts the device target data from the device data.

If the device interface request is wrong, and it prompts that the device does not exist or the permission is invalid, the current IoT device will be marked as invalid, and the device target data parsing will be interrupted;

Otherwise, the current Internet of Things device is marked as offline, and the acquired latest device data in the offline state of the current Internet of Things device is used as the device target data.

In addition, if the access interface configuration information does not include the specified device data parameters, directly extract the latest data in the device data as device target data; otherwise, extract the device data that meets the specified device data parameters as the device data Device target data.

In addition, in order to reduce unnecessary program execution, when performing the parsing of the device target data associated with the mapping file, it is possible to first determine whether the IoT device is in a valid state based on the parsed device identification information. The format is sent to the form system; otherwise, parsing of the device target data is interrupted.

In addition, after the form system stores the device target data in the form template, it also feeds back to the mapping file parsing system to complete the storage of the device target data; It is judged whether there is a next access cycle, and if so, when the next access cycle is reached, the device target data analysis associated with the mapping file is performed again; otherwise, the device target data analysis associated with the current mapping file is no longer performed.

Below, the form system in this embodiment is introduced as follows:

A form is a system that can first design a form field template, and then form instance data according to the form template to form a form with an uncertain data format. The form system itself is a relatively common software system, which can well support a variety of data - especially in the process of integrating IoT devices, in the face of various devices, different data needs to be stored Very necessary when structuring device data. Custom forms in the form system need to support common data types of device status information (strings, integers, floating-point numbers, enumeration values, embedded pictures, embedded sound files, etc.), and support format matching to find form templates (for Corresponding to the interface request and storage of different device data), as well as the data addition, deletion and modification of form instance data (tables) under a specific form template, in conjunction with the device access interface parsing function in the mapping file parsing system, to obtain and record the status information of each device in real time .

In this embodiment, the form system mainly performs two operations:

1. After receiving the data format sent by the mapping file parsing system, obtain a form template matching the data format; specifically,

According to the unique identifier of the data structure, the form system queries whether a form template with the unique identifier of the same data structure is stored in the form system,

If stored, the form template is recorded as a form template matching the data format; if not, a new form template is created according to the unique identifier of the data structure, and the new form is set according to the data structure For the key fields in the template, record the form template with the key fields set as the form template matching the data format.

2. After receiving the device target data sent by the mapping file parsing system, store the device target data in the form template;

If the device access interface information further includes data status alarm information, and the device target data stored in the form template meets the alarm condition, the form system also generates corresponding alarm information.

In this embodiment, the working flow chart of the mapping file parsing system and the form system to achieve device target data acquisition and storage is shown in Figure 5. The entire process of target data and storage to the form system. Next, a textual description of the work flow chart in Figure 5:

Step 5-1: Reaching the access cycle entry, the mapping file parsing system determines whether the IoT device is in a valid state, (it should be noted that the default IoT device is in a valid state; but in the parsing of the device target data associated with the mapping file IoT devices may be marked as invalid during the process);

If yes, continue to perform the mapping file parsing; perform step 5-2;

Otherwise, the map file parsing is interrupted.

Step 5-2: The mapping file parsing system sends the parsed data format to the form system;

Step 5-3: the form system is based on obtaining a form template matching the data format; specifically,

According to the unique identifier of the data structure, the form system queries whether the form template with the unique identifier of the same data structure is stored in the form system,

If stored, record the form template as a form template matching the data format;

If not stored, create a new form template according to the unique identifier of the data structure; and set the key fields in the new form template according to the data structure, and record the form template with the key fields set as matching in the form template of the data format;

At the same time, if the device access interface information includes data status alarm information, one or more key fields in the form template are also set as alarm fields according to the data status alarm information;

After obtaining the complete information of the form template, record the form template as the form template corresponding to the IoT device; and report back to the mapping file parsing system to complete the processing of the device data format;

Step 5-4: After the mapping file parsing system receives the feedback and completes the processing of the device data format, it starts to obtain the device target data; specifically,

Read the access interface address, and link to the device access interface platform;

generating a device interface request using the security verification information and the device unique identifier; the device interface request is used to query device data of the current Internet of Things device;

If the device interface request is successful, the mapping file parsing system obtains the device data from the device access interface platform, and extracts the device target data from the device data;

If the device interface request is wrong, and it prompts that the device does not exist or the permission is invalid, the current IoT device will be marked as invalid, and the parsing of the mapping file will be interrupted;

Otherwise, mark the current IoT device as offline, and use the latest device data obtained when the current IoT device is offline as the device target data;

Step 5-5: After completing the acquisition of the device target data, store the device target data in the form template corresponding to the IoT device;

Create a new form instance in the form template, and record the device target data (in some cases, the latest state of the device, that is, "the latest data in the device data") in the created form instance;

If a field of the form is an alarm field, and an alarm occurs in the field data in the form instance, an alarm message will be generated, then the record will be completed, and the corresponding return data will be created;

Otherwise, complete the record directly and create the corresponding return data;

Step 5-6: Feed back the returned data to the mapping file parsing system to complete the closed loop of storing data to the form;

At the same time, or the returned data contains alarm information, the mapping file parsing system can also distribute alarm information through the message system;

Step 5-7: The mapping file parsing system also determines whether there is a next access cycle,

If so, reach the access cycle exit and wait for the arrival of the next access cycle; after the next access cycle arrives, jump to step 5-1;

If not, the access interface data processing is completed.

In addition, it should be noted that after performing steps 5-4, the IoT device may be in an online or offline state when it is valid, and the online or offline state of the device corresponding to the current device target data can also be synchronized to the form template. , so as to get clearer and more complete device data information. Therefore, by making full use of the interaction process between the mapping file parsing system and the form system, a lot of valuable information can be obtained. In addition, after acquiring the device target data, based on the device target data, it can also perform subsequent work such as device target data analysis and processing, visual display, etc., so as to effectively expand the functions and usage scenarios of the IoT device visualization integration system.

In addition, in the visual display interface of this embodiment, one or more file display windows can be laid out; each file display window is bound with a mapping file, and the file display window is used to display the form data obtained by parsing the bound mapping file and device access interface.

The visual display interface can realize the splicing and combination of multiple file display windows, so as to satisfy a certain system interface. The large-screen layout function shown in Figure 6 is a special display method of the visual display interface. In the visual display interface, the alarm information is visually displayed in the form of special marks. Special marks such as differences in color, brightness, font, etc.

Example 2

Embodiment 2 of the present invention also discloses a visualization integration method for IoT devices based on a mapping file. The process is shown in FIG. 7 , including:

Step S1: store the mapping file in the cloud file system; a mapping file indicates a single IoT device, including: a required item, device access interface information; optional item: a web page link for the device to access the operation interface;

Step S2: When the mapping file parsing system detects that a new mapping file is added to the cloud file system, execute:

Content analysis of the mapping file to parse out the contents of the mapping file;

The device target data parsing associated with the mapping file implemented based on the device access interface information to obtain device target data;

Step S3: The form system obtains a form template matching the data format based on the device access interface information, stores the device target data in the form template, and forms form data; and feeds back the form data to the form template. Map file parsing system;

Step S4: the form data is visually displayed on the visual display interface; if the mapping file includes a web page link of the device access operation interface, the device access operation interface linked to the web page link is also visually displayed.

For the specific implementation process of the method embodiment of the present invention, reference may be made to the foregoing system embodiment, and details are not described herein again in this embodiment.

Since the principle of this embodiment is the same as that of the above-mentioned system embodiment, this method also has the corresponding technical effect of the above-mentioned system embodiment.

Those skilled in the art can understand that all or part of the procedures for implementing the solutions in the above embodiments can be completed by instructing relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. Wherein, the computer-readable storage medium is a magnetic disk, an optical disk, a read-only storage memory, or a random-access storage memory, or the like.

The above description is only a preferred embodiment of the present invention, but the protection scope of the present invention is not limited to this. Substitutions should be covered within the protection scope of the present invention.

Claims (10)

1. an integrated system for visualization of Internet of Things equipment based on a mapping file, is characterized in that, comprising: The cloud file system is used to store a mapping file of the Internet of Things device; wherein, a mapping file indicates a single Internet of Things device, including: a required item, device access interface information; an optional item: a web page link for the device to access the operation interface; To map the file parsing system, execute: Mapping file content parsing, used to parse out the contents of the mapping file; The device target data analysis associated with the mapping file based on the device access interface information is used to obtain device target data; a form system for obtaining a form template matching the device access interface information, storing the device target data in the form template to form form data; and feeding back the form data to the mapping file parsing system; The visual display interface is used to visually display the form data, and the device access operation interface to which the webpage link is linked. 2. The visualization integration system for Internet of Things devices based on a mapping file according to claim 1, characterized in that, in the visualization display interface, one or more file display windows are laid out; Each file display window is bound to a mapping file, and the file display window is used to display the form data and device access operation interface obtained by parsing the bound mapping file. 3. The visualized integration system for IoT devices based on a mapping file according to claim 1, wherein the device access interface information comprises an access interface address, security verification information, device identification information and a data format of the access interface; The device identification information includes device type unique identification and device unique identification. 4 . The visualization integration system for IoT devices based on a mapping file according to claim 3 , wherein a web page link is linked to a corresponding device access operation interface based on the security verification information and the device unique identifier. 5 . 5. The visualized integration system for IoT devices based on a mapping file according to any one of claims 1 to 4, wherein the device target data analysis associated with the mapping file implemented based on the device access interface information, executes: sending the parsed data format to the form system, so that the form system obtains a form template matching the data format based on the data format; Obtain the device target data of the IoT device according to the parsed access interface address, security verification information and device identification information, and send the device target data to the form system. 6. The visualization integration system for Internet of Things devices based on a mapping file according to claim 5, wherein the data format of the access interface comprises: A data structure, used to describe the key fields involved in the device target data of the IoT device; The unique identifier of the data structure is used to uniquely identify the data structure based on the unique identifier of the device type. 7. The visualization integration system for IoT devices based on a mapping file according to claim 6, wherein the form system obtains a form template matching the device access interface information, comprising: According to the unique identifier of the data structure, the form system queries whether a form template with the unique identifier of the same data structure is stored in the form system, If stored, record the form template as a form template matching the data format; If not stored, create a new form template according to the unique identifier of the data structure, set the key fields in the new form template according to the data structure, and record the form template with the key fields set as matching the The device accesses the form template of the data format in the interface information. 8. The visualization integration system for Internet of Things devices based on a mapping file according to claim 6, wherein the device access interface information further comprises data state alarm information; the data state alarm information comprises an alarm field and each The alarm condition of the alarm field; where, Setting one or more key fields in the data structure as the alarm field; Corresponding alarm conditions are respectively set for each alarm field; if the device target data stored in the form template meets the alarm conditions, the form system also generates corresponding alarm information; In the visual display interface, the alarm information is visually displayed in the form of special marks. 9. The integrated system for visualization of IoT devices based on a mapping file according to claim 5, wherein the device target data is obtained by performing the following operations: Read the access interface address, and link to the device access interface platform; generating a device interface request using the security verification information and the device unique identifier; the device interface request is used to query device data of the current Internet of Things device; If the device interface request is successful, the mapping file parsing system obtains the device data from the device access interface platform, and extracts the device target data from the device data; If the device interface request is wrong, and the prompt device does not exist or the permission is invalid, the current IoT device is marked as invalid, and the parsing of the device target data is interrupted; Otherwise, the current Internet of Things device is marked as offline, and the acquired latest device data in the offline state of the current Internet of Things device is used as the device target data. 10. A method for visual integration of Internet of Things devices based on a mapping file, comprising: Store the mapping file in the cloud file system; a mapping file indicates a single IoT device, including: required item, device access interface information; optional item: web page link for the device to access the operation interface; When the mapping file parsing system detects a new mapping file in the cloud file system, execute: Content analysis of the mapping file to parse out the contents of the mapping file; The device target data parsing associated with the mapping file implemented based on the device access interface information to obtain device target data; The form system obtains a form template matching the data format based on the device access interface information, stores the device target data in the form template, and forms form data; and feeds back the form data to the mapping file for parsing system; The visual display interface visually displays the form data; if the mapping file includes a web page link of the device access operation interface, the device access operation interface linked to the web page link is also visually displayed.

Images