CN116340413A - Internet of things edge data acquisition and storage method - Google Patents
Internet of things edge data acquisition and storage method Download PDFInfo
- Publication number
- CN116340413A CN116340413A CN202310314248.4A CN202310314248A CN116340413A CN 116340413 A CN116340413 A CN 116340413A CN 202310314248 A CN202310314248 A CN 202310314248A CN 116340413 A CN116340413 A CN 116340413A
- Authority
- CN
- China
- Prior art keywords
- equipment
- internet
- data
- rule
- things
- 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.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for collecting and storing data of an edge end of an Internet of things, which comprises the following steps: s1, constructing an Internet of things management platform and setting a plurality of equipment access modes; s2, based on functions and definitions of equipment, an object model of the equipment is built on the Internet of things management platform, an access mode matched with the equipment is selected, the equipment is dynamically modeled by adopting the object model, the equipment is accessed into the Internet of things management platform, and the equipment is subjected to full life cycle on-line management; s3, constructing a visual rule engine, acquiring equipment information, and performing data conversion on the equipment information based on the visual rule engine to obtain equipment data; s4, storing the converted equipment data into different application databases in a classified mode.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method for acquiring and storing data at an edge end of an Internet of things.
Background
With the continuous development of internet of things, more and more devices and sensors are deployed in various scenes, generating a large amount of data. These data need to be collected, stored and processed to support various application scenarios such as smart home, smart city, smart manufacturing, etc. However, due to the huge number of devices, wide distribution and limited resources of the internet of things, the traditional centralized data acquisition and storage mode cannot meet the requirements. Therefore, the edge computing is widely applied to the field of the Internet of things as an emerging computing mode. The edge calculation places the calculation and storage resources at a position closer to the data source, so that the efficiency of data acquisition and processing can be improved, and the delay and bandwidth consumption of data transmission can be reduced. Therefore, the research on the data acquisition and storage method of the Internet of things edge has important significance for improving the performance and reliability of the Internet of things system.
At present, technologies of an internet of things edge data acquisition and storage method mainly comprise distributed storage, data compression, de-duplication, data caching and the like, and the technologies can be combined with each other to meet requirements in different scenes. However, although the method for collecting and storing the data at the edge of the internet of things has already made a certain progress, some disadvantages still exist:
1) Safety problem: edge devices are often in an untrusted environment and are vulnerable to attack and threat, so some security mechanisms and techniques need to be employed to protect the security and privacy of data;
2) Data consistency problem: because of the distributed nature of the edge devices, the consistency of the data is difficult to ensure, so that some data synchronization and replication techniques are required to ensure the consistency and reliability of the data;
3) Standardization issues, currently lacking uniform standards and specifications, result in compatibility and interoperability issues between different vendors and systems.
Disclosure of Invention
The invention aims to provide a method for acquiring and storing data at the edge of the Internet of things, which is used for solving the problems.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
the method for acquiring and storing the data of the edge end of the Internet of things comprises the following steps:
s1, constructing an Internet of things management platform and setting a plurality of equipment access modes;
s2, based on functions and definitions of equipment, an object model of the equipment is built on the Internet of things management platform, an access mode matched with the equipment is selected, the equipment is dynamically modeled by adopting the object model, the equipment is accessed into the Internet of things management platform, and the equipment is subjected to full life cycle on-line management;
s3, constructing a visual rule engine, acquiring equipment information, and performing data conversion on the equipment information based on the visual rule engine to obtain equipment data;
s4, storing the converted equipment data into different application databases in a classified mode.
Preferably, the device access mode includes device direct connection, device gateway and third party platform API docking.
Preferably, the step of accessing the equipment in the S2 to the basic management platform of the internet of things specifically includes the following steps:
s21, developing a protocol packet of the equipment by a developer, wherein the protocol packet is used for authentication and encoding and decoding of the equipment;
s22, uploading the protocol package to the Internet of things management platform, judging whether the protocol package is a new protocol or not by the Internet of things management platform through a protocol management module, if so, adding the new protocol to the protocol management module and issuing, otherwise, editing the existing protocol in the protocol management module and reissuing;
s23, creating product information of the equipment, adding the equipment into an equipment management module, and activating the equipment;
and S24, creating a network component and a device access gateway for connecting the device, wherein when the device sends a message to the Internet of things management platform, the Internet of things management platform calls the message to encode and decode through the device access gateway, and reads the message information.
Preferably, the object model includes devices, components and functions, wherein the functions include attributes, behaviors and events, the attributes are readable or settable parameter functions supported by the devices, the behaviors are capabilities or methods that the devices can be invoked externally, and the events are states which occur when the devices are in operation and need to be perceived and processed externally.
Preferably, the on-line management of the full life cycle includes device management, status monitoring, remote upgrade, data acquisition, messaging, data flow, and rules engine.
Preferably, the step S3 specifically includes the following steps:
s31, constructing a visual rule engine based on Node-RED;
s32, the rule engine acquires the rule configured by the user, and analyzes the rule into a topic, an attribute conversion rule and a triggering condition through a rule analyzer;
s33, the rule engine recursively forms a rule reasoning network according to the triggering condition to recursively form a rule reasoning network, and adopts a Redis hash type to add a main key ID of a rule as the field by taking a 'product Key|topic' as a hash table key, and an attribute conversion rule as a value cache;
s34, subscribing to the equipment message by a rule engine, and acquiring all attribute conversion rules under 'product Key|topic' from a Redis cache;
s35, the attribute conversion rule and the equipment message are processed in parallel through the data conversion module to obtain converted equipment data.
Preferably, the step S4 specifically includes the following steps:
s41, pushing the device data into a rule reasoning network, and obtaining the main key ID of the rule successfully matched through rule matching verification of an application rule engine,
s42, acquiring a data destination with a well-configured rule from an application database, and pushing out the converted equipment data;
s43, performing persistence processing on the converted device data, and storing the device data in a corresponding application database for storage.
Preferably, the device message includes message metadata, message payload, message type, and message source entity.
Preferably, the application database comprises a relational database, a time sequence database and a non-relational database.
After the technical scheme is adopted, compared with the background technology, the invention has the following beneficial effects:
1. the invention provides a method for acquiring and storing data at the edge of an Internet of things, which adopts a combination mode of a unified access technology integrating multi-source heterogeneous equipment, an equipment full life cycle management technology based on an object model, a customizable visual rule engine technology and a database design scheme, and is used for solving a series of data problems, equipment problems and application problems in application scenes of wide interconnection of everything and deep man-machine interaction.
2. The invention provides a method for collecting and storing data at the edge of the Internet of things, which enables multi-source heterogeneous data generated by multiple devices of the Internet of things to be more convenient to analyze and share, and simultaneously solves the problem of low data utilization efficiency caused by lack of service relevance between mass data by accessing and fusing data, thereby fully utilizing the data value.
3. The invention provides a method for acquiring and storing data at the edge of the Internet of things, which ensures that the newly added application does not need to be custom developed and developed for different standards for multiple times along with the increase of industrial application and equipment quantity so as to reduce the business replication cost and solve the problems of high development cost and long time of equipment access caused by different standards and diversified data types of different equipment.
4. The invention provides a method for acquiring and storing data at the edge of the Internet of things, which solves the problems of multiple access protocols and multiple data models among different manufacturers and respective sealing, reduces the difficulty of collaboration among the main bodies of an industrial chain, enhances the equipment linkage and service compatibility, and improves the user experience.
5. The invention provides a method for acquiring and storing data at the edge of the Internet of things, which is characterized in that terminal equipment entities are digitally described, equipment virtualization is realized at a cloud end, application development of the Internet of things can be directly carried out based on cloud virtual equipment, and research and development of the terminal equipment can be synchronously carried out, so that an original serial research and development flow is changed into a parallel research and development flow, the research and development period is shortened, and the labor and resource cost is saved.
Drawings
FIG. 1 is a flow chart of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the following examples in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Examples
The invention discloses a method for acquiring and storing data of an edge end of an Internet of things by matching with the figure 1, which comprises the following steps:
s1, constructing an Internet of things management platform, integrating various heterogeneous devices by taking IOT connection management as a core unified access standard rule, enabling the system to adapt to various network environments and common transmission protocols, realizing quick access and unified management of various hardware terminals and manufacturer device management platforms, and integrating various heterogeneous systems and distributed resources to realize management and control integration, so as to construct the Internet of things integrated access management system.
And setting a plurality of equipment access modes, wherein the equipment access modes comprise equipment direct connection, equipment gateway and third party platform API butt joint. The network equipment access scheme can adopt 2G/3G/4G, NB-IoT, loRaWAN, WIFI and the like, provides access realization of various protocols such as MQTT, UDP, TCP, HTTP and the like, and meets the use requirements of various application scenes.
The equipment manufacturer can complete equipment access flow through platform unified standards, and after the manufacturer is integrated on the equipment, the equipment is safely accessed to the Internet of things management platform through the SDK, so that the equipment can be managed by the Internet of things management platform. The Internet of things equipment is accessed to the SDK, and a simple and standard rapid access technical means is provided for terminal equipment manufacturers. The user only needs to deploy SDK source codes in the target system to compile and carry out necessary environment configuration, data docking and protocol configuration, and can conveniently communicate with the management platform of the Internet of things.
S2, based on functions and definitions of the equipment, including attributes, data, services, events and the like of the equipment, an object model of the equipment is built on an Internet of things management platform, description, management and control of the equipment are facilitated through unified model language, and interactive communication and understanding among the equipment are facilitated. The method comprises the steps of selecting an access mode matched with equipment, adopting an object model to dynamically model the equipment, accessing the equipment into an Internet of things management platform, and carrying out full life cycle on-line management on the equipment, so that business personnel do not need to care about complicated equipment access and management processes, and can concentrate on business excavation.
The object model refers to digitizing an entity of a physical space and constructing a data model of the entity at a cloud end. The object model describes a physical entity, which is a digitized representation of an entity in physical space.
The object model of the Internet of things management platform belongs to a grammar semantic layer on an application protocol, wherein the grammar layer defines the types of object model description languages, such as XML, JSON and the like; the semantic layer defines the basic keywords that need to be included when describing the object model in detail using a description language. In the management platform of the Internet of things, the standard format definition of the service data of the terminal equipment is completed by the object model.
Meanwhile, in the aspect of business logic, the object model belongs to an equipment management module of an Internet of things management platform. Different devices are connected with an application platform by using a unified object model standard, and data intercommunication is carried out among different applications by using the unified object model standard. The object model is used as a basic capability of data access, and needs to interact with other functions of the device management module, such as device data storage, online debugging tools and the like.
The object model includes devices, components and functions, wherein the functions include attributes, behaviors and events, and three dimensions of the attributes, behaviors and events include what the device can do, what can be done, and which information can be provided externally.
The attribute is a readable or settable parameter function supported by the device, and is generally used for describing the running state of the device, and a user can change the running state of the device through a set request mode. The behavior is the capability or method that the device can be invoked externally, input parameters and output parameters can be set, the event is a state which occurs when the device runs and needs to be perceived and processed externally, one or more output parameters can be contained, and the device reports period information or alarm information through the event.
The full life cycle on-line management includes device management, status monitoring, remote upgrade, data acquisition, messaging, data flow, and rules engine.
The device access internet of things basic management platform in S2 specifically comprises the following steps:
s21, developing a protocol packet of the equipment by a developer, wherein the protocol packet is used for authentication and encoding and decoding of the equipment;
s22, uploading the protocol package to an Internet of things management platform, judging whether the protocol package is a new protocol or not by the Internet of things management platform through a protocol management module, if so, adding the new protocol in the protocol management module and issuing, otherwise, editing the existing protocol in the protocol management module and reissuing;
s23, creating product information of the equipment, adding the equipment into an equipment management module, and activating the equipment;
and S24, creating a network component and a device access gateway for connecting the device, and when the device sends a message to the Internet of things management platform, the Internet of things management platform calls the message to encode and decode through the device access gateway, and reads the message information.
S3, constructing a visual rule engine, acquiring equipment information, and performing data conversion on the equipment information based on the visual rule engine to acquire equipment data.
The step S3 specifically comprises the following steps:
s31, constructing a visual rule engine based on Node-RED;
the rules engine provides a visual, procedural data (logic) processing tool. The method has flexible rule model configuration, and supports various rule models and custom rule models. The device alarms, scene linkage and the like of the platform are managed by a unified rule engine. SQL may be used in the rules engine to subscribe to data in the message gateway and forward the processed data to a designated place, such as: send message notifications, push to MQ, etc. Support standard sql grammar and expansion functions, support aggregation functions, window functions, etc. While the alert rules are set by the rules engine and corresponding actions, such as notifications, are enabled to forward alert messages. ( The Node-RED is a visual Internet of things arranging tool, equipment, a server and API applications can be connected based on a Flow editor of a browser, nodeJS language is used in the background, web pages are provided for writing Flow, a user can complete the creation of the Flow by dragging the browser, protocols such as http, mqtt, websocket, tcp, udp and the like are supported, and all mainstream linking equipment and servers are supported. The Node-RED uses a Nodejs event driven non-blocking model, and has lower requirements on hardware environment. )
S32, the rule engine acquires the rule configured by the user, and analyzes the rule into a topic, an attribute conversion rule and a triggering condition through a rule analyzer;
s33, the rule engine recursively forms a rule reasoning network according to the triggering condition to recursively form a rule reasoning network, and adopts a Redis hash type to add a main key ID of a rule as the field by taking a 'product Key|topic' as a hash table key, and an attribute conversion rule as a value cache;
in the process of operating the rule engine, a new rule is added to a certain equipment product, and the rule engine synchronously updates the rule reasoning network, the database and the Redis cache. If the added rule is deleted or modified, the rule engine updates the connection relation between the cache and the reasoning network node related to the rule; meanwhile, the rule engine can continuously delete the nodes which are free outside the inference network due to rule deletion or update in the inference network.
S34, subscribing to the equipment message by a rule engine, and acquiring all attribute conversion rules under 'product Key|topic' from a Redis cache;
s35, processing the attribute conversion rule and the equipment message in parallel through a data conversion module to obtain converted equipment data;
s4, storing the converted equipment data into different application databases in a classified mode.
The step S4 specifically comprises the following steps:
s41, pushing the device data into a rule reasoning network, and obtaining the main key ID of the rule successfully matched through rule matching verification of an application rule engine,
s42, acquiring a data destination with well-configured rules from an application database, pushing out the converted equipment data, thereby completing equipment data circulation, and if no related rules are acquired from a cache, indicating that no related rules are configured, only carrying out log embedding on the data.
S43, performing persistence processing on the converted device data, adopting different persistence schemes for different data, designing different application database structures and data dictionaries, and storing the device data into a corresponding application database for storage.
The device message is not only the package of the uploading data of the client, but also the event message generated when the management platform manages the entity of the platform, and the device message comprises message metadata, message load, message type and message source entity.
Message metadata and message payload are objects that can store common data structures or a combination of these data structures. The message type is the type of the flag message, mainly: data uploading information, attribute uploading information, equipment RPC calling server information, equipment connection information, equipment disconnection information, entity modifying information, entity deleting information and other types. The message source entity represents the generating entity of the message. For device generation, the message source entity is the device. For messages generated by the operation of an entity, the message source entity is the entity being operated upon.
The system comprises a platform, a control platform and a control platform, wherein necessary data, configuration parameters and system parameters are stored in a centralized manner in the platform operation; the system establishes a plurality of application databases to respectively complete different functions and store the data of the different functions. The data structure of each database table and the type and size of each data item have been defined in the application database definition, and the data storage of the entire application follows these data storage rules. The design of the database table follows the 3-range practical principle, and the constraint, index and main foreign key relation are all clearly defined.
The application database comprises a relational database, a time sequence database and a non-relational database.
Relational database: for business data, such as information of users, equipment, related configuration and the like, a relational database is adopted to support Mysql5.7+, postgreSQL 9+ and SqlServer.
A time sequence database: the elastsearch time sequence data is used for realizing the time sequence database related function and is used for storing device messages, data and the like. The grouping statistical query can be performed according to time periods, and the index is supported to be tabulated according to months. The time sequence data persistence is oriented to interface programming, and the storage scheme can be replaced according to the situation.
Non-relational database: information such as cache, device configuration, status, etc. is stored in redis. The log is stored using an elastic search, and the index is tabulated monthly.
The present invention is not limited to the above-mentioned embodiments, and any changes or substitutions that can be easily understood by those skilled in the art within the technical scope of the present invention are intended to be included in the scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.
Claims (9)
1. The method for acquiring and storing the data of the edge of the Internet of things is characterized by comprising the following steps of:
s1, constructing an Internet of things management platform and setting a plurality of equipment access modes;
s2, based on functions and definitions of equipment, an object model of the equipment is built on the Internet of things management platform, an access mode matched with the equipment is selected, the equipment is dynamically modeled by adopting the object model, the equipment is accessed into the Internet of things management platform, and the equipment is subjected to full life cycle on-line management;
s3, constructing a visual rule engine, acquiring equipment information, and performing data conversion on the equipment information based on the visual rule engine to obtain equipment data;
s4, storing the converted equipment data into different application databases in a classified mode.
2. The method for acquiring and storing the edge data of the internet of things according to claim 1, wherein the method comprises the following steps: the device access mode comprises direct connection of devices, device gateway and docking of a third party platform API.
3. The method for acquiring and storing the edge data of the internet of things according to claim 1, wherein the method comprises the following steps: s2, the equipment accessing the basic management platform of the Internet of things specifically comprises the following steps:
s21, developing a protocol packet of the equipment by a developer, wherein the protocol packet is used for authentication and encoding and decoding of the equipment;
s22, uploading the protocol package to the Internet of things management platform, judging whether the protocol package is a new protocol or not by the Internet of things management platform through a protocol management module, if so, adding the new protocol to the protocol management module and issuing, otherwise, editing the existing protocol in the protocol management module and reissuing;
s23, creating product information of the equipment, adding the equipment into an equipment management module, and activating the equipment;
and S24, creating a network component and a device access gateway for connecting the device, wherein when the device sends a message to the Internet of things management platform, the Internet of things management platform calls the message to encode and decode through the device access gateway, and reads the message information.
4. The method for acquiring and storing the edge data of the internet of things according to claim 1, wherein the method comprises the following steps: the object model comprises equipment, components and functions, wherein the functions comprise attributes, behaviors and events, the attributes are readable or settable parameter functions supported by the equipment, the behaviors are capabilities or methods which can be externally invoked by the equipment, and the events are states which occur when the equipment runs and need to be externally perceived and processed.
5. The method for acquiring and storing the edge data of the internet of things according to claim 1, wherein the method comprises the following steps: the full life cycle online management includes device management, status monitoring, remote upgrade, data acquisition, message communication, data flow and rules engine.
6. The method for acquiring and storing the edge data of the internet of things according to claim 1, wherein the method comprises the following steps: the step S3 specifically comprises the following steps:
s31, constructing a visual rule engine based on Node-RED;
s32, the rule engine acquires the rule configured by the user, and analyzes the rule into a topic, an attribute conversion rule and a triggering condition through a rule analyzer;
s33, the rule engine recursively forms a rule reasoning network according to the triggering condition to recursively form a rule reasoning network, and adopts a Redis hash type to add a main key ID of a rule as the field by taking a 'product Key|topic' as a hash table key, and an attribute conversion rule as a value cache;
s34, subscribing to the equipment message by a rule engine, and acquiring all attribute conversion rules under 'product Key|topic' from a Redis cache;
s35, the attribute conversion rule and the equipment message are processed in parallel through the data conversion module to obtain converted equipment data.
7. The method for acquiring and storing the edge data of the internet of things according to claim 6, wherein the method comprises the following steps: the step S4 specifically comprises the following steps:
s41, pushing the device data into a rule reasoning network, and obtaining the main key ID of the rule successfully matched through rule matching verification of an application rule engine,
s42, acquiring a data destination with a well-configured rule from an application database, and pushing out the converted equipment data;
s43, performing persistence processing on the converted device data, and storing the device data in a corresponding application database for storage.
8. The method for acquiring and storing the edge data of the internet of things according to claim 6, wherein the method comprises the following steps: the device message includes message metadata, a message payload, a message type, and a message source entity.
9. The method for acquiring and storing the edge data of the internet of things according to claim 6, wherein the method comprises the following steps: the application database comprises a relational database, a time sequence database and a non-relational database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310314248.4A CN116340413A (en) | 2023-03-28 | 2023-03-28 | Internet of things edge data acquisition and storage method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310314248.4A CN116340413A (en) | 2023-03-28 | 2023-03-28 | Internet of things edge data acquisition and storage method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116340413A true CN116340413A (en) | 2023-06-27 |
Family
ID=86892617
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310314248.4A Pending CN116340413A (en) | 2023-03-28 | 2023-03-28 | Internet of things edge data acquisition and storage method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116340413A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116980483A (en) * | 2023-07-24 | 2023-10-31 | 深圳市微能信息科技有限公司 | Fire-fighting Internet of things data access method and system |
| CN117527861A (en) * | 2024-01-05 | 2024-02-06 | 四川盛邦润达科技有限公司 | Equipment access method, internet of things gateway and Internet of things visualization platform |
| CN117667065A (en) * | 2023-12-08 | 2024-03-08 | 格瑞利(江苏)智能科技有限公司 | Low-code application configuration platform |
| CN117857608A (en) * | 2024-03-07 | 2024-04-09 | 安徽慕京信息技术有限公司 | Method and system for collecting equipment data based on Internet of things platform |
-
2023
- 2023-03-28 CN CN202310314248.4A patent/CN116340413A/en active Pending
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116980483A (en) * | 2023-07-24 | 2023-10-31 | 深圳市微能信息科技有限公司 | Fire-fighting Internet of things data access method and system |
| CN117667065A (en) * | 2023-12-08 | 2024-03-08 | 格瑞利(江苏)智能科技有限公司 | Low-code application configuration platform |
| CN117527861A (en) * | 2024-01-05 | 2024-02-06 | 四川盛邦润达科技有限公司 | Equipment access method, internet of things gateway and Internet of things visualization platform |
| CN117527861B (en) * | 2024-01-05 | 2024-03-22 | 四川盛邦润达科技有限公司 | Equipment access method, internet of things gateway and Internet of things visualization platform |
| CN117857608A (en) * | 2024-03-07 | 2024-04-09 | 安徽慕京信息技术有限公司 | Method and system for collecting equipment data based on Internet of things platform |
| CN117857608B (en) * | 2024-03-07 | 2024-05-03 | 安徽慕京信息技术有限公司 | Method and system for collecting equipment data based on Internet of things platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116340413A (en) | Internet of things edge data acquisition and storage method | |
| CN103336813B (en) | A kind of Internet of Things data integrated management scheme based on middleware framework | |
| CN110601876A (en) | Intelligent Internet of things platform | |
| CN102349056A (en) | Dynamically composing data stream processing applications | |
| Xu et al. | Eaaas: Edge analytics as a service | |
| CN113992769B (en) | Industrial Internet information exchange method | |
| Jeong et al. | An IoT platform for civil infrastructure monitoring | |
| Reinfurt et al. | Applying IoT patterns to smart factory systems | |
| CN103530538B (en) | A kind of XML secured views querying method based on Schema | |
| CN113868306A (en) | Data modeling system and method based on OPC-UA specification | |
| CN112287114A (en) | Knowledge graph service processing method and device | |
| Vandana et al. | Semantic ontology based IoT-resource description | |
| CN106446256A (en) | Real-time industrial production information sensation system based on context calculation | |
| Sehic et al. | A programming model for context-aware applications in large-scale pervasive systems | |
| CN114254606A (en) | Microservice framework model | |
| CN118259880A (en) | Rule chain-based service combination interface design method | |
| CN101924815A (en) | 3G MOA phone middleware embedded system | |
| CN113721856A (en) | Digital community management data storage system | |
| CN112486706A (en) | Internet of things local equipment linkage method based on MQTT message driving mechanism | |
| CN114528270A (en) | System and method for automatically associating real-time stream data with service dimension information in cloud environment | |
| CN116521664A (en) | Data monitoring method and device for data warehouse, computing equipment and storage medium | |
| Wang et al. | Semantic Information Modeling and Implementation Method for Water Conservancy Equipment | |
| CN114124859B (en) | Intelligent customer service robot of network maintenance platform and maintenance method | |
| Li et al. | Design of smart home management system based on MQTT and FBP | |
| Schreiber et al. | Context-aware self adapting systems: a ground for the cooperation of data, software, and 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 |