Internet of Things system based on free configuration of component library

Abstract

The invention discloses an Internet of Things system based on free configuration of a component library. The Internet of Things system comprises a base layer, a component layer and an application system layer, the Internet of Things system is constructed through a visual system designer; the base layer comprises an equipment communication base and an instruction analysis base; the component layer encapsulates all services of the platform into independent component units, and the component units are divided into functional components and data components; an independently running system of the application system layer is formed by configuring various component units; the visual system designer can select or drag the required component units into the page cells in a visual mode, and construction of the Internet of Things system is rapidly completed. The method has the advantages that the Internet of Things system can be quickly created, and different project requirements can be met for customized development.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to an Internet of Things system freely configured based on a component library. Background Art

[0002] In recent years, with the deployment of communication technologies such as 5G, NB-IoT, and LoRa, the connectivity, speed, and coverage of IoT devices have been significantly improved, and the industrial chain has gradually improved and matured; as the center of device management, data integration, and application development, the IoT platform is becoming more mature and feature-rich.

[0003] With the continuous deepening of IoT applications, more intelligent and personalized services will be realized. Technological development is driving innovation and transformation of the entire industry. Customized demands are increasing to meet the needs of specific industries, such as smart parks, smart cultural tourism, smart transportation, etc.

[0004] The traditional customized demand development model requires a lot of manpower and material resources, has low development efficiency, long development cycle, and high complexity and low efficiency in IoT platform deployment, making it impossible to respond quickly to market changes and quickly deliver user needs.

[0005] Although there are some visual process form designs and data screen visual designs, they are all related to the database only and do not involve IoT terminal hardware devices. They have certain limitations and are not suitable for the development demands of the IoT industry.

[0006] The IoT industry needs to integrate different protocols, support the connection of massive devices, collect data from various sensors and devices, and store, analyze and process the data. It needs to handle message transmission and event triggering between devices and platforms to achieve the needs of remote control of devices and linkage control of customized scenarios, and can simplify the deployment complexity of the IoT platform and improve deployment efficiency. Summary of the invention

[0007] The purpose of the present invention is to provide an Internet of Things system that is freely configurable based on a component library. The present invention has the advantages of being able to quickly create an Internet of Things system and meet the customized development requirements of different projects.

[0008] The technical solution of the present invention is as follows: an Internet of Things system freely configured based on a component library, comprising a base layer, a component layer, and an application system layer; the Internet of Things system is constructed by a visual system designer; the base layer comprises a device communication base and an instruction parsing base; the component layer encapsulates all platform services into independent component units, and the component units are divided into functional components and data components; the independently running system of the application system layer is formed by configuring various component units; the visual system designer can select or drag the required component units into the page cells in a visual manner to quickly complete the construction of the Internet of Things system.

[0009] In the aforementioned IoT system based on free configuration of component library, the communication base is responsible for the communication access of the device, the instruction parsing base is responsible for parsing and assembling the uplink and downlink instructions of different IoT devices, and encapsulating the general capability interface of the device according to the device classification for the component layer to call.

[0010] In the aforementioned Internet of Things system based on free configuration of component library, the component layer constructs a platform function component library and a data component library; the component unit includes a front-end interface, back-end services and interfaces; the component units are all built on the base layer, and the base layer supports the basic capabilities of the component units, including capability interfaces including terminal device protocol parsing and device communication, to realize pluggable application of component units on the base layer.

[0011] In the aforementioned Internet of Things system freely configured based on the component library, the visual system designer includes a platform component selection area, a system page content layout area, a system menu configuration area, a system style setting area and a system page thumbnail display area.

[0012] In the aforementioned Internet of Things system based on free configuration of component library, the platform component selection area includes visualization function components and visualization data components, and the visualization function components and visualization data components are derived from encapsulated component units;

[0013] The system menu configuration area can customize the system multi-level menu module, define the function components and data array menu;

[0014] The system page content layout area can provide a page template to present the content of the visual function component and the visual data component dragged to the template cell;

[0015] The system style setting area can set the system page background image mode, including at least GIS map, BIM model and vector map;

[0016] The system page thumbnail display area can display the configured menu pages.

[0017] Compared with the prior art, the present invention has the following beneficial effects:

[0018] The present invention simplifies the traditional complex code development process into a visual, drag-and-drop operation, allowing technicians to quickly create complex IoT application systems and industry platforms;

[0019] The visual system designer packages functional components, data components, predefined style templates, and built-in models into a new development mode, where users can directly drag and drop to build the IoT applications they want;

[0020] The present invention can speed up application development, especially when it is necessary to quickly respond to market changes or business needs. It can realize the "one thousand faces for one thousand people" of projects, customize different styles, functions and data according to different project requirements, so as to adapt to the needs of different industries and application scenarios.

[0021] The componentized development design model of the present invention can lower the technical threshold, improve R&D efficiency, shorten the R&D cycle, and can quickly respond to market changes and business needs, thereby reducing costs and increasing efficiency.

[0022] The present invention packages the IoT service functions into components to form functional components and data components. Each component implements a specific function or a group of functions, and each component is independently developed, upgraded and maintained to improve the maintainability, scalability and flexibility of the system.

[0023] In summary, the present invention has the advantages of being able to quickly create an Internet of Things system and meet the customized development requirements of different projects.

[0024] Instruction Manual

[0025] Figure 1 It is a system architecture diagram of the present invention;

[0026] Figure 2 It is the architecture diagram of the visualization system designer of the present invention;

[0027] Figure 3 It is a schematic diagram of a component unit packaging framework in an embodiment of the present invention;

[0028] Figure 4 It is a relationship diagram between application subsystems and industry platform dashboards and components in an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The present invention is further described below in conjunction with the accompanying drawings and embodiments, but they are not intended to limit the present invention.

[0030] Embodiment. An Internet of Things system based on a freely configurable component library, such as Figure 1As shown, it includes a base layer, a component layer, and an application system layer; the Internet of Things system is constructed through a visual system designer; the base layer includes a device communication base and an instruction parsing base; the component layer encapsulates all platform services into independent component units, and the component units are divided into functional components and data components; the independently running system of the application system layer is formed by configuring various component units; the visual system designer can select or drag the required component units into the page cells in a visual way to quickly complete the construction of the Internet of Things system.

[0031] The communication base is responsible for the communication access of the device, the instruction parsing base is responsible for the parsing and assembly of uplink and downlink instructions of different IoT devices, and encapsulates the general capability interface of the device according to the device classification for the component layer to call.

[0032] The component layer is constructed to form a platform function component library and a data component library; the component unit includes a front-end interface, back-end services and interfaces; the component units are all built on the base layer, and the base layer supports the basic capabilities of the component units, including capability interfaces such as terminal device protocol parsing and device communication, to realize pluggable applications of component units on the base layer.

[0033] like Figure 2 As shown, the visual system designer includes a platform component selection area, a system page content layout area, a system menu configuration area, a system style setting area and a system page thumbnail display area.

[0034] The platform component selection area includes a visualization function component and a visualization data component, and the visualization function component and the visualization data component are derived from a packaged component unit;

[0035] The system menu configuration area can customize the system multi-level menu module, define the function components and data array menu;

[0036] The system page content layout area, when selecting a menu from the system menu configuration area, can customize the style template of the page content area to present the dynamic page template, and define the component target area in this area, and can freely drag the source component of the platform component selection area to the page content layout area to perform component configuration of the system page;

[0037] The system style setting area can set the system page background image mode, including at least GIS map, BIM model and vector map;

[0038] The system page thumbnail display area can display the configured menu pages.

[0039] Development and design method based on componentization

[0040] The platform is designed in a componentized and layered manner, including front-end services, back-end gateway services, middle-layer functional component services and data component services, as well as underlying device command services and device communication services.

[0041] The device instruction service is used for assembling and parsing the uplink and downlink instruction protocols of the device. The design pattern realizes the upward unified device interface exposure and is downward compatible with the access of IoT terminals of different device types and manufacturers.

[0042] The device protocol package service adopts a multi-module design, which is characterized in that one device type is an independent module, and according to the type of terminal device accessed by the platform, the protocol module of the corresponding device is dynamically used.

[0043] The device communication service defines the sending of platform downlink instructions, the receiving and processing of uplink device data, and the management of device connection channels.

[0044] In the device uplink processing, the instance dynamically monitors a specific message queue to perform consumption processing of the uplink data, ensuring that the uplink data of the same device can enter the same queue according to the rules and be consumed by the same instance.

[0045] Platform component development, design and construction: functional component library, data component library

[0046] The functional modules and data modules of each business are encoded and encapsulated into an independent component to achieve high cohesion and low coupling. Components exchange data through interfaces and are given attributes such as names and schematic diagrams. Different industry libraries can be customized according to different industries or departments to facilitate visual display and calling, and realize modular expansion and unified management of component applications. Independent components can simplify the development process, improve development efficiency, simplify the testing process, and improve test coverage. The component unit encapsulation framework structure is as follows: Figure 3 .

[0047] The component design idea is to abstract and encapsulate all the platform's businesses into two categories: functional components and data components:

[0048] The principle of functional component design encapsulation is based on a set that can independently complete a series of related functions. The underlying components are endowed with capabilities by multiple API interfaces, and the functions are presented by the web front-end page unit. Finally, they are provided to users in the form of components for viewing, operation and analysis. Functional components include general basic components and business components, such as device control components, event history components, monitoring components, device management components, policy configuration components, operation and maintenance components, alarm components, visualization scene components, operation history components, etc., to meet users' equipment control and management needs.

[0049] The design and encapsulation principle of data components is based on the ability to independently provide a collection of graphical presentations of data units. Data components collect data collected by various IoT devices connected to the platform and data generated by front-end business operations, aggregate and convert them according to different data types, and present them to users in the form of graphics or tables. First, the data collection layer collects data from IoT devices such as lighting equipment, AI monitoring, environmental collectors, electric meters, LED display screens, digital speakers, and smart manhole covers through encapsulated IoT communication protocols and device acquisition control protocols; then the data aggregation layer cleans, formats, aggregates, and logically converts the collected data according to types such as lighting data, personnel information data, meteorological and environmental data, electricity consumption data, vehicle information data, security monitoring data, and manhole cover pipe network data; finally, the data unit is presented in a visual chart. Each statistical unit is provided to users as a data component for custom configuration to meet user data viewing, statistical analysis, business decision-making, and other needs.

[0050] S1: Web front-end service. The web front-end has a system UI component library. The platform encapsulates the functions shared by multiple components into independent page components for reference by all components in the platform, thereby improving the reusability of components.

[0051] S2: For each functional component / data component unit on the front end, take the [Lighting Equipment Control Component] as an example, create and define component page files, style files, business logic, and data processing files respectively:

[0052] S3: Backend system service, based on the SpringCloud microservice framework, provides interface capabilities in the form of microservices. The https request initiated by the front-end [lighting equipment control component] is authenticated and processed by the gateway service, and then the service request is distributed to the lower-level functional component service.

[0053] S4: The corresponding processing class is matched within the functional component service, and this service performs protocol assembly and downlink operations of the device control instructions.

[0054] S5: The content of the IoT terminal device protocol is defined in the Protocol device protocol service. The device protocol service is designed in a multi-module manner. According to the type of access device, it depends on the Command device instruction service module through the xxx.xml file. The assembly definition of the device protocol is unified in the Protocol. After the encapsulation is completed, the lighting device control command protocol data is sent to the device communication service instance.

[0055] S6: Downlink data of lighting equipment, according to the equipment connection channel number channelId, sends the equipment protocol instruction data to the equipment side through the connection channel, and after receiving the instruction, executes the corresponding instruction.

[0056] S7: After the device command is sent through S6 and the device completes execution, the processing result is reported asynchronously for the listening queue set by the upper-level Command device command service instance to parse and process the uplink data. The processed data is sent to the upper-level functional component service + data component service for business processing, persistence, etc.

[0057] By executing the above steps S1-S7, the development and design of functional components + data components can be completed. Based on this component-based design model, each component unit can be defined and processed independently. The lower-level Command device instruction service and device communication service provide the lowest-level IoT protocol and control, communication and other capabilities for all components to ensure that each component only needs to focus on its own business processing. Finally, each component is given a globally unique code, schematic diagram and other basic information. Through the component library management module of the platform, the information of each component unit is entered to complete the presentation of the component units in the component library on the system. The components in this component library can be used in the visual system designer module to perform system applications and component configuration of industry platforms for different projects. For the detailed configuration process, please refer to the description of the visual system designer section.

[0058] Different projects can choose different style templates in the visual system designer module, and configure multiple application subsystems + multiple industry platform dashboards for a project. The style template determines the presentation style of the subsystem or industry platform page, including color scheme and layout. The components determine the integrated business functions and data functions of the subsystem or industry platform. The relationship between the subsystem, industry platform and component is maintained through a unique code, and is persisted to support the modification and expansion of the project application system + industry platform functions in the future. The relationship between the application subsystem and the industry platform dashboard and components under the project is as follows: Figure 4 .

[0059] In summary, when a new project introduces new requirements or the requirements of a deployed project are expanded, we only need to decompose the requirements a second time. For some customized requirements, we can quickly carry out parallel development of independent components. Most requirements only need to be imported to ordinary technicians, and the framework is built and the menu is configured based on the visual system designer. Through the provided visual interface and draggable functional components and data components, a customized IoT system or IoT industry platform can be quickly built, which greatly reduces the development workload, improves development efficiency, and shortens the project acceptance time.

[0060] All business functions of the IoT platform are encapsulated to form functional components and data components. Each component implements a specific function or a group of functions, and each component is independently developed, upgraded and maintained. The component-based development model lowers the technical threshold, improves R&D efficiency, and improves the maintainability, scalability and flexibility of the system. It can provide a visual system designer to quickly configure project requirements and freely drag and drop functional components to form a network according to market changes or business needs, realize the "thousand faces" of projects, quickly respond to market changes and business needs, shorten the R&D cycle, achieve cost reduction and efficiency improvement, and use automated scripts to deploy complex IoT platform deployment and update processes with one click, lowering the technical threshold for platform deployment and greatly improving platform deployment efficiency and accuracy.

[0061] The specific quantitative data comparison is as follows:

[0062] Comparison Dimensions Traditional Model Optimization Mode 1 component development efficiency 7 days 5 days 1 Project Configuration Efficiency 2 days 2 hours 1 Project Deployment Efficiency 3 days 3 hours

Claims

1. An Internet of Things system based on a component library with free configuration, characterized in that: It includes a base layer, a component layer, and an application system layer; the Internet of Things system is constructed through a visual system designer; the base layer includes a device communication base and an instruction parsing base; the component layer encapsulates platform services into independent component units, and the component units are divided into functional components and data components; the independently running system of the application system layer is formed by configuring various component units; the visual system designer can select or drag the required component units in a visual way to quickly complete the construction of the Internet of Things system.

2. According to claim 1, the Internet of Things system based on component library free configuration is characterized in that: The communication base is responsible for the communication access of the device, the instruction parsing base is responsible for the parsing and assembly of uplink and downlink instructions of different IoT devices, and encapsulates the general capability interface of the device according to the device classification for the component layer to call.

3. The Internet of Things system based on component library free configuration according to claim 1, characterized in that: The component layer is constructed to form a platform function component library and a data component library; the component unit includes a front-end interface, back-end services and interfaces; the component units are all built on the base layer, and the base layer supports the basic capabilities of the component units, including capability interfaces such as terminal device protocol parsing and device communication, to realize pluggable applications of component units on the base layer.

4. The Internet of Things system based on component library free configuration according to claim 1, characterized in that: The visual system designer includes a platform component selection area, a system page content layout area, a system menu configuration area, a system style setting area and a system page thumbnail display area.

5. The Internet of Things system based on component library free configuration according to claim 4 is characterized in that: The platform component selection area includes a visualization function component and a visualization data component, and the visualization function component and the visualization data component are derived from a packaged component unit; The system menu configuration area can customize the system multi-level menu module, define the function components and data array menu; The system page content layout area can provide a page template to present the content of the visual function component and the visual data component dragged to the template cell; The system style setting area can set the system page background image mode, including at least GIS map, BIM model and vector map; The system page thumbnail display area can display the configured menu pages.

Images