CN114945040A - Internet of things equipment management system based on cloud edge cooperation - Google Patents
Internet of things equipment management system based on cloud edge cooperation Download PDFInfo
- Publication number
- CN114945040A CN114945040A CN202210339717.3A CN202210339717A CN114945040A CN 114945040 A CN114945040 A CN 114945040A CN 202210339717 A CN202210339717 A CN 202210339717A CN 114945040 A CN114945040 A CN 114945040A
- Authority
- CN
- China
- Prior art keywords
- equipment
- cloud
- template
- attribute
- 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.)
- Pending
Links
- 230000004048 modification Effects 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 9
- 238000013480 data collection Methods 0.000 claims description 3
- 239000000126 substance Substances 0.000 claims description 2
- 238000012545 processing Methods 0.000 abstract description 7
- 238000003672 processing method Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 9
- 238000004422 calculation algorithm Methods 0.000 description 8
- 238000000034 method Methods 0.000 description 7
- 238000004364 calculation method Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000003068 static effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 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
- 238000012795 verification Methods 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
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
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Communication Control (AREA)
Abstract
The application relates to an Internet of things equipment management system based on cloud-edge cooperation, which comprises a cloud end, an edge end and an equipment end, wherein the cloud end is used for generating a unified data acquisition module and sending the unified data acquisition module to the edge end; the equipment end is used for acquiring original data and sending the original data to the edge end; the edge end is used for receiving the uniform data acquisition module issued by the cloud end, receiving the original data sent by the equipment end, converting the original data into standard data based on a preset configuration format in the uniform data acquisition module, and sending the standard data to the cloud end. According to the data processing method and device, data of a large number of edge devices with different structures can be acquired and converted into standard data, the standard data are sent to the cloud, the risk of data loss when the edge gateway is down is reduced, updating and upgrading of the gateway or the Internet of things devices can be achieved in batches and on a large scale through the cloud, and the data processing efficiency of the Internet of things devices is improved.
Description
Technical Field
The application relates to the technical field of the Internet of things, in particular to an Internet of things equipment management system based on cloud edge collaboration.
Background
With the development of the internet of things and cloud computing technology, the number of devices currently accessed into the internet of things is increasing, the devices comprise various machines and sensors, smart homes, vehicles, wearable devices, industrial devices and the like, the data volume generated each year is huge, and at present, almost half of data in the internet of things can be processed at network edge nodes in order to improve the data processing speed of the internet of things.
The edge, as an extension of the cloud, may provide IoT (Internet of Things) device access and data collection capabilities. On the edge node, because the formats of various devices are not uniform, the data acquired by the edge node all need to be converted by a plurality of layers of protocols, and finally the data is reported to the gateway, so that the data acquisition is realized.
The traditional internet of things equipment management efficiency is increasingly unable to meet the explosive growth of large-scale equipment and data, for example, for a scene with a large amount of edge equipment, if a gateway is down, data of the edge equipment connected with the gateway is lost. Moreover, if the upgrade gateway needs to be updated, batch large-scale update in a short time cannot be achieved, and in addition, the control instruction flow of the conventional IoT scene issuing device is complex, for example, when the device is authenticated, fine-grained control of the device from a cloud end and the like all result in complex data processing flow and reduction of data processing efficiency.
Disclosure of Invention
Based on this, it is necessary to provide an internet of things device management system based on cloud edge coordination, in order to solve the above technical problems.
An internet of things equipment management system based on cloud edge collaboration, the system comprising: the system comprises a cloud end, an edge end and an equipment end; wherein the content of the first and second substances,
the cloud end is used for generating a unified data acquisition module and sending the unified data acquisition module to the edge end;
the equipment end is used for acquiring original data and sending the original data to the edge end;
the edge end is used for receiving the unified data acquisition module issued by the cloud end, receiving the original data sent by the equipment end, converting the original data into standard data based on a preset configuration format in the unified data acquisition module, and sending the standard data to the cloud end.
In one embodiment, the cloud comprises a device controller; the cloud end is used for constructing an equipment template, binding an equipment instance based on the equipment template, and generating the unified data acquisition module by using the corresponding relation between the equipment instance and the equipment template through the equipment controller.
In one embodiment, the cloud is further configured to obtain a device protocol input by a user, and construct the device template based on the device protocol by using an automatic assembly model.
In one embodiment, the device protocol number is multiple; the automatic assembly model is further used for carrying out correctness verification on the equipment protocols, and if the equipment protocols are correct, the equipment template is constructed.
In one embodiment, the cloud is further configured to feed back corresponding first modification prompt information if the device protocol is incorrect.
In one embodiment, the cloud is configured to perform correctness checking on the number of attribute entries in the device instance and the number of attribute entries in the device template by using the device controller, and if the number of attribute entries in the device instance is equal to the number of attribute entries in the device template, generate the unified data collection module.
In one embodiment, the cloud is configured to feed back the corresponding second modification prompt information if the number of the attribute entries in the device instance is not equal to the number of the attribute entries in the device template.
In one embodiment, the device instance contains at least one of a device template name, a device transport protocol, device attribute access information, and a device twin attribute.
In one embodiment, the device template is a template constructed based on the kubernets API.
In one embodiment, the device template includes at least one of a template name, a device attribute description, a device attribute access mode, a device attribute preset maximum, and a device attribute unit.
The embodiment provides an internet of things equipment management system based on cloud edge coordination, which comprises a cloud end, an edge end and an equipment end, wherein the cloud end is used for generating a uniform data acquisition module and sending the uniform data acquisition module to the edge end; the device end is used for acquiring original data and sending the original data to the edge end; the edge end is used for receiving the uniform data acquisition module issued by the cloud end, receiving the original data sent by the equipment end, converting the original data into standard data based on a preset configuration format in the uniform data acquisition module, and sending the standard data to the cloud end. According to the data processing method and device, data of a large number of edge devices with different structures can be acquired and converted into standard data, the standard data are sent to the cloud, the risk of data loss when the edge gateway is down is reduced, updating and upgrading of the gateway or the Internet of things devices can be achieved in batches and on a large scale through the cloud, and the data processing efficiency of the Internet of things devices is improved.
Drawings
Fig. 1 is a system structure diagram of an internet of things device management system based on cloud edge coordination in one embodiment;
fig. 2 is a diagram of an application environment of an internet of things device management system in cloud-side collaboration in another embodiment;
fig. 3 is a system structure diagram of an internet of things device management system based on cloud edge coordination in another embodiment;
FIG. 4 is a diagram illustrating an internal structure of a computer device according to an embodiment;
fig. 5 is an internal structural diagram of a computer device in another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application 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 and not restrictive on the broad application.
The internet of things equipment management system based on cloud edge collaboration is shown in fig. 1. The device terminal 103 is connected to the edge terminal 102 through a network, and the edge terminal 102 is connected to the cloud terminal 101. The device end 103 is various intelligent devices, including but not limited to personal computers, notebook computers, smart phones, tablet computers and portable wearable devices of different structures manufactured by different manufacturers, such as signal acquisition and test devices of various access control devices, air conditioners, smart meters or smart water meters, and the edge end 102, i.e., an edge gateway, is a gateway at the edge of a network, and can provide functions of lightweight connection management, protocol conversion, real-time data analysis and application management; the cloud 103 may be a SaaS (Software-as-a-Service) based cloud server.
In one embodiment, as shown in fig. 2, the cloud end 103 may be connected to the terminal device 100 of the user through a network, so that the user can manage the edge end 102 and the device end 103 on the terminal device.
In an embodiment, as shown in fig. 3, fig. 3 shows a specific structural block diagram of the internet of things device management system based on cloud edge collaboration. The system comprises a cloud end, an edge end and an equipment end, wherein the cloud end is used for generating a unified data acquisition module and sending the unified data acquisition module to the edge end.
Specifically, the user realizes management and control of the cloud end through the terminal device, the user inputs various required configuration information at the terminal device, and the cloud end generates the unified data acquisition module according to the configuration information. The unified data acquisition module is a data acquisition module for devices of the same category, for example, data acquisition is realized for devices of different models of air conditioners, and the data acquisition module is converted into a unified format. The cloud 101 automatically generates a unified data acquisition module according to configuration information input by a user, and issues the module to the edge terminal 102, that is, an edge gateway, and lays out the unified data acquisition module on the edge gateway.
The equipment end is used for acquiring original data and sending the original data to the edge end;
specifically, the device side is various terminal devices, such as an air conditioner, a water meter and the like, arranged in the internet of things. Because manufacturers are different, the models of the devices of the same type are different, and the formats of the original data acquired by the devices are different, the original data generated by the devices of different types need to be converted into a uniform format for processing by a cloud.
The edge end is used for receiving the uniform data acquisition module issued by the cloud end, receiving the original data sent by the equipment end, converting the original data into standard data based on a preset configuration format in the uniform data acquisition module, and sending the standard data to the cloud end.
Specifically, the edge end converts the original data of different formats and different types sent by the equipment end into standard data by using the unified data acquisition module, and sends the standard data to the cloud end.
According to the embodiment, a large amount of data of the edge devices with different structures can be acquired and converted into the standard data, the standard data are sent to the cloud, the risk of data loss when the edge gateway is down is reduced, the updating and upgrading of the gateway or the internet of things devices can be realized in batches and on a large scale through the cloud, and the data processing efficiency of the internet of things devices is improved.
In one embodiment, the cloud comprises a device controller; and the cloud is used for constructing the equipment template, binding the equipment instance based on the equipment template, and generating the unified data acquisition module by using the corresponding relation between the equipment instance and the equipment template through the equipment controller.
Specifically, the cloud includes a device controller, an algorithm for creating a device template is run in the device controller, the device template describes device attributes of similar devices (the devices are based on a similar protocol), the device attributes include configuration such as attribute names, default values, types and the like, and a user can access the attributes to obtain corresponding information. The equipment template is a reusable template and can manage large-scale equipment with the same category and the same protocol. The device template may bind multiple different device instances, for example, the same device template may bind different brands of air conditioners from different manufacturers. The device instance represents an actual device object, and has a strong coupling relationship with the device template, which is equivalent to referencing the attributes defined in the device template and performing corresponding instantiation. The device access specifications in the device instance (i.e., some inherent properties of the device itself) are static, but the data changes in the device properties are dynamic with the reporting of the state of the device itself (e.g., data collected by the device, such as temperature, whether the device is currently in a normal or faulty state). The user inputs the property information of the device instance to be bound, the device controller automatically generates a device template according to the property information and the corresponding algorithm, and simultaneously the device template is bound with the device instances. And the equipment controller generates a unified data acquisition module according to the established corresponding relation between the equipment template and the equipment instance.
According to the embodiment, the device template is established at the cloud running device controller, and the unified data acquisition modules of the device examples of the same type and different types are automatically established, so that the original data of the device examples of different types are subsequently converted into standard data, the access compatibility of different device examples is improved, different edge gateways do not need to be customized by manufacturers, the access flow of the device examples is simplified, and the data can be efficiently processed in batches.
In an embodiment, the cloud is further configured to obtain a device protocol input by a user, and construct a device template based on the device protocol by using the automatic assembly model.
Due to the fact that protocols used by different devices are different, the cloud end can also build a device template by utilizing an automatic assembly model according to device protocols of a plurality of device instances input by a user.
Specifically, an automatic assembly model of various protocols is provided in the algorithm:
{protocol 1 ,protocol 2 ,…,protocol n }
wherein, protocol n (n-1, 2,3 … …) are names of respective protocols, each protocol representing a class of devices; after the configuration information (including various protocols and equipment attributes) is input, equipment templates can be created and automatically assembled, and the calculation formula is as follows:
Model＝protocol(p 1 ,p 2 ,…,p n )，p 1 to p n The method comprises the steps of representing various attributes of specific physical equipment, packaging attribute sets into a protocol Model, and forming a final equipment template which is a Model.
The embodiment utilizes the four assembly models to automatically generate the device templates based on different device protocols, and can be adaptively compatible with different device instances.
In one embodiment, the number of device protocols is multiple; and the automatic assembly model is further used for checking the correctness of the equipment protocols, and if the equipment protocols are correct, the equipment template is constructed. And the cloud end is also used for feeding back corresponding first modification prompt information if the equipment protocol is incorrect.
Specifically, the algorithm further provides a correctness checking model corresponding to each protocol:
{check 1 ,check 2 ,…，check n }
Model＝protocol(p 1 ,p 2 ,…,p n ) Check in the above equation n Representation to device Properties p n Checking for correctness, p 1 To p n The device attributes are shown, and the Model is the final device template.
For p in the above formula 1 To p n And (5) checking, wherein the calculation formula is as follows:
when p is 1 To p n If the equipment template is correct, constructing an equipment template; when there is an error, p will be correspondingly erroneous n And feeding back to the user side as first modification prompt information to prompt the user to correct.
According to the embodiment, the automatic assembly model is used, the equipment template is automatically generated according to the equipment attribute or the equipment protocol input by the user, the equipment template can be automatically updated and upgraded, and the equipment management and control level is improved.
In an embodiment, the cloud is configured to perform correctness checking on the number of the attribute items in the device instance and the number of the attribute items in the device template by using the device controller, and if the number of the attribute items in the device instance is equal to the number of the attribute items in the device template, generate the unified data acquisition module. And the cloud end is used for feeding back corresponding second modification prompt information if the number of the attribute items in the equipment instance is not equal to the number of the attribute items in the equipment template.
Specifically, configuration content in a format required by the unified data acquisition module is generated by the device controller according to the device instance and the information of the device template bound with the device instance, and entry correctness verification is performed in the configuration generation process, wherein a calculation formula is as follows:
COUNT (P) denotes the number of attribute entries in the device instance, P d And (4) representing the number of attribute items of the equipment template, wherein the number is 0 when the attribute items are equal to each other, and otherwise, the number is 1, and second modification prompt information needs to be fed back to the user to prompt the user to modify the configuration again.
In the above embodiment, the binding between the device instance and the device template is realized by checking the number of the attribute items of the device instance and the number of the attribute items of the device template.
In an embodiment, the device instance contains at least one of a device template name, a device transport protocol, device attribute access information, and a device twin attribute.
Specifically, the construction of an instance of the device requires the input of at least one of the following parameters:
1) name, device model ref, device template name, chooses to use the created device template as an association.
2) protocol, namely, device transport protocol, and the data type is a character string, which indicates a transport protocol required by the device.
3) PropertyVisitors, which is the specific information accessed by the device attribute, and the data type is a character string.
4) And twins, namely the twin attribute of the equipment, and is used for recording the control instruction sent to the equipment and recording the data reported by the equipment.
The above embodiments provide data matting for the mathematical description of the subsequently constructed device instance by defining device attribute parameters.
In one embodiment, the device template is constructed based on the kubernets API.
Specifically, the device template in the present application is constructed based on the customized resource extended by the kubernets API and the declarative API, so that the device template can be used as a resource object that can be managed by the kubernets cluster. The device template describes device attributes of the protocol devices of the same type, and the device attributes comprise configuration of attribute names, default values, types and the like, and a user can access the attributes to obtain corresponding information. The equipment template is a reusable template and can manage large-scale equipment with the same type and the same protocol.
Similarly, the device instance is also constructed based on the customized resource extended by the kubernets API and the declarative API, and serves as a resource object which can be managed and controlled by the kubernets cluster. The device instance represents an actual device object, has a strong coupling relation with the device template, and is equivalent to reference to the attributes defined in the device model and perform corresponding instantiation. The device access specification in the device instance is static, but the data changes to the device attributes and the status reporting of the device itself are dynamic. When creating an instance of a device, various specific attribute information of the device needs to be declared, including an attribute name, an attribute type, an attribute default value, and an attribute access mode, and according to different device protocols (e.g., BLE, MODBUS, opuca), the device also needs to have a setting of a corresponding access address, so as to complete creation of an instance object of the device.
In addition, the equipment controller can generate a unified data acquisition module based on the equipment template and the equipment instance object. And the Kubernets acquires the content of the object through a List/Watch mechanism, synthesizes json data and sends the json data to the edge end to be used by the equipment data acquisition program. When the edge terminal reports the equipment state data, the controller updates the corresponding data to the corresponding equipment instance object in Kubernets, and equipment update is carried out between the edge and the cloud.
The embodiment establishes and constructs the equipment template and the equipment example based on the Kubernets API, is favorable for unified specification, and realizes easy and flexible application and rapid upgrade and deployment.
In an embodiment, the device template includes at least one of a template name, a device attribute description, a device attribute access mode, a device attribute preset maximum value, and a device attribute unit.
Specifically, the configuration parameters of the device template include at least one of the following parameters:
1) name, i.e. the name of the device template, and the data type is a character string, which is the unique identifier of the device template and is composed of lower case letters, numbers and middle drawn lines.
2) Name, i.e. the name of the property of the device associated with the template, the data type is a string.
3) Description, i.e. description of device attributes, the data type is a string.
4) property, type, int, access mode, i.e. the access mode of the device attribute, the data type is a string, the field has two types of values, namely ReadOnly and ReadWrite, ReadOnly indicates read-only, and ReadWrite indicates write-enabled.
5) property, int, maximum, i.e., the maximum value of the device attribute, which the collected data cannot exceed.
6) property. type. int. unit, i.e. the unit of device attributes.
In the above embodiment, the data is laid for the mathematical description of the device template to be constructed subsequently by defining the configuration parameters of the device template.
The above system is described below with a specific application scenario, and the specific implementation is as follows:
(1) and constructing an equipment template. And establishing an algorithm of the equipment template, and directly establishing the equipment template at the cloud end through the algorithm. The template configuration is shown in fig. 2 and includes the following aspects:
name, i.e. device template name, data type is a string, is a device template unique identifier, and consists of lower case letters, numbers and middle drawn lines.
Name, i.e. the name of the device associated with the template, and the data type is a string.
Description, namely the description of the device attribute, and the data type is a character string.
1.4) properties, type, int, accessmode, i.e. the access mode of the device attribute, the data type is a character string, the field has two types of values, namely ReadOnly and ReadWrite, ReadOnly indicates read-only, and ReadWrite indicates writable.
1.5) properties, type, int, maximum of device properties, which the collected data cannot exceed.
1.6) properties. type. int. unit, i.e. units of device attributes.
Automatic assembly models of various protocols are provided in the algorithm:
{protocol 1 ,protocol 2 ,…,protocol n }
and providing a correctness check model corresponding to each protocol:
{check 1 ,check 2 ,…,check n }
after the configuration information is input, selecting a designated model according to a protocol to establish and automatically assemble an equipment template, wherein the calculation formula is as follows:
Model＝protocol(p 1 ,p 2 ,…,p n )，p 1 to p n The device attributes are shown, and the Model is the final device template.
Meanwhile, correctness check is provided in the algorithm, and p in the formula is checked 1 To p n And (5) checking, wherein the calculation formula is as follows:
(2) and constructing an equipment instance. As shown in fig. 2, the following aspects are included:
name, i.e., device template name, chooses to use the created device template as an association.
2.2) protocol, namely device transmission protocol, the data type is character string, which represents the transmission protocol required by the device.
2.3) PropertyVisitors, i.e. the specific information accessed by the device attribute, the data type is a character string.
And 2.4) twins, namely the twin attribute of the equipment, which is used for recording the control instruction sent to the equipment and recording the data reported by the equipment.
(3) Equipment acquisition configuration generation and distribution
Generating configuration content in a format required by a data acquisition module by an equipment controller according to the information of the equipment instance and the binding equipment template thereof, and checking the correctness of the entry in the configuration generation process, wherein the calculation formula is as follows:
COUNT (P) denotes the number of attribute entries in the device instance, P d The number of attribute entries representing the device template is 0 when the two are equal, otherwise 1, and the configuration needs to be modified again.
(4) Unified data acquisition module
The acquisition module can provide equipment data acquisition of different protocols, the unified data acquisition module is issued to the edge side through the cloud center, and the module performs corresponding data acquisition by using the configuration in the step (3) and reports the data to the cloud.
According to the embodiment, the attribute information of the equipment is sent to the edge node by the cloud end through constructing the equipment template and the equipment instance template, and the application of the edge node can make a corresponding response according to the change of the information sent by the cloud end, so that cloud-edge cooperation is realized. The system replaces the traditional physical gateway, can flexibly and easily realize the rapid upgrade and deployment of the application, and realizes the efficient data acquisition from bottom to top and the device control from top to bottom.
In one embodiment, a computer device is provided, which can be used as the cloud server 101, and its internal structure diagram can be shown in fig. 4. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The database of the computer device is used for storing device templates, device attributes, device instances and collected device data. The network interface of the computer device is used for communicating with an external terminal through a network connection.
In an embodiment, a computer device is provided, and the computer device may also be a terminal, and as the cloud component, an internal structure diagram of the computer device may be as shown in fig. 5. The computer device comprises a processor, a memory, a communication interface, a display screen and an input device which are connected through a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the configurations shown in fig. 4-5 are only block diagrams of some of the configurations relevant to the present application, and do not constitute a limitation on the computing devices to which the present application may be applied, and that a particular computing device may include more or less components than shown, or combine certain components, or have a different arrangement of components.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent application shall be subject to the appended claims.
Claims (10)
1. The Internet of things equipment management system based on cloud edge collaboration is characterized by comprising the following components: the system comprises a cloud end, an edge end and an equipment end; wherein the content of the first and second substances,
the cloud end is used for generating a unified data acquisition module and sending the unified data acquisition module to the edge end;
the equipment end is used for acquiring original data and sending the original data to the edge end;
the edge end is used for receiving the unified data acquisition module issued by the cloud end, receiving the original data sent by the equipment end, converting the original data into standard data based on a preset configuration format in the unified data acquisition module, and sending the standard data to the cloud end.
2. The system of claim 1, wherein the cloud comprises a device controller; the cloud end is used for constructing an equipment template, binding an equipment instance based on the equipment template, and generating the unified data acquisition module by using the corresponding relation between the equipment instance and the equipment template through the equipment controller.
3. The system of claim 2, wherein the cloud is further configured to obtain a device protocol input by a user, and wherein the device template is constructed based on the device protocol using an automated assembly model.
4. The system of claim 3, wherein the device protocol number is plural; the automatic assembly model is further used for checking correctness of the equipment protocol, and if the equipment protocols are correct, the equipment module is constructed.
5. The system of claim 4, wherein the cloud is further configured to feed back the corresponding first modification hint if the device protocol is incorrect.
6. The system according to claim 2, wherein the cloud is configured to perform, by using the device controller, correctness check on the number of attribute entries in the device instance and the number of attribute entries in the device template, and if the number of attribute entries in the device instance is equal to the number of attribute entries in the device template, generate the unified data collection template.
7. The system of claim 6, wherein the cloud is configured to feed back the corresponding second modification prompt if the number of the attribute entries in the device instance is not equal to the number of the attribute entries in the device template.
8. The system of claim 2, wherein the device instance contains at least one of a device template name, a device transport protocol, device attribute access information, and a device twin attribute.
9. The system of claim 2, wherein the device template is a template constructed based on the kubernets API.
10. The system according to any one of claims 2 to 9, wherein the device template includes at least one of a template name, a device attribute description, a device attribute access pattern, a device attribute preset maximum, and a device attribute unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210339717.3A CN114945040A (en) | 2022-04-01 | 2022-04-01 | Internet of things equipment management system based on cloud edge cooperation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210339717.3A CN114945040A (en) | 2022-04-01 | 2022-04-01 | Internet of things equipment management system based on cloud edge cooperation |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114945040A true CN114945040A (en) | 2022-08-26 |
Family
ID=82906274
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210339717.3A Pending CN114945040A (en) | 2022-04-01 | 2022-04-01 | Internet of things equipment management system based on cloud edge cooperation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114945040A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108173874A (en) * | 2018-01-29 | 2018-06-15 | 海尔优家智能科技（北京）有限公司 | A kind of intelligent device management method, platform, system, medium and equipment |
| US20200034351A1 (en) * | 2018-07-25 | 2020-01-30 | Denso International America, Inc. | Source Authentication And Changed Primitive Verification Systems And Methods For Real Time Updating Of Cloud-Based HD 3-D Map |
| CN112714193A (en) * | 2021-03-26 | 2021-04-27 | 深圳佳兆业科技集团有限公司 | Community data processing system, method, device and equipment based on Internet of things platform |
| CN114221690A (en) * | 2021-12-16 | 2022-03-22 | 中国人民解放军国防科技大学 | Semantic model construction method for cloud edge cooperative system |
-
2022
- 2022-04-01 CN CN202210339717.3A patent/CN114945040A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108173874A (en) * | 2018-01-29 | 2018-06-15 | 海尔优家智能科技（北京）有限公司 | A kind of intelligent device management method, platform, system, medium and equipment |
| US20200034351A1 (en) * | 2018-07-25 | 2020-01-30 | Denso International America, Inc. | Source Authentication And Changed Primitive Verification Systems And Methods For Real Time Updating Of Cloud-Based HD 3-D Map |
| CN112714193A (en) * | 2021-03-26 | 2021-04-27 | 深圳佳兆业科技集团有限公司 | Community data processing system, method, device and equipment based on Internet of things platform |
| CN114221690A (en) * | 2021-12-16 | 2022-03-22 | 中国人民解放军国防科技大学 | Semantic model construction method for cloud edge cooperative system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8255869B2 (en) | Industry template customization and transclusion for use in industrial automation and information solutions | |
| CN104932480A (en) | Automobile diagnostic system design method and apparatus | |
| US11797273B2 (en) | System and method for enhancing component based development models with auto-wiring | |
| TW201439792A (en) | System and method for accessing database | |
| CN111309593A (en) | JSON interface verification method, device and equipment and computer readable storage medium | |
| CN109471624B (en) | Shared data model control system based on GOSAA and data architecture generation method | |
| CN108279882B (en) | Framework generation method, device, equipment and computer readable medium | |
| CN111556158A (en) | Access method, access device, access equipment and storage medium of Internet of things platform | |
| CN109660372A (en) | A kind of method and device of the business configuration of SDN | |
| CN110825395B (en) | Multi-plug-in layered deployment system, device and medium | |
| CN114221690A (en) | Semantic model construction method for cloud edge cooperative system | |
| CN110647564B (en) | Hive table building method, electronic device and computer readable storage medium | |
| US10868880B2 (en) | Control system with persistent and transient data stores for registration, production and status data for networked devices | |
| CN109062870A (en) | The method and storage medium that server, business datum verify | |
| US20170199858A1 (en) | Form management system and method | |
| CN114945040A (en) | Internet of things equipment management system based on cloud edge cooperation | |
| CN102270126B (en) | Method and equipment for quickly determining interface code and test script parameter value | |
| CN116263659A (en) | Data processing method, apparatus, computer program product, device and storage medium | |
| CN116204554B (en) | Data processing method, system, electronic device and storage medium | |
| US8655910B1 (en) | Methods and systems for coupling client-side and server-side persistence frameworks | |
| CN112241276A (en) | Equipment upgrading method and device | |
| CN115032901B (en) | Equipment control method and electronic equipment | |
| CN117234523A (en) | Method, device, computer equipment and storage medium for configuring reactor platform functions | |
| CN114201240B (en) | Method and device for configuring helm chart | |
| CN113128187B (en) | Form generation method, device and system |
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 |