CN112202874B - Extensible Internet of things bottom equipment adapter and construction method - Google Patents
Extensible Internet of things bottom equipment adapter and construction method Download PDFInfo
- Publication number
- CN112202874B CN112202874B CN202011041790.XA CN202011041790A CN112202874B CN 112202874 B CN112202874 B CN 112202874B CN 202011041790 A CN202011041790 A CN 202011041790A CN 112202874 B CN112202874 B CN 112202874B
- Authority
- CN
- China
- Prior art keywords
- internet
- things
- docking
- management system
- service
- 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
Images
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/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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
- H04L41/5083—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to web hosting
-
- 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/10—Protocols in which an application is distributed across nodes in the network
-
- 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/562—Brokering proxy services
Abstract
The invention discloses an extensible Internet of things bottom equipment adapter and a construction method thereof. The adapter includes: the system comprises a communication middleware, a device docking library module and a host program; the communication middleware is used for providing an API (application programming interface) based on a publish-subscribe mode for the upper Internet of things management system and the bottom layer equipment according to a plurality of predefined topics; the equipment docking library module comprises a plurality of service modules which are divided according to service types, and each service module comprises a plurality of manufacturer docking libraries which are divided according to manufacturer identifications; and the host program is used for loading the device docking library module and carrying out configuration management and operation and maintenance on the device docking library module. The invention has expandability and universality, can provide service across service scenes and platforms, transversely expands and supports various types of bottom equipment of multiple manufacturers, and longitudinally adapts to various service functions of an upper Internet of things management system, thereby being suitable for different application scenes.
Description
Technical Field
The invention belongs to the technical field of Internet of things, and particularly relates to an extensible Internet of things bottom layer equipment adapter and a construction method thereof.
Background
In recent years, technologies such as the internet of things, artificial intelligence, 5G, block chains and cloud are developed vigorously, and the internet of things plays a role in developing earth and lifting in the fields of smart homes, intelligent transportation, intelligent communities, intelligent medical treatment, intelligent security, intelligent buildings and the like.
For a mature solution of the internet of things, namely an internet of things management system or platform in a local area network, the system comprises the following parts: client, server, adapter, bottom equipment. The client is responsible for presenting data and interacting with a client, and can be a PC application, a browser or a mobile phone and the like; the server is responsible for processing various data traffic, storing data, distributing data and performing centralized scheduling; the bottom layer equipment is responsible for acquiring data, and the data is acquired through hardware equipment such as a sensor and a monitor and then distributed through Internet of things communication protocols such as LoRa, ZigBee and Wi-Fi; the adapter is responsible for converting data collected by the equipment into data approved by the server and sending the data to the server, and is also responsible for translating an instruction sent to the equipment by the server into a control instruction which can be understood by the equipment and sending the control instruction to the equipment.
In general, in different application scenarios or solutions provided by different software developers, different adapters need to be specially developed for devices of different manufacturers to adapt to a plurality of manufacturer devices. However, communication protocols used by different manufacturers and API calling modes provided by different manufacturers are different, which causes the function of the adapter to be complicated, the version to be confused, the universality to be poor and the adapter to be difficult to reuse, and the situation undoubtedly increases extra labor cost and time cost for internet of things solution manufacturers.
Disclosure of Invention
Aiming at least one defect or improvement requirement in the prior art, the invention provides an extensible Internet of things bottom layer equipment adapter and a construction method thereof, which have expandability and universality, can provide service across service scenes and platforms, transversely expand and support bottom layer equipment of multiple types and multiple manufacturers, and longitudinally adapt to various service functions of an upper layer Internet of things management system, thereby being suitable for different application scenes.
To achieve the above object, according to a first aspect of the present invention, there is provided an extensible internet of things underlying device adapter, including: the system comprises a communication middleware, a device docking library module and a host program;
the communication middleware is used for providing an API (application programming interface) based on a publish-subscribe mode for the upper-layer Internet of things management system and the bottom-layer equipment according to a plurality of predefined topics, and the topics are predefined according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment;
the equipment docking library module comprises a plurality of service modules divided according to the service types, each service module comprises a plurality of manufacturer docking libraries divided according to manufacturer identifications, and the manufacturer docking libraries are used for providing data interaction services with the bottom-layer equipment;
and the host program is used for loading the device docking library module and carrying out configuration management on the device docking library module.
Preferably, the API interface is configured to obtain a subscription theme of the upper-layer internet of things management system, and push a state of the bottom-layer device related to the subscription theme of the upper-layer internet of things management system to the upper-layer internet of things management system; the API is used for obtaining the subscription theme of the bottom layer equipment and sending the control instruction related to the subscription theme of the bottom layer equipment to the bottom layer equipment.
Preferably, the internet of things underlying device adapter is packaged into an independent service.
Preferably, all the vendors in one of the service modules provide the same service interface to the library.
Preferably, each of the vendor docking libraries is a separate module.
Preferably, the configuration management specifically includes: defining a valid status of all of the vendor docking libraries in the device docking library module by defining a configuration rule file.
According to a second aspect of the present invention, there is provided a method for constructing an extensible internet of things underlying device adapter, including:
acquiring the service type of an upper Internet of things management system and the manufacturer identification of a bottom device;
a plurality of themes are predefined according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment;
selecting a communication middleware of the Internet of things bottom layer equipment adapter, wherein the communication middleware is used for providing an API (application programming interface) based on a publishing and subscribing mode for an upper Internet of things management system and bottom layer equipment according to the theme;
constructing a manufacturer docking library for each bottom layer device according to manufacturer identification, dividing the manufacturer docking libraries with the same service type into a service module, and constructing a plurality of service modules into a service docking library module;
and developing a host program, wherein the host program is used for loading the device docking library module and carrying out configuration management on the device docking library module.
Preferably, if the bottom layer device is modified or added, the corresponding vendor docking library is modified or added in the service docking library module.
Preferably, if the upper-layer internet of things management system is modified or added, the subscription theme of the upper-layer internet of things management system is modified or added.
Preferably, the API interface is configured to obtain a subscription theme of the upper-layer internet of things management system, and push a state of the bottom-layer device related to the subscription theme of the upper-layer internet of things management system to the upper-layer internet of things management system; the API is used for obtaining the subscription theme of the bottom layer equipment and sending the control instruction related to the subscription theme of the bottom layer equipment to the bottom layer equipment.
In general, compared with the prior art, the invention has the following beneficial effects: by adopting the architecture of the communication middleware, the device docking library module and the host program, the upper-layer Internet of things management system and the bottom-layer device are decoupled from each other and do not depend on each other, so that the adapter has expandability and universality, can provide service across service scenes and platforms, transversely expands the adapter to support the bottom-layer devices of various types of multiple manufacturers, longitudinally adapts to various service functions of the upper-layer Internet of things management system, and is suitable for different application scenes.
Drawings
FIG. 1 is a schematic diagram of an application of an adapter of an embodiment of the present invention;
FIG. 2 is a schematic diagram of the components of an adapter of an embodiment of the present invention;
FIG. 3 is a communication schematic of an adapter of an embodiment of the present invention;
FIG. 4 is a diagram illustrating the interaction between a vendor docking library and an underlying device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
As shown in fig. 1, an extensible internet of things underlying device adapter according to an embodiment of the present invention is connected to an upper internet of things management system in various application scenarios, and is connected to underlying devices of various manufacturers.
As shown in fig. 2, an extensible internet of things underlying device adapter according to an embodiment of the present invention includes: communication middleware, a device docking library module and a host program.
And the communication middleware is used for providing an API (application programming interface) based on a publish-subscribe mode for the upper-layer Internet of things management system and the bottom-layer equipment according to a plurality of predefined topics, and the topics are predefined according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment. In this way, the adapter exposes the API interface upward, and the upstream solution management system can interface with the API to control device/get device status, etc. The communication middleware may employ Message Queue Telemetry Transport (MQTT) middleware.
The equipment docking library module comprises a plurality of service modules divided according to service types, each service module comprises a plurality of manufacturer docking libraries divided according to manufacturer identifications, and the manufacturer docking libraries are used for providing data interaction services with the bottom-layer equipment. Thus, the adapter integrates devices of different manufacturers according to the service, encapsulates the library of the bottom docking manufacturer, and simultaneously interfaces the API in the library to receive the command and send the device state and the like.
And the host program is used for loading the device docking library module and carrying out configuration management on the device docking library module.
The Internet of things underlying equipment adapter is packaged into an independent service.
Therefore, the adapter of the embodiment of the invention has the advantages that the management system and the manufacturer equipment of the solution can complete service intercommunication, the management system and the manufacturer equipment are mutually decoupled and do not depend on each other, and the adapter has universality and universality.
Alternative implementations of each module are described in detail below.
(1) Communication middleware
As shown in fig. 3, the communication middleware is used to provide an API interface for the upper-layer internet of things management system and the underlying device, and the API interface has two roles: (a) the system comprises a subscription theme for acquiring the upper-layer Internet of things management system, and pushing the state of the bottom-layer equipment related to the subscription theme of the upper-layer Internet of things management system to the upper-layer Internet of things management system; (b) the system is used for acquiring the subscription theme of the bottom layer device and sending the control instruction related to the subscription theme of the bottom layer device to the bottom layer device.
The theme is an abstraction of a predefined string of characters, a function point that can be recognized by both the upstream management system and the downstream docking library. And one end subscribes to the theme, and the other end publishes the theme, so that upstream and downstream communication is realized. Taking the door opening of the access control system as an example, the theme of door opening is defined in advance as follows: and if the theme is required to be opened, the downstream system issues the theme, and once the theme is issued, the downstream system receives an instruction to execute an opening action.
The communication middleware has the advantages of light weight, simplicity, openness, easiness in implementation and the like, is used for connecting an upstream management system and downstream equipment, and has the following specific connection mode:
s1, firstly, defining a theme according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment, wherein the theme is designed to be universal, and the theme is kept the same for different manufacturers of the same service. The subject matter is disclosed both above and below, which can be used indifferently.
S2, if the upstream needs to acquire the equipment state, the upstream needs to subscribe to the related topic of the equipment state, and when the state of the downstream equipment is changed, data can be immediately pushed to all subscribers who subscribe to the related topic.
And S3, similarly, the downstream can subscribe the theme, and when the upstream issues a control instruction, all the downstream equipment subscribed with the related theme can receive the instruction and further execute the operation.
(2) Device docking library module
As shown in fig. 4, the vendor docking library is used to provide a service for data interaction with the underlying device, specifically, an interface for querying and modifying device attributes, and may actively send device attribute information upward or passively receive an upstream control instruction.
Specifically, data interaction between the vendor docking library and the underlying device is illustrated.
Suppose that: subscribing to a topic for the library:
/sys/{productKey}/{deviceID}/thing/service/property/set，
upstream publishing the subject:
/sys/{productKey}/{deviceID}/thing/service/property/set，
the two methods are completely the same, except that one end of the publication needs to carry a message body (payload), which is a further detailed description of the topic, and the general message body is a cross-platform standard common format (json, xml, etc.), as exemplified by json:
payload format
{
"id":3536123,
"version":"1.0",
"params":{
"attribute key1": attribute value1",
attribute key2 'attribute value 2'
},
"method":"property.set"
}
After receiving the message body, the library analyzes the message body and finds that the values of the device attributes (Key1 and Key2) are set to new values (value1 and value2), and then calls an interface provided by a device manufacturer to modify the device.
At present, equipment of each manufacturer needs to develop a docking library independently, and the development modes are various, such as SDK, Http, MQ and the like, and are determined by the equipment of the manufacturer.
The equipment docking library module comprises a plurality of service modules which are divided according to the service types, and each service module comprises a plurality of vendor docking libraries which are divided according to vendor identifications. All vendors in a business module provide the same business interface to the library. Such as: the charging pile of the manufacturer A is developed into a docking warehouse, and the charging pile equipment of the manufacturer B is developed into another docking warehouse. But the two belong to the same service, the same service interface should be realized, and the service interface includes all the due functions of the charging pile, such as starting charging, obtaining charging progress, obtaining charging duration, pushing charging amount, and the like, interacts with the MQTT middleware, and pushes or subscribes the theme related to MQTT so as to interact with the upstream.
Each manufacturer docking library is an independent operation module. The manufacturer docking base is in a modular design, namely, one manufacturer docking base is an independent module which is regarded as a plug-in unit and can be plugged and unplugged for the whole adapter.
(3) Host program
The host program is mainly used for loading the device docking library module and carrying out configuration management on the device docking library module. The corresponding vendor docking library may be loaded into the host program in advance as required. However, not all vendor docking libraries are used in every functional scenario, and therefore, which vendor docking libraries are enabled in different application functional scenarios are modified by configuration. The valid status of all of the vendor docking libraries in the device docking library module may be defined by defining a configuration rule file. For example, for the wisdom campus solution of a, only three devices of one manufacturer are needed, and then 3 docking libraries need to be configured; however, for the smart community solution of B, 10 devices from four vendors are required, and 10 docking libraries are required. If the more scenes and solutions applied by the adapter, the more compatible manufacturers and devices, the more powerful the adapter is, the more adaptable functions and devices are, and the expandability is achieved.
The host program may also provide operational management of the device docking library module, such as starting and shutting down vendor docking libraries. The host program may also provide error recovery for the device docking library module, such as automatically restarting a vendor docking library when an error occurs with the vendor docking library.
The host program can use a modular design, that is, one manufacturer docking library is a separate module, and the module is regarded as a plug-in unit and can be plugged and unplugged for the whole adapter.
The construction method of the extensible Internet of things bottom equipment adapter provided by the embodiment of the invention comprises the following steps:
and S1, collecting the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment. The collected content is abstracted into a set of self-defined standard codes (ID) which comprise service codes and manufacturer codes and are generally used for upper layer system and bottom layer equipment. The service types are functions such as charging pile, lighting, entrance guard and the like, and are classified according to manufacturers and service functions.
And S2, pre-defining a plurality of themes according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment. That is, the service in S1 is abstracted to the theme of the communication middleware, and the data format may be json or protobuffer. The design of the subject matter calls for general readability.
And S3, selecting a communication middleware of the Internet of things bottom layer equipment adapter, wherein the communication middleware is used for providing an API (application programming interface) based on a publish-subscribe mode for the upper Internet of things management system and the bottom layer equipment according to the theme. The model selection is carried out aiming at MQTT middleware, and at present, a plurality of open-source communication middleware such as RabbitteMQ, ActiveMQ, Kafka and the like are available in the market, and the model selection is carried out according to requirements and application scenes.
S4, constructing a manufacturer docking library for each bottom layer device according to manufacturer identification, dividing the manufacturer docking libraries with the same service type into one service module, and constructing a plurality of service modules into a service docking library module.
And S5, developing a host program, wherein the host program is used for loading the device docking library module and carrying out configuration management on the device docking library module. The host program uses a modular design, and each docking library is regarded as a plug-in. The decision of which vendor docking libraries to use is made by configuration.
And finally, debugging the adapter and testing the upstream and downstream communication processes.
Preferably, if the bottom layer device needs to be modified or added, the corresponding vendor docking library is modified or added in the service docking library module.
Preferably, if the upper-layer internet of things management system needs to be modified or added, the subscription theme of the upper-layer internet of things management system is modified or added.
Preferably, the API interface is configured to obtain a subscription theme of the upper-layer internet of things management system, and push a state of the bottom-layer device related to the subscription theme of the upper-layer internet of things management system to the upper-layer internet of things management system; the API is used for obtaining the subscription theme of the bottom layer device and sending the control instruction related to the subscription theme of the bottom layer device to the bottom layer device.
The implementation principle and technical effect of the construction method are similar to those of the adapter, and are not described herein again.
In the following, embodiments in several application scenarios are briefly described.
Application scenario 1: the management system of the current one set of wisdom community in A community contains and fills electric pile, video monitoring, and the key is reported to the police, and functions such as entrance guard need the data acquisition's of bottom equipment function. Then, the embodiment of the invention needs to know which manufacturers exist in the existing community equipment, and if the docking library of the manufacturers exists in the adapter, the manufacturers do not need to develop, and the docking library of the manufacturers can be directly configured. If the docking library of the manufacturer does not exist, the development is needed. After the docking library is configured, the intelligent community management system needs to subscribe/publish the theme of the adapter to complete the business function.
Application scenario 2: a community needs to completely change the charging pile equipment into equipment of another manufacturer, and the manufacturer library supported by the adapter is checked to know that the adapter contains the docking library of the equipment manufacturer, so that the manufacturer docking library can be directly changed at the adapter end. Need not other places and change, practice thrift development cost greatly.
Application scenario 3: a community needs to add some earth magnetism equipment newly to guide the parking, then only need the adapter to develop the butt joint storehouse of corresponding firm alone, need not whole adapter change, and can not influence other functions. The extensible and easy-to-maintain characteristic of the adapter is embodied.
Application scenario 4: the B community feels that the set of adaptation architecture of the A community is very useful, and the B community also wants to introduce a set. Because the functions of the adapter and the system are the same, the adapter end does not need to be developed, and only an upstream system needs to subscribe/publish the theme of the adapter. The universal and universal characteristics of the adapter are embodied.
Application scenario 5: c community has gone online one set of wisdom building system, only needs the entrance guard function, and the producer also is listed in the adapter support, so only need the adapter do well the configuration can, need not development. The adapter customization feature is embodied.
In conclusion, the invention aims to construct the Internet of things bottom layer equipment adapter with high universality, high expandability and high customization, the adapter can be released and operated as an independent product, and pain points such as repeatability of equipment acquisition functions, difficulty in maintenance and difficulty in expansion among different Internet of things solutions can be effectively solved. As an independent product, the API interface can be exposed to a third party from the outside, and the docking library of manufacturers and equipment can be expanded infinitely from the inside to the outside. Along with the lapse of time, the accumulation of function is more and more, can realize the adaptation to most thing networking equipment on the market.
It must be noted that in any of the above embodiments, the methods are not necessarily executed in order of sequence number, and as long as it cannot be assumed from the execution logic that they are necessarily executed in a certain order, it means that they can be executed in any other possible order.
It will be understood by those skilled in the art that the foregoing is only a preferred embodiment of the present invention, and is not intended to limit the invention, and that any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. An extensible internet of things underlying device adapter, comprising: the system comprises a communication middleware, a device docking library module and a host program;
the communication middleware is used for providing an API (application programming interface) based on a publish-subscribe mode for the upper-layer Internet of things management system and the bottom-layer equipment according to a plurality of predefined topics, and the topics are predefined according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment;
the equipment docking database module comprises a plurality of service modules divided according to the service types, each service module comprises a plurality of manufacturer docking databases divided according to manufacturer identifications, and the manufacturer docking databases provide services for data interaction with the bottom-layer equipment;
and the host program is used for loading the device docking library module and carrying out configuration management on the device docking library module.
2. The extensible internet of things underlying device adapter as recited in claim 1, wherein the API interface is configured to obtain a subscription theme of the upper internet of things management system and push a status of the underlying device related to the subscription theme of the upper internet of things management system to the upper internet of things management system; the API is used for obtaining the subscription theme of the bottom layer equipment and sending the control instruction related to the subscription theme of the bottom layer equipment to the bottom layer equipment.
3. The scalable internet of things infrastructure device adapter of claim 1, wherein the internet of things infrastructure device adapter is packaged as a stand-alone service.
4. The extensible internet of things infrastructure device adapter of claim 1, wherein all of the vendors in one of the business modules provide the same business interface to a library.
5. The extensible internet of things infrastructure device adapter of claim 1, wherein each of the vendor docking libraries is a standalone module.
6. The extensible internet of things underlying device adapter of claim 1, wherein the configuration management is specifically: defining a valid state of the vendor docking library in the device docking library module by defining a configuration rule file.
7. A construction method of an extensible Internet of things bottom layer equipment adapter is characterized by comprising the following steps:
acquiring the service type of an upper Internet of things management system and the manufacturer identification of a bottom device;
a plurality of themes are predefined according to the service type of the upper-layer Internet of things management system and the manufacturer identification of the bottom-layer equipment;
selecting a communication middleware of the Internet of things bottom layer equipment adapter, wherein the communication middleware is used for providing an API (application programming interface) based on a publishing and subscribing mode for an upper Internet of things management system and bottom layer equipment according to the theme;
constructing manufacturer docking libraries for each bottom layer device according to manufacturer identification, dividing the manufacturer docking libraries with the same service type into a service module, and constructing a plurality of service modules into device docking library modules;
and developing a host program, wherein the host program is used for loading the device docking library module and carrying out configuration management on the device docking library module.
8. The method for constructing the extensible internet of things underlying device adapter as recited in claim 7, wherein if the underlying device is modified or added, the corresponding vendor docking library is modified or added in the device docking library module.
9. The method for building the extensible IOT (Internet of things) underlying device adapter as recited in claim 7, wherein if the upper IOT management system is modified or added, a subscription theme of the upper IOT management system is modified or added.
10. The method for building the extensible internet of things bottom-layer device adapter as recited in claim 7, wherein the API interface is configured to obtain a subscription theme of the upper-layer internet of things management system, and push a status of the bottom-layer device related to the subscription theme of the upper-layer internet of things management system to the upper-layer internet of things management system; the API is used for obtaining the subscription theme of the bottom layer equipment and sending the control instruction related to the subscription theme of the bottom layer equipment to the bottom layer equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011041790.XA CN112202874B (en) | 2020-09-28 | 2020-09-28 | Extensible Internet of things bottom equipment adapter and construction method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011041790.XA CN112202874B (en) | 2020-09-28 | 2020-09-28 | Extensible Internet of things bottom equipment adapter and construction method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112202874A CN112202874A (en) | 2021-01-08 |
| CN112202874B true CN112202874B (en) | 2022-08-05 |
Family
ID=74006854
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011041790.XA Active CN112202874B (en) | 2020-09-28 | 2020-09-28 | Extensible Internet of things bottom equipment adapter and construction method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112202874B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113608781A (en) * | 2021-08-02 | 2021-11-05 | 上海同星智能科技有限公司 | Multi-adapter compatible library file module, calling method, calling system and device |
| CN115150226A (en) * | 2022-06-20 | 2022-10-04 | 武汉虹信技术服务有限责任公司 | Intelligent gateway adaptation system based on object model and operation method thereof |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2461545A1 (en) * | 2010-12-06 | 2012-06-06 | Sap Ag | In-vehicle application platform for vehicle-to-business communication |
| CN102902536A (en) * | 2012-09-14 | 2013-01-30 | 杭州泛和科技有限公司 | Computer system of Internet of things |
| CN105653293A (en) * | 2016-01-31 | 2016-06-08 | 吴林 | Non-standard Internet-of-Things operating system |
| CN106685815A (en) * | 2017-01-04 | 2017-05-17 | 上海建坤信息技术有限责任公司 | Multi - protocol hardware acquisition gateway system |
| CN106899638A (en) * | 2015-12-21 | 2017-06-27 | 中国科学院信息工程研究所 | A kind of fusions networking relationships system for solving Heterogeneous data and method |
| CN110971614A (en) * | 2019-12-17 | 2020-04-07 | 软通动力信息技术（集团）有限公司 | Internet of things adaptation method and system, computer equipment and storage medium |
| CN111585958A (en) * | 2020-04-01 | 2020-08-25 | 西安电子科技大学 | Self-adaptive access method and system for heterogeneous equipment of Internet of things platform |
-
2020
- 2020-09-28 CN CN202011041790.XA patent/CN112202874B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2461545A1 (en) * | 2010-12-06 | 2012-06-06 | Sap Ag | In-vehicle application platform for vehicle-to-business communication |
| CN102902536A (en) * | 2012-09-14 | 2013-01-30 | 杭州泛和科技有限公司 | Computer system of Internet of things |
| CN106899638A (en) * | 2015-12-21 | 2017-06-27 | 中国科学院信息工程研究所 | A kind of fusions networking relationships system for solving Heterogeneous data and method |
| CN105653293A (en) * | 2016-01-31 | 2016-06-08 | 吴林 | Non-standard Internet-of-Things operating system |
| CN106685815A (en) * | 2017-01-04 | 2017-05-17 | 上海建坤信息技术有限责任公司 | Multi - protocol hardware acquisition gateway system |
| CN110971614A (en) * | 2019-12-17 | 2020-04-07 | 软通动力信息技术（集团）有限公司 | Internet of things adaptation method and system, computer equipment and storage medium |
| CN111585958A (en) * | 2020-04-01 | 2020-08-25 | 西安电子科技大学 | Self-adaptive access method and system for heterogeneous equipment of Internet of things platform |
Non-Patent Citations (1)
| Title |
|---|
| 基于开放标准的NB-IoT平台体系设计;欧阳恩山;《福建冶金》;20171215(第06期);正文第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112202874A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Dias et al. | Designing and constructing internet-of-Things systems: An overview of the ecosystem | |
| US7720953B2 (en) | System and method of data source detection | |
| CN101888320B (en) | Enhanced network adapter framework | |
| CN112202874B (en) | Extensible Internet of things bottom equipment adapter and construction method | |
| EP2003854B1 (en) | Server for communicating with multi-mode devices using multi-mode applications | |
| CN112988485B (en) | Simulation test method and device for electric power Internet of things equipment | |
| US8732652B2 (en) | System and method for creating multi-mode applications | |
| WO2007117705A9 (en) | Software enabled video and sensor interoperability system and method | |
| US10990449B2 (en) | Managing application relationships in machine-to-machine systems | |
| CN103218220A (en) | Dynamic pluggable component based-Internet of things middleware system | |
| Wu et al. | OneM2M-based IoT protocol integration | |
| Sciullo et al. | WoT Store: Managing resources and applications on the web of things | |
| CN115080101B (en) | Application management method, application subscription method and related equipment | |
| De Troyer et al. | Building IoT systems using distributed first-class reactive programming | |
| Vogel et al. | An open architecture approach: Towards common design principles for an iot architecture | |
| Krainyk et al. | Internet-of-Things Device Set Configuration for Connection to Wireless Local Area Network. | |
| Warriach et al. | An interplatform service-oriented middleware for the smart home | |
| US20200389528A1 (en) | Service-oriented internet of things platform and control method therefor | |
| CN114979144B (en) | Cloud edge communication method and device and electronic equipment | |
| CN113347609B (en) | Wireless intelligent control platform | |
| Plebani et al. | MicroMAIS: executing and orchestrating Web services on constrained mobile devices | |
| CN110198225A (en) | A kind of management method and management server of more clusters | |
| CN111026413B (en) | Requirement-oriented complex system 'pull' mode deployment system and method thereof | |
| Taherkordi et al. | Restful service development for resource-constrained environments | |
| Marin et al. | Sensor bean: a component platform for sensor-based services |
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 |