CN112039983B - Method and system for realizing connection middleware of Internet of things equipment - Google Patents
Method and system for realizing connection middleware of Internet of things equipment Download PDFInfo
- Publication number
- CN112039983B CN112039983B CN202010886798.XA CN202010886798A CN112039983B CN 112039983 B CN112039983 B CN 112039983B CN 202010886798 A CN202010886798 A CN 202010886798A CN 112039983 B CN112039983 B CN 112039983B
- Authority
- CN
- China
- Prior art keywords
- equipment
- terminal equipment
- middleware
- terminal
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000007726 management method Methods 0.000 claims description 22
- 238000004458 analytical method Methods 0.000 claims description 12
- 238000007405 data analysis Methods 0.000 claims description 8
- 238000012544 monitoring process Methods 0.000 claims description 5
- 238000012423 maintenance Methods 0.000 claims description 4
- 238000013523 data management Methods 0.000 claims description 3
- 239000008186 active pharmaceutical agent Substances 0.000 claims 2
- 230000006855 networking Effects 0.000 claims 1
- 238000004088 simulation Methods 0.000 claims 1
- QVFWZNCVPCJQOP-UHFFFAOYSA-N chloralodol Chemical compound CC(O)(C)CC(C)OC(O)C(Cl)(Cl)Cl QVFWZNCVPCJQOP-UHFFFAOYSA-N 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y40/00—IoT characterised by the purpose of the information processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method and a system for realizing the connection of internet of things equipment with middleware, wherein the method comprises the following steps: the terminal equipment is connected with the equipment middleware through a standard protocol or a private protocol; the equipment middleware acquires the attribute, service and event of the connected terminal equipment and generates a corresponding terminal equipment shadow according to the attribute, service and event; when the application platform issues an instruction to the terminal equipment, the equipment middleware receives the instruction by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment; when the terminal equipment uploads data to the application platform, the equipment middleware receives the data by utilizing the shadow of the terminal equipment corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform. The invention can realize the effect of accessing the terminal equipment in charge of the lower part and uploading data to the application platform in charge of the upper part through the equipment middleware.
Description
Technical Field
The invention relates to the technical field of middleware of the Internet of things, in particular to a method and a system for realizing the connection of equipment of the Internet of things with the middleware.
Background
The internet of things IoT (Internetofthings) is a network for connecting objects with each other and people with the objects through the internet and exchanging and communicating information so as to realize intelligent identification, positioning, tracking, monitoring and management of the objects.
With the gradual entering of the transformation period of the property industry and the property industry, the terminal equipment of the Internet of things is quickly accessed by means of the technology of the Internet of things, the terminal equipment data are acquired, the data are integrated for application, and a digital platform of the terminal equipment data is built, so that the terminal equipment data are the digital transformation key input field of various large-scale properties and property companies. In the process of actively attempting intelligent propulsion of property and property, AIoT (artificial intelligence internet of things) is selected as a most important technology access point, and in AIoT, connection with various edge terminal devices is a most basic capability. In the prior implementation process of the related service system and platform, the terminal equipment is in butt joint. However, with the deep service, the defects of the modes of the terminal equipment access work, the strong coupling of the terminal equipment access and the upper layer service and the like are gradually reflected. That is, each product has a respective terminal device connection module, and although the respective directions of emphasis are different, the related general parts (such as authentication, connection management, etc.) need to be implemented, which results in waste of human resources and is not beneficial to accumulation of technical depth.
In addition, the coupling degree requirements of the access part of the terminal equipment and each product are higher, when a plurality of products are required to be combined and delivered, the whole set of products are required to be carried, but the requirements can be met by only the functions of a certain type of terminal equipment, so that the carrying of the whole set of products can cause the increase of cost. Meanwhile, when the personalized requirements are met, modification on a baseline product may be needed, but the response speed to the client requirements is slow due to excessive carried products, the version management difficulty of the products is high, and when the products are provided for a third party platform for docking, excessive precondition constraint and relationship mapping exist in the docking process, so that the time and the labor are consumed. And when more terminal devices are accessed later, the logic of the platform is more complicated, which is more unfavorable for product management.
Disclosure of Invention
The embodiment of the invention provides a method and a system for realizing equipment connection middleware of an Internet of things, and aims to provide equipment middleware which is responsible for accessing terminal equipment and uploading data to an application platform.
The embodiment of the invention provides a method for realizing the connection of Internet of things equipment with middleware, which comprises the following steps:
the terminal equipment is connected with the equipment middleware through a standard protocol or a private protocol;
the equipment middleware acquires the attribute, service and event of the connected terminal equipment and generates a corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment;
when an application platform issues an instruction to terminal equipment, the equipment middleware receives the instruction by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment;
when the terminal equipment uploads data to the application platform, the equipment middleware receives the data by utilizing the terminal equipment shadow corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform.
Further, the method further comprises the following steps:
creating and saving a device model in the device middleware;
selecting a device type in an application platform, acquiring a corresponding device model from the device middleware, and configuring device basic information according to the device model;
generating a corresponding terminal equipment shadow in the equipment middleware according to the equipment basic information;
and adding equipment configuration information in an application platform, submitting the equipment configuration information to the equipment middleware, and configuring the shadow of the terminal equipment.
Further, when the application platform issues an instruction to the terminal device, the device middleware receives the instruction by using a terminal device shadow corresponding to the terminal device, parses the instruction into a format adapted to the terminal device, and then issues the parsed instruction to the terminal device, including:
receiving data or instructions issued by an application platform through the shadow of the terminal equipment;
judging whether the corresponding terminal equipment is in an online state or not;
if the terminal equipment is in the on-line state, analyzing the data or the instruction into a format adapted to the terminal equipment, and issuing the analyzed data or instruction to the terminal equipment;
if the terminal equipment is judged not to be in the on-line state, storing the data or the instruction, and continuously judging whether the terminal equipment is in the on-line state;
and after the data or the instruction is successfully issued, carrying out state synchronization on the shadow of the terminal equipment according to the state of the terminal equipment.
Further, when the terminal device uploads data to the application platform, the device middleware receives the data by using a terminal device shadow corresponding to the terminal device, parses and encapsulates a format of the data, and sends the encapsulated data to the application platform, including:
acquiring data of corresponding terminal equipment through the shadow of the terminal equipment, and analyzing the data into a format adapted to an application platform;
if the data analysis is successful, storing and reporting the analyzed data to an application platform;
if the data analysis fails, a log of the analysis failure is stored in the shadow of the terminal equipment.
Further, the method further comprises the following steps:
when the equipment middleware receives a terminal equipment connection request, the equipment middleware matches the equipment model with the terminal equipment;
if the matching is successful, allowing the terminal equipment to access the equipment middleware;
if the matching fails, acquiring the attribute, the event and the service of the terminal equipment, creating an equipment model according to the attribute, the event and the service of the terminal equipment, matching the created equipment model with the terminal equipment, and allowing the terminal equipment to be accessed.
Further, after the device middleware obtains the attribute, service and event of the connected terminal device and generates a corresponding shadow of the terminal device according to the attribute, service and event of the terminal device, the device middleware includes:
and uploading the attribute, the event and the service of the shadow of the terminal equipment to an application platform by the equipment middleware, and setting a corresponding instruction for the terminal equipment by the application platform according to the attribute, the event and the service of the shadow of the terminal equipment.
Further, the terminal device is connected with the device middleware through a standard protocol or a private protocol, and includes:
the equipment middleware analyzes the protocol of the terminal equipment to enable the protocol of the terminal equipment to be adapted to an application platform.
The embodiment of the invention also provides a middleware system for connecting the Internet of things equipment, which comprises the following steps: terminal equipment, equipment middleware and an application platform;
the terminal equipment is used for connecting with the equipment middleware through a standard protocol or a private protocol;
the equipment middleware is used for acquiring the attribute, service and event of the connected terminal equipment and generating a corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment; when an application platform issues an instruction to terminal equipment, the equipment middleware receives the instruction by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment; when the terminal equipment uploads data to the application platform, the equipment middleware receives the data by utilizing the terminal equipment shadow corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform.
Further, the equipment middleware is also used for creating and storing an equipment model;
the application platform is used for selecting equipment types, acquiring corresponding equipment models from the equipment middleware and configuring equipment basic information according to the equipment models; generating a corresponding terminal equipment shadow in the equipment middleware according to the equipment basic information; and adding equipment configuration information, submitting the equipment configuration information to the equipment middleware, and configuring the shadow of the terminal equipment.
Further, the device middleware is further configured to receive data or instructions issued by an application platform through the shadow of the terminal device; judging whether the corresponding terminal equipment is in an online state or not; if the terminal equipment is in the on-line state, analyzing the data or the instruction into a format adapted to the terminal equipment, and issuing the analyzed data or instruction to the terminal equipment; if the terminal equipment is judged not to be in the on-line state, storing the data or the instruction, and continuously judging whether the terminal equipment is in the on-line state; and after the data or the instruction is successfully issued, carrying out state synchronization on the shadow of the terminal equipment according to the state of the terminal equipment.
The embodiment of the invention provides a method and a system for realizing the connection of Internet of things equipment with middleware, wherein the method comprises the following steps: the terminal equipment is connected with the equipment middleware through a standard protocol or a private protocol; the equipment middleware acquires the attribute, service and event of the connected terminal equipment and generates a corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment; when an application platform issues an instruction to terminal equipment, the equipment middleware receives the instruction by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment; when the terminal equipment uploads data to the application platform, the equipment middleware receives the data by utilizing the terminal equipment shadow corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform. According to the embodiment of the invention, the equipment middleware generates the corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment, so that the aim of accessing the terminal equipment in charge of lower responsibility and uploading data to the application platform in charge of upper responsibility is fulfilled.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic flow chart of an implementation method of an internet of things device connection middleware according to an embodiment of the present invention;
fig. 2 is a schematic sub-flowchart of an implementation method of an internet of things device connection middleware according to an embodiment of the present invention;
fig. 3 is another schematic sub-flowchart of an implementation method of an internet of things device connection middleware according to an embodiment of the present invention;
fig. 4 is a basic frame diagram of an implementation method of an internet of things device connection middleware according to an embodiment of the present invention;
fig. 5 is a schematic architecture diagram of an internet of things device connection middleware system according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
Referring to fig. 1, fig. 1 is a schematic flow chart of an implementation method of an internet of things device connection middleware according to an embodiment of the present invention, which specifically includes: steps S101 to S104.
S101, connecting terminal equipment with equipment middleware through a standard protocol or a private protocol;
s102, the equipment middleware acquires the attribute, service and event of the connected terminal equipment, and generates a corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment;
s103, when an application platform issues an instruction to a terminal device, the device middleware receives the instruction by utilizing a terminal device shadow corresponding to the terminal device, analyzes the instruction into a format adapted to the terminal device, and then issues the analyzed instruction to the terminal device;
and S104, when the terminal equipment uploads the data to the application platform, the equipment middleware receives the data by utilizing the terminal equipment shadow corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform.
In this embodiment, the device middleware abstracts a corresponding shadow of the terminal device according to the attribute, service and event of the terminal device, that is, the device middleware has the same attribute, service and event as the terminal device, so as to provide for the application platform to call, and manages the terminal device when the terminal device is accessed, for example, data transmission, protocol analysis and the like. When the application platform needs to call the service of the terminal equipment, the application platform can realize the issuing of data (or instructions) through the corresponding shadow of the terminal equipment; when the terminal equipment needs to upload data to the application platform, the data uploading can be realized according to the shadow of the corresponding terminal equipment, so that the purposes of accessing the terminal equipment in charge of lower responsibility and uploading the data to the application platform in charge of upper responsibility are realized.
According to the embodiment, the equipment middleware analyzes the protocol of the terminal equipment, and uploads data to the application platform after the analysis is completed, and the equipment middleware shields the access difference and complexity of the terminal equipment for the application platform. And as the terminal equipment butted by the equipment middleware is more and more comprehensive, the access capability of the terminal equipment can be quickly multiplexed for different solutions, and the time for the application platform to butt the terminal equipment is greatly reduced. Meanwhile, the equipment middleware supports connection of various protocols, terminal equipment and networks, and the terminal equipment, the system and the like can be interconnected, intercommunicated and interchanged through the equipment middleware.
It should be noted that, the attribute of the terminal device described in this embodiment is generally used to describe the state of the terminal device during operation, such as the current ambient temperature read by the temperature sensor; the service of the terminal equipment represents the capability or method of the terminal equipment which can be called by the outside, such as the capability of the temperature sensor which can be called by the application platform to collect the real-time temperature value of the current environment, etc.; the event of the terminal equipment represents the event when the terminal equipment operates, such as the generation of high-temperature alarm by a temperature sensor. In addition, the standard protocols described in this embodiment include standard protocols such as WiFi, 4G, and 5G, and the proprietary protocols include Modbus protocol (a serial communication protocol), lora protocol (a wide area network wireless protocol), and the like.
In an embodiment, as shown in fig. 2, the method for implementing the middleware for connecting the internet of things device further includes:
s201, creating and storing a device model in the device middleware;
s202, selecting a device type in an application platform, acquiring a corresponding device model from the device middleware, and configuring device basic information according to the device model;
s203, generating a corresponding terminal device shadow in the device middleware according to the device basic information;
s204, adding device configuration information in an application platform, submitting the device configuration information to the device middleware, and configuring the shadow of the terminal device.
In this embodiment, when the application platform needs to display or call the service of the terminal device, a device model meeting the service requirement may be selected from the device model(s) created by the device middleware, and device basic information and device configuration information may be added to the selected device model. The equipment middleware generates a corresponding terminal equipment shadow according to the equipment basic information and configures the terminal equipment shadow according to the equipment configuration information.
For example, when the application platform needs to display the temperature condition in the current environment, a temperature sensor device needs to be added, the device middleware provides a corresponding temperature sensor device model, the application platform adds device basic information for the temperature sensor device model, the device middleware generates a corresponding temperature sensor device shadow according to the device basic information, then the application platform adds device configuration information for the temperature sensor device shadow, and the device middleware configures the temperature sensor device according to the device configuration information, so that a temperature sensor display list (application platform) -temperature sensor device shadow (device middleware) -temperature sensor (terminal device) link is formed.
In one embodiment, as shown in fig. 3, the step S103 includes:
s301, receiving data or instructions issued by an application platform through the shadow of the terminal equipment;
s302, judging whether corresponding terminal equipment is in an online state or not;
s303, if the terminal equipment is judged to be in an on-line state, analyzing the data or the instruction into a format adapted to the terminal equipment, and issuing the analyzed data or instruction to the terminal equipment;
s304, if the terminal equipment is not in the online state, storing the data or the instruction, and continuously judging whether the terminal equipment is in the online state;
and S305, after the data or the instruction is successfully issued, carrying out state synchronization on the shadow of the terminal equipment according to the state of the terminal equipment.
In this embodiment, when the device middleware receives data or an instruction issued by an application platform, it is first determined whether a terminal device receiving the data or the instruction is in an on-line state, so as to avoid that the device middleware cannot issue the data or the instruction to the terminal device after analyzing the data or the instruction. If the terminal equipment is in an on-line state, after analyzing the data or the instruction, issuing the data or the instruction to the terminal equipment, and executing corresponding operation by the terminal equipment according to the data or the instruction; if the terminal equipment is not in the on-line state, the data or the instruction is not analyzed temporarily, but the data or the instruction is stored, and whether the terminal equipment is in the state is continuously judged until the data or the instruction is successfully issued to the terminal equipment. And after the data or the equipment is successfully issued, the equipment middleware synchronously updates the state of the shadow of the terminal equipment corresponding to the terminal equipment.
If there are a plurality of terminal devices corresponding to the application platform, the device middleware may determine, according to the received data or instructions, the terminal device that ultimately receives the data or instructions, and then determine whether the terminal device is in an online state; if only one terminal device exists corresponding to the application platform, the device middleware can directly judge whether the terminal device is in an on-line state after receiving the data or the instruction.
In one embodiment, the step S104 includes:
acquiring data of corresponding terminal equipment through the shadow of the terminal equipment, and analyzing the data into a format adapted to an application platform;
if the data analysis is successful, storing and reporting the analyzed data to an application platform;
if the data analysis fails, a log of the analysis failure is stored in the shadow of the terminal equipment.
In this embodiment, after acquiring the data of the terminal device, the device middleware analyzes the acquired data, so that the analyzed data format can be adapted to the application platform, and reports the data after the analysis is successful. When the analysis of the data fails, the data cannot be reported, or the reported data cannot be received by the application platform, at this time, a log of the analysis failure can be stored first, so that the equipment middleware can analyze or execute other operations again later.
For example, the temperature sensor uploads the collected data to the equipment middleware, and the equipment middleware obtains the data uploaded by the temperature sensor through the shadow of the temperature sensor equipment, analyzes the data into a temperature value which can be supplied to the application platform for display, and pushes the temperature value to the application platform.
In an embodiment, the method for implementing the middleware for connecting the internet of things device further includes:
when the equipment middleware receives a terminal equipment connection request, the equipment middleware matches the equipment model with the terminal equipment;
if the matching is successful, allowing the terminal equipment to access the equipment middleware;
if the matching fails, acquiring the attribute, the event and the service of the terminal equipment, creating an equipment model according to the attribute, the event and the service of the terminal equipment, matching the created equipment model with the terminal equipment, and allowing the terminal equipment to be accessed.
In this embodiment, when the device middleware accesses to the terminal device, the device model that has been created and stored is first matched with the terminal device to be accessed, and it is determined whether the device model corresponding to the terminal device is created in the device middleware. If the matching is successful, judging that a device model corresponding to the terminal device is created in the device middleware, namely, the attribute, the event and the service of the terminal device are stored, so that the terminal device can be directly accessed; if the matching fails, it is determined that the device model corresponding to the terminal device is not created in the device middleware, that is, the attribute, the event and the service corresponding to the terminal device are not stored, but the device model corresponding to the terminal device can be created according to the attribute, the event and the service of the terminal device in order that the terminal device can be directly called after being accessed, and then the terminal device is accessed. Of course, after the device model is created, matching still needs to be performed, and after matching is successful, the terminal device is allowed to access.
In an embodiment, after the device middleware obtains the attribute, service and event of the connected terminal device and generates a corresponding shadow of the terminal device according to the attribute, service and event of the terminal device, the method includes:
and uploading the attribute, the event and the service of the shadow of the terminal equipment to an application platform by the equipment middleware, and setting a corresponding instruction for the terminal equipment by the application platform according to the attribute, the event and the service of the shadow of the terminal equipment.
In this embodiment, the device middleware uploads the attribute, event and service of the corresponding terminal device to the application platform through the shadow of the terminal device, and then the application platform sets an instruction for the corresponding terminal device according to the received attribute, event and service, and can directly issue the set instruction to the device middleware when the data of the terminal device needs to be acquired. For example, the terminal device shadow corresponding to the device middleware temperature sensor uploads the attribute, service and event of the temperature sensor to the application platform, and then the application platform can set an instruction about acquiring temperature data or acquiring the temperature data according to the attribute, service and event.
In an embodiment, the terminal device connects with the device middleware through a standard protocol or a proprietary protocol, including:
the equipment middleware analyzes the protocol of the terminal equipment to enable the protocol of the terminal equipment to be adapted to an application platform.
In this embodiment, since the protocols supported by different terminal devices may be different, in order to enable the terminal devices to adapt to the application platform, the device middleware parses the protocols supported by the terminal devices after receiving the access request of the terminal devices. For example, the protocol supported by the temperature sensor and some other type of sensor is the modbus protocol, which is transmitted through an intelligent gateway (e.g., an intelligent home gateway, etc.), and the device middleware parses the modbus protocol into a Netty (an open framework) service group, so that the temperature sensor or other type of sensor is adapted to a corresponding application platform.
In a specific embodiment, as shown in fig. 4, the terminal device includes an IP device and a non-IP device, where the IP device accesses the device middleware through http(s), MQTT (message queue telemetry transport), SIP (session initiation protocol), a private protocol, and the like, and may directly perform TCP/IP protocol transmission with the device middleware or perform TCP/IP protocol transmission with the device middleware through a gateway; the non-IP equipment is accessed into the equipment middleware through protocols such as Modbus, zigBee, BLE (Bluetooth low energy consumption), lora and the like, and TCP/IP protocol transmission is carried out with the equipment middleware through a gateway.
The equipment middleware performs equipment management, equipment access, operation and maintenance monitoring and the like on the accessed terminal equipment, wherein the equipment management specifically comprises type management, analog management, equipment grouping and shadow equipment; the equipment access specifically comprises connection management, protocol analysis, data management, instruction management and the like. The middle of the device also provides functions of a rule engine, an open API, a console and the like.
The service application (i.e. application platform) and the equipment middleware are transmitted through protocols such as http(s), RPC (remote procedure call), MQTT (request message traffic) and the like, and the service application specifically comprises services such as space and scene solutions, operation and maintenance and monitoring platforms, third party applications and the like.
Furthermore, the device middleware is further provided with an adaptation layer, which is used for adapting the protocol of the terminal device. Specifically, the device middleware adapts a modelbus protocol (i.e., modbus) of a terminal device (such as a temperature and humidity sensor, a smoke sensor, etc.) through a Netty service group (a private protocol cluster), wherein the modelbus protocol is transmitted through an intelligent gateway (such as an intelligent home gateway, an EBA gateway, etc.); the device middleware can also adapt to the lora and wan protocols of some terminal devices (such as geomagnetism, intelligent lighting devices and the like) through a lora, wan, MQTT cluster, wherein the lora and wan protocols are transmitted through a lora gateway; the device middleware can also adapt vendor protocols of some terminal devices (such as third party devices) through other collection server clusters for interfacing with the third party devices; the device middleware can also adapt to SDK (software development kit)/TCP protocol of some terminal devices (such as monitoring devices, access control devices and the like) through an audio and video processing cluster.
Fig. 5 is a schematic architecture diagram of a middleware system for connecting devices of the internet of things, which includes: terminal device 501, device middleware 502 and application platform 503;
the terminal device 501 is configured to connect with the device middleware 502 through a standard protocol or a proprietary protocol;
the device middleware 502 is configured to obtain attributes, services, and events of the connected terminal device 501, and generate a corresponding terminal device shadow according to the attributes, services, and events of the terminal device 501; when the application platform 503 issues an instruction to the terminal device 501, the device middleware 502 receives the instruction by using a terminal device shadow corresponding to the terminal device 501, parses the instruction into a format adapted to the terminal device 501, and then issues the parsed instruction to the terminal device 501; when the terminal device 501 uploads data to the application platform 503, the device middleware 502 receives the data by using a terminal device shadow corresponding to the terminal device 501, parses and encapsulates a format of the data, and sends the encapsulated data to the application platform 503.
In one embodiment, the device middleware 502 is further configured to create and save a device model;
the application platform 503 is configured to select a device type and obtain a corresponding device model from the device middleware 502, and configure device basic information according to the device model; generating a corresponding terminal device shadow in the device middleware 502 according to the device basic information; and adding equipment configuration information, submitting the equipment configuration information to the equipment middleware, and configuring the shadow of the terminal equipment.
In an embodiment, the device middleware 502 is further configured to receive, through the shadow of the terminal device, data or instructions issued by the application platform 503; judging whether the corresponding terminal device 501 is in an on-line state; if it is determined that the terminal device 501 is in an online state, the data or the instruction is parsed into a format adapted to the terminal device 501, and the parsed data or instruction is issued to the terminal device 501; if it is determined that the terminal device 501 is not in an online state, storing the data or the instruction, and continuously determining whether the terminal device 501 is in an online state; after the data or the instruction is issued successfully, the state synchronization is performed on the shadow of the terminal device according to the state of the terminal device 501.
In an embodiment, the device middleware 502 is further configured to obtain data of the corresponding terminal device 501 through the shadow of the terminal device, and parse the data into a format adapted to the application platform 503; if the data analysis is successful, storing and reporting the analyzed data to the application platform 503; if the data analysis fails, a log of the analysis failure is stored in the shadow of the terminal equipment.
In an embodiment, the device middleware 502 is further configured to, when the device middleware 502 receives a connection request of a terminal device 501, match the device model with the terminal device 501 by the device middleware 502; if the matching is successful, allowing the terminal equipment 501 to access the equipment middleware; if the matching fails, the attribute, the event and the service of the terminal equipment 501 are acquired, a device model is created according to the attribute, the event and the service of the terminal equipment 501, then the created device model is matched with the terminal equipment 501, and then the terminal equipment 501 is allowed to be accessed.
In an embodiment, the device middleware 502 is further configured to upload the attribute, the event and the service of the shadow of the terminal device to the application platform 503, and set, by the application platform 503, a corresponding instruction for the terminal device 501 according to the attribute, the event and the service of the shadow of the terminal device.
In an embodiment, the device middleware 502 is further configured to parse a protocol of the terminal device 501, so that the protocol of the terminal device 501 is adapted to the application platform 503.
Since the embodiments of the system portion and the embodiments of the method portion correspond to each other, the embodiments of the system portion refer to the description of the embodiments of the method portion, which is not repeated herein.
In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. For the system disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section. It should be noted that it would be obvious to those skilled in the art that various improvements and modifications can be made to the present application without departing from the principles of the present application, and such improvements and modifications fall within the scope of the claims of the present application.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Claims (4)
1. The method for realizing the connection of the Internet of things equipment with the middleware is characterized by comprising the following steps:
the terminal equipment is connected with the equipment middleware through a standard protocol or a private protocol;
the equipment middleware acquires the attribute, service and event of the connected terminal equipment and generates a corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment;
when an application platform issues an instruction to terminal equipment, the equipment middleware receives the instruction by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment;
when the terminal equipment uploads data to the application platform, the equipment middleware receives the data by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform;
further comprises:
creating and saving a device model in the device middleware;
selecting a device type in an application platform, acquiring a corresponding device model from the device middleware, and configuring device basic information according to the device model;
generating a corresponding terminal equipment shadow in the equipment middleware according to the equipment basic information;
adding equipment configuration information in an application platform, submitting the equipment configuration information to the equipment middleware, and configuring the shadow of the terminal equipment;
when the application platform issues an instruction to the terminal equipment, the equipment middleware receives the instruction by using a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment, including:
receiving data or instructions issued by an application platform through the shadow of the terminal equipment;
judging whether the corresponding terminal equipment is in an online state or not;
if the terminal equipment is in the on-line state, analyzing the data or the instruction into a format adapted to the terminal equipment, and issuing the analyzed data or instruction to the terminal equipment;
if the terminal equipment is judged not to be in the on-line state, storing the data or the instruction, and continuously judging whether the terminal equipment is in the on-line state;
after the data or the instruction is successfully issued, carrying out state synchronization on the shadow of the terminal equipment according to the state of the terminal equipment;
when the application platform has a plurality of corresponding terminal devices, the device middleware firstly determines the terminal device which is finally received according to the data or the instruction received by the shadow of the terminal device, and then judges whether the terminal device is in an on-line state or not; when only one corresponding terminal device exists in the application platform, directly judging whether the corresponding terminal device is in an on-line state or not;
further comprises:
when the equipment middleware receives a terminal equipment connection request, the equipment middleware matches the equipment model with the terminal equipment;
if the matching is successful, allowing the terminal equipment to access the equipment middleware;
if the matching fails, acquiring the attribute, event and service of the terminal equipment, creating an equipment model according to the attribute, event and service of the terminal equipment, matching the created equipment model with the terminal equipment, and allowing the terminal equipment to be accessed;
the device middleware obtains the attribute, service and event of the connected terminal device, and generates a corresponding shadow of the terminal device according to the attribute, service and event of the terminal device, and then comprises the following steps:
the equipment middleware uploads the attribute, the event and the service of the shadow of the terminal equipment to an application platform, and the application platform sets corresponding instructions for the terminal equipment according to the attribute, the event and the service of the shadow of the terminal equipment;
the equipment middleware carries out equipment management, equipment access and operation and maintenance monitoring on the accessed terminal equipment, wherein the equipment management specifically comprises type management, simulation management, equipment grouping and shadow equipment; the equipment access comprises connection management, protocol analysis, data management and instruction management;
the device middleware also provides rules engines, open APIs, and console functions.
2. The method for implementing the middleware for connecting the internet of things device according to claim 1, wherein when the terminal device uploads the data to the application platform, the device middleware receives the data by using a terminal device shadow corresponding to the terminal device, parses and encapsulates a format of the data, and sends the encapsulated data to the application platform, including:
acquiring data of corresponding terminal equipment through the shadow of the terminal equipment, and analyzing the data into a format adapted to an application platform;
if the data analysis is successful, storing and reporting the analyzed data to an application platform;
if the data analysis fails, a log of the analysis failure is stored in the shadow of the terminal equipment.
3. The method for implementing the device connection middleware of the internet of things according to claim 1, wherein the terminal device connects with the device middleware through a standard protocol or a proprietary protocol, and includes:
the equipment middleware analyzes the protocol of the terminal equipment to enable the protocol of the terminal equipment to be adapted to an application platform.
4. The utility model provides an thing networking device connects middleware system which characterized in that includes: terminal equipment, equipment middleware and an application platform;
the terminal equipment is used for connecting with the equipment middleware through a standard protocol or a private protocol;
the equipment middleware is used for acquiring the attribute, service and event of the connected terminal equipment and generating a corresponding terminal equipment shadow according to the attribute, service and event of the terminal equipment; when an application platform issues an instruction to terminal equipment, the equipment middleware receives the instruction by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes the instruction into a format adapted to the terminal equipment, and then issues the analyzed instruction to the terminal equipment; when the terminal equipment uploads data to the application platform, the equipment middleware receives the data by utilizing a terminal equipment shadow corresponding to the terminal equipment, analyzes and encapsulates the format of the data, and sends the encapsulated data to the application platform;
the equipment middleware is also used for creating and storing an equipment model;
the application platform is used for selecting equipment types, acquiring corresponding equipment models from the equipment middleware and configuring equipment basic information according to the equipment models; generating a corresponding terminal equipment shadow in the equipment middleware according to the equipment basic information; adding equipment configuration information, submitting the equipment configuration information to the equipment middleware, and configuring the shadow of the terminal equipment;
the equipment middleware is further used for matching the equipment model with the terminal equipment when the equipment middleware receives a terminal equipment connection request; if the matching is successful, allowing the terminal equipment to access the equipment middleware; if the matching fails, acquiring the attribute, event and service of the terminal equipment, creating an equipment model according to the attribute, event and service of the terminal equipment, matching the created equipment model with the terminal equipment, and allowing the terminal equipment to be accessed;
the equipment middleware is also used for receiving data or instructions issued by an application platform through the shadow of the terminal equipment; judging whether the corresponding terminal equipment is in an online state or not; if the terminal equipment is in the on-line state, analyzing the data or the instruction into a format adapted to the terminal equipment, and issuing the analyzed data or instruction to the terminal equipment; if the terminal equipment is judged not to be in the on-line state, storing the data or the instruction, and continuously judging whether the terminal equipment is in the on-line state; after the data or the instruction is successfully issued, carrying out state synchronization on the shadow of the terminal equipment according to the state of the terminal equipment;
the equipment middleware is also used for uploading the attribute, the event and the service of the shadow of the terminal equipment to an application platform, and setting corresponding instructions for the terminal equipment by the application platform according to the attribute, the event and the service of the shadow of the terminal equipment;
the equipment middleware is further used for determining the terminal equipment which is finally received according to the data or the instruction received by the shadow of the terminal equipment when a plurality of corresponding terminal equipment exist in the application platform, and judging whether the terminal equipment is in an online state or not; when only one corresponding terminal device exists in the application platform, directly judging whether the corresponding terminal device is in an on-line state or not;
the equipment middleware is also used for carrying out equipment management, equipment access and operation and maintenance monitoring on the accessed terminal equipment, wherein the equipment management specifically comprises type management, analog management, equipment grouping and shadow equipment; the equipment access comprises connection management, protocol analysis, data management and instruction management;
the device middleware is also used to provide rules engines, open APIs, and console functions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010886798.XA CN112039983B (en) | 2020-08-28 | 2020-08-28 | Method and system for realizing connection middleware of Internet of things equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010886798.XA CN112039983B (en) | 2020-08-28 | 2020-08-28 | Method and system for realizing connection middleware of Internet of things equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112039983A CN112039983A (en) | 2020-12-04 |
| CN112039983B true CN112039983B (en) | 2023-12-22 |
Family
ID=73586101
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010886798.XA Active CN112039983B (en) | 2020-08-28 | 2020-08-28 | Method and system for realizing connection middleware of Internet of things equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112039983B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113328891A (en) * | 2021-06-08 | 2021-08-31 | 西人马(深圳)科技有限责任公司 | Data communication method, device, equipment and storage medium |
| CN113542390B (en) * | 2021-07-12 | 2022-07-05 | 山东大学 | Internet of things equipment management method and system adopting memory data model |
| CN114422558A (en) * | 2021-12-29 | 2022-04-29 | 国网天津市电力公司 | Data message conversion self-description protocol MQTT method based on container edge proxy |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111201764B (en) * | 2017-10-19 | 2022-12-16 | Sk电信有限公司 | Method and server device for providing platform service of Internet of things |
| CN107911492A (en) * | 2017-12-27 | 2018-04-13 | 浙江力石科技股份有限公司 | The method and device that equipment accesses in platform of internet of things |
| US10805104B2 (en) * | 2018-06-26 | 2020-10-13 | Verizon Patent And Licensing Inc. | Virtual network endpoints for internet of things (IOT) devices |
| CN109104461A (en) * | 2018-07-06 | 2018-12-28 | 安徽电科恒钛智能科技有限公司 | A kind of data processing system and its method based on Internet of things middleware |
| CN109587228B (en) * | 2018-11-23 | 2021-08-10 | 山东浪潮科学研究院有限公司 | Equipment access method of public protocol Internet of things platform system |
| CN110493270B (en) * | 2019-09-25 | 2020-10-09 | 北京金茂绿建科技有限公司 | Internet of things equipment access fusion control method and device |
| CN111585958B (en) * | 2020-04-01 | 2021-10-29 | 西安电子科技大学 | Self-adaptive access method and system for heterogeneous equipment of Internet of things platform |
-
2020
- 2020-08-28 CN CN202010886798.XA patent/CN112039983B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112039983A (en) | 2020-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112039983B (en) | Method and system for realizing connection middleware of Internet of things equipment | |
| CN110430219B (en) | Method and system for self-adapting of multi-protocol Internet of things equipment | |
| CN109889551A (en) | A kind of method of the Internet of Things cloud platform of Intelligent hardware access | |
| CN110933146B (en) | Data conversion method and device and server | |
| Milenkovic | Internet of Things: Concepts and System Design | |
| CN109270850A (en) | A kind of intelligent household management system and method based on Internet of Things | |
| CN106790222B (en) | MODBUS/full-interconnection manufacturing network information service adapter and implementation method thereof | |
| CN110995859A (en) | Intelligent transformer substation supporting platform system based on ubiquitous Internet of things | |
| CN111611054B (en) | Application deployment method and device | |
| CN114567620B (en) | Digital model and physical equipment matching system and method based on MQTT protocol | |
| CN105187486A (en) | Semi-offline conference activity signing-in method and system | |
| CN112637283B (en) | Chat robot-based Internet of things intelligent home management system and control method | |
| CN107179977B (en) | Database Full-automatic monitoring system based on mpm models | |
| CN112688997B (en) | RPA robot-based universal data acquisition and management method and system | |
| CN108303944A (en) | A kind of industrial 4.0 networked systems of injection molding machine and monitoring method | |
| CN107172613B (en) | A kind of remote maintenance system and method for car wireless terminal | |
| CN106899452B (en) | Message circulation processing Internet of things terminal debugging method based on XM2M protocol | |
| WO2021031386A1 (en) | Positioning method and device, server, storage medium and terminal | |
| KR20100025941A (en) | Wireless sensor node for production management system and sensor server and production management system and method for production management | |
| CN114915521A (en) | Intelligent home gateway and data processing method | |
| CN106292584A (en) | A kind of flexible manufacturing system based on modular control unit | |
| CN103944779B (en) | A kind of WAP service features monitoring method and system | |
| CN113765719B (en) | Instant implementation method for unified management, monitoring and maintenance of Internet of things access | |
| CN116032911A (en) | Internet of things large-screen real-time monitoring system based on websocket | |
| CN116471294A (en) | Internet of things access system, method and medium based on object model and rule engine |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |