阅读说明：本技术 基于多场景应用的端边物联网平台架构 (End edge Internet of things platform architecture based on multi-scene application ) 是由 袁晓宇 潘群 杲靖 叶鸿 仲崇磊 蓝海倩 徐云霞 周文龙 于 2021-06-22 设计创作，主要内容包括：本发明提供基于多场景应用的端边物联网平台架构,包括物联网平台与物联网边缘网关系统,物联网平台包括核心服务处理单元与外部系统,核心服务处理单元包括传输微服务模块与JavaScript执行器微服务模块；物联网边缘网关系统包括：设备服务模块用于接入外部设备、采集设备数据并将获取的数据传输至核心数据微服务单元、加载并管理对应设备；核心服务模块为数据采集单元采集的数据提供集中存储、通过元数据微服务单元获取设备的配置信息、由设备微服务向设备转发命令、管理与物联网边缘网关系统连接并由其操作的设备的信息；应用服务模块,对感知数据进行提取、处理或转换并将它们从物联网边缘网管系统发送至用户指定的位置。(The invention provides a terminal edge Internet of things platform architecture based on multi-scene application, which comprises an Internet of things platform and an Internet of things edge gateway system, wherein the Internet of things platform comprises a core service processing unit and an external system, and the core service processing unit comprises a transmission micro-service module and a JavaScript actuator micro-service module; the edge gateway system of the Internet of things comprises: the device service module is used for accessing external devices, acquiring device data, transmitting the acquired data to the core data micro-service unit, and loading and managing corresponding devices; the core service module provides centralized storage for data acquired by the data acquisition unit, acquires configuration information of the equipment through the metadata micro-service unit, forwards a command to the equipment by the equipment micro-service, and manages information of the equipment connected with and operated by the Internet of things edge gateway system; and the application service module is used for extracting, processing or converting the sensing data and sending the sensing data to a position specified by a user from the Internet of things edge network management system.)

1. The terminal edge Internet of things platform architecture based on multi-scene application is characterized by comprising an Internet of things platform and an Internet of things edge gateway system, wherein the Internet of things platform comprises a core service processing unit and an external system, and the core service processing unit comprises a transmission micro-service module and a JavaScript actuator micro-service module;

the Internet of things edge gateway system comprises:

the device service module comprises a device management unit, a data acquisition unit and a device service unit, wherein the device management unit is used for accessing external devices, the data acquisition unit acquires device data through a sensor and an actuator and transmits the acquired data to the core data micro-service unit, and the device service unit can simultaneously serve one or more devices and load and manage the corresponding devices;

the core service module comprises a core data micro-service unit, a command micro-service unit and a metadata micro-service unit, the core data micro-service unit provides centralized storage for the data acquired by the data acquisition unit, and other systems and services can only access the acquired data through the core data micro-service unit; the command micro service unit acquires the configuration information of the equipment through the metadata micro service unit, and the equipment micro service forwards the command to the equipment through GET or PUT; the metadata service unit manages information of equipment connected with and operated by the Internet of things edge gateway system;

and the application service module is used for extracting, processing or converting the sensing data and sending the sensing data to a position designated by a user from the Internet of things edge network management system.

2. An end-edge internet-of-things platform architecture based on multi-scenario applications as claimed in claim 1, wherein in the external system, messages or data can be pushed from the internet-of-things platform to the external system through a rules engine, and the external system processes data and reports the processed results back to the internet-of-things platform for visualization.

3. An end-edge internet-of-things platform architecture based on multi-scenario applications as claimed in claim 1, wherein the device management unit implements data access through SDK toolkit and hardware interface, and the hardware interface comprises a wired interface and a wireless interface.

4. An end-edge internet-of-things platform architecture based on multi-scenario application according to claim 3, wherein the wired interface comprises RS-485, RS-232, Ethernet and USB interfaces, and the wireless interface comprises Bluetooth, LoRaWAN and CAN interfaces.

5. An end-edge internet-of-things platform architecture based on multi-scenario application according to claim 3, wherein the external device accessing method comprises the following steps:

s1, the device sends an access request, judges whether a corresponding interface exists on the Internet of things edge gateway system, if so, performs the step S2, and if not, performs the step S2 after the conversion is completed through the adapter;

s2, judging whether the Internet of things edge gateway system has equipment service of a corresponding protocol, if yes, entering a step S3, if no, applying an SDK tool to quickly generate and add equipment service of the protocol according to the protocol, and after the addition is finished, performing a step S3;

and S3, judging whether the equipment description file exists on the edge gateway system of the Internet of things, if so, adding equipment through an API (application programming interface), if not, generating the equipment description file according to a manual of the equipment to be added, adding the equipment description file into an equipment library, and adding the equipment through the API, so as to realize the access of the equipment.

6. The multi-scenario application-based end edge internet of things platform architecture of claim 1, wherein the data acquisition unit transmits data to the core data micro-processing unit through an RSET interface.

7. An end-edge internet-of-things platform architecture based on multi-scenario applications as claimed in claim 1, wherein the core data micro-service unit is further capable of performing protective collection on data when the data is at an edge.

8. An end-edge internet-of-things platform architecture based on multi-scenario applications as claimed in claim 1, wherein the command micro-service unit can also adjust the number of requests on the device and also cache responses if necessary.

9. The end-edge Internet of things platform architecture based on multi-scenario application of claim 1, wherein the device information collected by the metadata micro-service unit includes type and composition of data reported by the obtaining device and a command mode of the obtaining device.

Technical Field

The invention relates to the technical field of platform architecture of the Internet of things, in particular to a terminal side platform architecture of the Internet of things based on multi-scene application.

Background

The perfect combination of the intelligent terminal and the cloud is the future direction of artificial intelligence, and in the era of intelligent internet, the integration of equipment, artificial intelligence and services tends to be great. As more and more intelligent devices are used, the interconnection and interworking and cooperative application between the intelligent devices become more and more urgent and more important.

However, with the diversification of the access devices of the internet of things, the problem of device difference becomes more and more prominent, so that each application scene customization service is time-consuming and labor-consuming; PaaS service provided by an Internet of things platform is generally provided by a public cloud provider and can only be provided by depending on IaaS, so that the Internet of things service of an application scene cannot be flexibly deployed; some internet of things equipment manufacturers build own ecology, and provide data of users for the users through own platforms, so that the data of the users are seriously leaked.

The invention with the application number of CN108270855A provides a method for accessing equipment to an Internet of things platform, which comprises the following steps: the access equipment is required to be equipment capable of operating an MQTT client and provided with a complete TCP/IP protocol stack, the platform equipment is a server supporting the MQTT protocol and is responsible for receiving and sending the whole MQTT protocol, the platform system provides equipment access service, data gateway service, automation service, data report service and application service, communication among the equipment access service, the data gateway service, the automation service, the data report service and the application service is realized through remote process calling, the platform system adopts a micro-service architecture and operates in a virtual containerization mode through Docker, each service is a Docker container, the platform system is provided with a Web page end and a mobile APP client, corresponding requirements and limits are provided for the access equipment and the server, the application range is narrow, and the Internet of things service of an application scene cannot be deployed flexibly.

Disclosure of Invention

The invention aims to provide an end edge Internet of things platform architecture based on multi-scenario application, and the customized service requirements of the Internet of things in different application scenarios can be quickly and conveniently realized.

The invention provides the following technical scheme:

the terminal edge Internet of things platform architecture based on multi-scene application comprises an Internet of things platform and an Internet of things edge gateway system, wherein the Internet of things platform comprises a core service processing unit and an external system, and the core service processing unit comprises a transmission micro-service module and a JavaScript actuator micro-service module;

the Internet of things edge gateway system comprises:

the device service module comprises a device management unit, a data acquisition unit and a device service unit, wherein the device management unit is used for accessing external devices, the data acquisition unit acquires device data through a sensor and an actuator and transmits the acquired data to the core data micro-service unit, and the device service unit can simultaneously serve one or more devices and load and manage the corresponding devices;

the core service module comprises a core data micro-service unit, a command micro-service unit and a metadata micro-service unit, the core data micro-service unit provides centralized storage for the data acquired by the data acquisition unit, and other systems and services can only access the acquired data through the core data micro-service unit; the command micro service unit acquires the configuration information of the equipment through the metadata micro service unit, and the equipment micro service forwards the command to the equipment through GET or PUT; the metadata service unit manages information of equipment connected with and operated by the Internet of things edge gateway system;

and the application service module is used for extracting, processing or converting the sensing data and sending the sensing data to a position designated by a user from the Internet of things edge network management system.

Preferably, in the external system, a message or data can be pushed from the internet of things platform to the external system through a rule engine, and the external system processes the data and reports the processing result back to the internet of things platform for visualization.

Preferably, the device management unit implements data access through an SDK kit and a hardware interface, where the hardware interface includes a wired interface and a wireless interface.

Preferably, the wired interface comprises RS-485, RS-232, Ethernet and USB interfaces, and the wireless interface comprises Bluetooth, LoRaWAN and CAN interfaces.

Preferably, the method for accessing the external device includes the following steps:

s1, the device sends an access request, judges whether a corresponding interface exists on the Internet of things edge gateway system, if so, performs the step S2, and if not, performs the step S2 after the conversion is completed through the adapter;

s2, judging whether the Internet of things edge gateway system has equipment service of a corresponding protocol, if yes, entering a step S3, if no, applying an SDK tool to quickly generate and add equipment service of the protocol according to the protocol, and after the addition is finished, performing a step S3;

and S3, judging whether the equipment description file exists on the edge gateway system of the Internet of things, if so, adding equipment through an API (application programming interface), if not, generating the equipment description file according to a manual of the equipment to be added, adding the equipment description file into an equipment library, and adding the equipment through the API, so as to realize the access of the equipment.

Preferably, the data acquisition unit transmits data to the core data microprocessing unit through an RSET interface.

Preferably, the core data micro-service unit can also perform protective collection on the data when the data is at the edge.

Preferably, the command microserver may also adjust the number of requests on the device and may also cache responses if necessary.

Preferably, the device information collected by the metadata microservice unit includes the type and composition of data reported by the acquisition device, and the command mode of the acquisition device.

The invention has the beneficial effects that: the invention relates to the access of equipment, unifies interfaces, and realizes the decoupling of upper application and a system and equipment of a sensing equipment manufacturer; the invention realizes the multi-protocol and multi-mode wide access to the lower layer whole network monitoring sensing equipment, the unified management and the data aggregation of the network stock and the newly built sensing equipment; the access of multiple protocols such as CoAP, MQTT, Modbus, OPC, LoRa and the like is supported; the invention realizes management and data acquisition of stock sensing equipment to the established data acquisition system of the existing network, standardizes data service, and quickly and conveniently realizes customized service requirements of the Internet of things in different application scenes by utilizing a terminal side Internet of things system framework consisting of an Internet of things edge network relation and an Internet of things platform.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:

FIG. 1 is a block diagram of the system architecture of the present invention;

FIG. 2 is an overall architecture diagram of the platform of the Internet of things of the invention;

FIG. 3 is an Internet of things edge gateway system architecture diagram of the present invention;

FIG. 4 is a diagram of an Internet of things edge gateway system loosely coupled service framework of the present invention;

fig. 5 is a device management access flow diagram of the device management unit of the present invention;

FIG. 6 is a device service module program logic diagram of the present invention;

FIG. 7 is a program logic diagram of an application service module of the present invention.

Detailed Description

Example one

As shown in fig. 1, an end-edge internet of things platform architecture based on multi-scenario application includes an internet of things platform and an internet of things edge gateway system.

As shown in fig. 2, the internet of things platform includes a core service processing unit and an external system, the core service processing unit includes a transmission micro-service module and a JavaScript executor micro-service module, wherein in the external system, a message or data can be pushed from the internet of things platform to the external system through a rule engine, and the external system processes the data and reports a processing result back to the internet of things platform for visualization.

As shown in fig. 3, the internet of things edge gateway system is a cross-platform interoperable network edge system. IT can interact with devices, sensors, actuators and other IoT objects in the physical world, providing services between sensors and actuators and IT systems, which is a bridge connecting "things" and "clouds" in the internet of things.

As shown in fig. 1 to 6, the internet of things edge gateway system includes:

the equipment service module comprises an equipment management unit, a data acquisition unit and an equipment service unit.

The device management unit is used for accessing an external device;

the data acquisition unit acquires equipment data through a sensor and an actuator and transmits the acquired data to the core data micro-service unit, wherein the equipment service uses a communication protocol of the sensor to acquire the data, the core data micro-service unit stores the sensor data in a local edge database, Redis is used as the database by default, other databases can be selected, and the function can be closed if the data does not need to be stored in actual use;

the device service unit can simultaneously service one or more devices, load and manage the corresponding devices, wherein the devices managed by the device service may not be simple and single physical devices, the devices may be an edge/internet of things gateway (and all devices connected to the gateway), a device manager, a sensor concentrator, a web service provided by HTTP, or a software sensor as one device or as a collection of devices onto the edge gateway.

In summary, the facility service provides the common scaffolding code and convenient method required by all facility services, making it easier to create facility services, and using the SDK also helps to ensure that facility services comply with the rules required by facility services.

Further, all the equipment service modules complete the following tasks:

(1) registering with a core metadata service: let the edge gateway know that it is running and can manage the apparatus at any time, obtain all new information rapidly;

(2) acquiring configuration information from a configuration service of the edge gateway, and acquiring a configuration file from local if the configuration service is not used;

(3) registering its edge gateway runtime microservice with a registry service (runtime) to allow other gateway services to communicate with it;

(4) loading and managing physical devices that it knows how to communicate, a process called device configuration, in some cases device services may have a way to automatically detect and configure devices;

(5) monitoring for configuration changes and applying the new configuration if appropriate, but in some cases not dynamically applying configuration changes (e.g., changing the operational port of a device service);

(6) and acquiring sensor data (namely acquiring the sensor data), and transmitting the data to the core data microservice through the REST interface.

As shown in fig. 1-4 and 7, the core service module includes a core data micro-service unit, a command micro-service unit and a metadata micro-service unit.

The core data micro-service unit provides centralized storage for the data acquired by the data acquisition unit, other systems and services can only access the acquired data through the core data micro-service unit, and the core data micro-service unit can also perform protective acquisition on the data when the data is positioned at the edge;

the command micro service unit acquires the configuration information of the equipment through the metadata micro service unit, and forwards a command to the equipment through GET or PUT by the equipment micro service, wherein the command or action request is from the north side of the edge gateway system of the Internet of things to the equipment service of a specific protocol and the proxy service of related equipment, and the command micro service unit is not directly communicated with the equipment; command microservices may provide a layer of protection around a device, may add additional security, and do not allow unnecessary interaction with the device (through device servicing); the command service may also adjust the number of requests on the device to avoid overloading the device, and may even cache responses if necessary to avoid waking the device;

the metadata service unit manages information of equipment connected with and operated by the Internet of things edge gateway system, wherein the equipment information comprises types and compositions of data reported by the equipment and a command mode of the equipment.

In summary, when several instances of the internet of things edge gateway system are simultaneously sent to a central location, it is crucial for the core service module to associate the data with its source, which may be specified by the GPS location of the sensor, the name or Identification (ID) of the sensor, the name or identification of some edge gateway that originally collected the data, or many other ways;

the internet of things edge gateway system may tag event data with a "tag," and the event object has a Tags attribute, which is a key/value pair mapping, throughout all the microservices that make up the system, allowing any service that creates or otherwise handles an event to add custom tag information to the event to help identify its source or otherwise identify it before it is sent to the north side.

As shown in fig. 1 to 7, the application service module extracts, processes or converts the sensing data and sends them from the internet of things edge network management system to a location designated by a user, and at the same time, the application service module can process events of the internet of things edge gateway system (and sensor data contained therein and transmit them to the data analysis package). By default, the data analysis package may replace or augment the local rules engine.

Example two

As shown in fig. 5, compared with the first embodiment, the device management unit in this embodiment implements data access through the SDK kit and the hardware interface, and adopts a flexible access manner, thereby facilitating fast access to the device.

The hardware interface comprises a wired interface and a wireless interface, wherein the wired interface comprises RS-485, RS-232, Ethernet and a USB interface, and the wireless interface comprises Bluetooth, LoRaWAN and CAN interfaces.

The access method of the external equipment comprises the following steps:

s1, the equipment sends an access request, whether a corresponding interface exists on the edge gateway system of the Internet of things is judged, if yes, the step S2 is carried out, and if no interface exists, the step S2 is carried out after the conversion is finished through the adapter;

s2, judging whether equipment services of a corresponding protocol exist on the edge gateway system of the Internet of things, if so, entering a step S3, if not, rapidly generating and adding the equipment services of the protocol according to the protocol by applying an SDK tool, and after the addition is finished, carrying out a step S3;

and S3, judging whether an equipment description file exists on the edge gateway system of the Internet of things, if so, adding equipment through an API (application programming interface), if not, generating the equipment description file according to a manual of the equipment to be added, adding the equipment description file into an equipment library, and adding the equipment through the API, so as to realize the access of the equipment.

Other components and principles of the present embodiment are the same as those of the first embodiment.

In conclusion, the invention realizes the decoupling of the upper application and the manufacturer system and the equipment of the sensing equipment by the access and unified interface of the equipment; the invention realizes the multi-protocol and multi-mode wide access to the lower layer whole network monitoring sensing equipment, the unified management and the data aggregation of the network stock and the newly built sensing equipment; the access of multiple protocols such as CoAP, MQTT, Modbus, OPC, LoRa and the like is supported; the invention realizes management and data acquisition of stock sensing equipment to the established data acquisition system of the existing network, standardizes data service, and quickly and conveniently realizes customized service requirements of the Internet of things in different application scenes by utilizing a terminal side Internet of things system architecture consisting of an Internet of things edge network relation and an Internet of things platform.

Although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that changes may be made in the embodiments and/or equivalents thereof without departing from the spirit and scope of the invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.