CN112764637B - Intelligent agriculture Internet of things equipment description file generation method - Google Patents
Intelligent agriculture Internet of things equipment description file generation method Download PDFInfo
- Publication number
- CN112764637B CN112764637B CN202110133489.XA CN202110133489A CN112764637B CN 112764637 B CN112764637 B CN 112764637B CN 202110133489 A CN202110133489 A CN 202110133489A CN 112764637 B CN112764637 B CN 112764637B
- Authority
- CN
- China
- Prior art keywords
- equipment
- entering
- loading
- configuration
- instruction
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/0486—Drag-and-drop
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y10/00—Economic sectors
- G16Y10/05—Agriculture
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y20/00—Information sensed or collected by the things
- G16Y20/20—Information sensed or collected by the things relating to the thing itself
-
- 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
Abstract
The invention discloses a method for generating intelligent agriculture internet of things equipment description file, which comprises the following steps: the method comprises the steps of defining equipment description specifications, defining page components, loading page components and loading equipment structures, wherein the loading page components and the loading equipment structures comprise loading of main equipment, loading of sub equipment and loading of sensors, control information of a configuration selection area, configuration information adding equipment, the sub equipment and the sensors are used for dragging label options of editing page components to a main working area in a control selection area, component attributes are set in an attribute modification area, equipment configuration lists are constructed through graphical operation, description files are dynamically generated, staff maintaining the description files only need to understand general service personnel of equipment, the general operation is easier, universality is higher, efficiency is higher, files generated in a mode of constructing the equipment configuration lists are more accurate and clear, information transmission is easier to perceive, and positioning is more convenient.
Description
Technical Field
The invention belongs to the technical field of intelligent agriculture Internet of things, and particularly relates to a method for generating an intelligent agriculture Internet of things equipment description file.
Background
Basic model of thing networking development: (1) The Internet of things equipment sends data to an Internet of things platform through a network, and the platform stores and displays the data after analyzing the data; (2) The internet of things platform sends instruction data to the equipment, and the equipment completes corresponding instruction actions. When the internet of things equipment is connected to the internet of things platform, each equipment merchant needs to provide equipment description files for the equipment to be in butt joint with the internet of things platform, and the equipment description files need to accord with a certain fixed format. Usually, a programmer generates a device description file by knocking codes, but when the device structure is very complex or the number of sensors of the device is very large, the description file also becomes complex, often thousands of lines or even tens of thousands of lines, the programming workload becomes quite huge, errors are easy to occur, and the troubleshooting work is heavy after the errors occur; at the same time, this work must be done by a programmer writing.
To date, a method for generating a description file more efficiently does not exist, namely, a method which does not need manual coding, is efficient and accurate and is easy for mass operation can be realized.
Disclosure of Invention
Aiming at the defects, the invention provides a method for generating the intelligent agriculture internet of things device description file, which constructs a device configuration list through graphical operation and dynamically generates the description file. By the invention, the staff maintaining the description file is no longer a programmer with professional coding capability, but only a general service staff understanding the equipment constitution.
In order to solve the technical problems, the invention adopts the following technical scheme: a method for generating intelligent agriculture Internet of things equipment description file comprises the following steps:
beginning at S1 and then proceeding to step S2;
step S2: defining a device description specification, normalizing basic description items of the device, and then entering step S3;
step S3, defining a page component, and then entering step S4;
and S4, loading the page component and the loading device structure body, wherein the loading device structure body comprises loading of a main device, loading of a sub device and loading of a sensor.
Further, the loading of the master device includes the steps of:
starting at step S101: selecting a main device, clicking control information and configuration information of a configuration selection area, and then entering step S102;
step S102: selecting a page component, dragging a label option for editing the page component of the main equipment to a main working area in a control selection area, and then entering step S103;
step S103: selecting a component attribute, setting the component attribute in an attribute modification area, and then proceeding to step S104;
step S104: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the actual system hardware configuration, if so, jumping to the step S102, otherwise, entering the step S105;
and step 105, integrally storing and generating a JSON description file.
Further, the loading of the sub-device comprises the following steps:
starting at step S201: newly adding a piece of sub-equipment, performing point selection on the configuration of the sub-equipment in the configuration selection area, adding the names, the type codes and the number of the sub-equipment, and then entering step 202;
step S202: selecting a page component, clicking configuration information under the configuration of the sub-equipment, dragging label options describing the sub-equipment to a main working area in a control selection area, and then entering step S203;
step S203: setting component attributes, setting component attributes in an attribute modification area and then proceeding to step 204;
step S204: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the actual system hardware configuration, if so, jumping to the step S202, otherwise, entering the step S205;
step S205: judging whether an instruction is needed, if yes, entering a step S206, otherwise, entering a step S105;
step S206: a new instruction is added, control information of the configuration selection area is selected, and then step S207 is carried out;
step S207: the configuration instruction, clicking the control selection area to drag the label options of the editing instruction component to the main working area, editing the attribute in the attribute modification area, and then entering step S208;
step S208: judging whether other instructions exist or not, if so, judging by a user according to the requirements and the system hardware configuration, if so, jumping to a step S206, otherwise, entering a step S105;
and step 105, integrally storing and generating a JSON description file.
Further, the loading of the sensor comprises the following steps:
starting at step S301: newly adding a sensor, clicking the sensor configuration of the configuration selection area, and then entering step S302;
step S302: selecting a page component, dragging a label option of the editing sensor component to a main working area in a control selection area, and then entering step S303;
step S303: setting component attributes, setting the component attributes in an attribute modification area, and then entering step 304;
step S304: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the system hardware configuration, if so, jumping to the step S302, otherwise, entering the step S305;
step S305: judging whether an instruction is needed, if yes, entering a step S306, otherwise, entering a step S105;
step S306: a new instruction is added, control information of the configuration selection area is selected, and then step S307 is carried out;
step S307: the configuration instruction, clicking the control selection area to drag the label options of the editing instruction control to the main working area, editing the attribute in the attribute modification area, and then entering step S308;
step S308: judging whether other instructions exist, if yes, jumping to the step S306, otherwise, entering the step S105;
and step 105, integrally storing and generating a JSON description file, clicking a ROOT node, and viewing the details of the JSON description file.
Further, the basic description items that all devices have include a name (name), a type (type), an identification code (code), a parameter object list (params), an instruction object list (cmds), a sensor list (sensors), and the devices may contain sub-zero to multiple sub-devices (items), as well as the description items of each sub-device.
Further, description of parameter object list: the parameter object list "params" is edited by a description item such as a parameter name (name), a parameter identification code (key), a parameter type (property type), a parameter default value (value), whether a parameter is editable (editable) or not.
Further, description of instruction object list: the instruction object list "cmds" is edited by description items such as instruction names (names), display types (displaypype) of instructions on a platform, instruction identification codes (keys), instruction processors (handlecodes) and the like.
Further, the description of the sensor list includes editing a sensor list "sensors" through a sensor identification code (key), a transmission data type (dataType), an upper data alarm threshold limit (upper limit), a lower data alarm threshold limit (lower limit), and the like.
Further, the loading page component and the loading device structure body comprise loading of a main device, loading of a sub device and loading of a sensor; the method comprises the steps of loading all data items used in description specifications and description specifications into a computer memory, initializing, distributing generated page components in a control selection area in a label mode, distributing a device structure body in a configuration selection area, and constructing and generating an interface diagram.
Further, the details of the JSON description file are formatted, so that the JSON description file is convenient to read and supports one-key copying.
Compared with the prior art, the invention has the following advantages:
1. through graphical operation, a device configuration list is constructed, the description file is dynamically generated, staff maintaining the description file is not a programmer with professional coding capability any more, only a general service person understanding the device constitution is needed, the operation of the masses is easier, the universality is stronger, and the efficiency is higher.
2. The files generated by constructing the device configuration list are more accurate and clearer.
3. And compared with pure text information, the graphical information is more easily perceived and more convenient to position in the aspect of display.
4. To promote the cost of learning to use the graphics tool to be lower than the threshold of learning JSON.
Drawings
FIG. 1 is a system flow diagram depicting a method of file generation in an embodiment of the invention;
FIG. 2 is a diagram of a device description specification program in an embodiment of the invention;
FIG. 3 is a json description file generation interface diagram in an embodiment of the invention;
FIG. 4 is a detail view of a json description file in an embodiment of the present invention;
in the drawing the view of the figure,
1-control selection area, 2-configuration selection area, 3-main working area, 4-attribute modification area.
Detailed Description
The present invention will be further described below, and it should be understood by those skilled in the art that the following examples are not intended to limit the technical scope of the present invention, but are merely sufficient to illustrate how the present invention can be implemented.
In an embodiment, the device description specification is defined by specifying basic description items of devices, such as fig. 2, where all devices have basic description items including a name (name), a type (type), an identification code (code), a parameter object list (params), an instruction object list (cmds), and a sensor list (sensors), and a device may contain zero to multiple sub-devices (items), and the description items of each sub-device may also be the same.
Description within parameter object list: the parameter object list "params" is edited by description items such as a parameter name (name), a parameter identification code (key), a parameter type (property type), a parameter default value (value), whether the parameter is editable (editable), and the like.
Description of instruction object list: the instruction object list "cmds" is edited by description items such as instruction name (name), display type (displaypype) of the instruction on the platform, instruction identification code (key), instruction processor (handlecode) and the like.
Description of the sensor list "sensors" is compiled by means of a sensor identification code (key), a transmission data type (dataType), a data alarm threshold upper limit (upperLimit), a data alarm threshold lower limit (lowerLimit) etc.
Referring to fig. 1, a method for generating a device description file of intelligent agriculture internet of things specifically includes the following steps:
the step starts at S1 and then proceeds to step S2;
step S2: defining a device description specification, normalizing basic description items of the device, and then entering step S3;
step S3, defining a page component, processing all data items used in the specification, finishing the data items into a page component capable of displaying, dragging and modifying attributes on a WEB page, and then entering step S4;
the page components and functions are as follows:
s4, loading a page component and a loading device structure body, wherein the loading device structure body comprises loading of a main device, loading of a sub device and loading of a sensor; specifically, all data items used in the description specification and the description specification are loaded into a computer memory, initialized, the generated page components are distributed in a control selection area in a label mode, a device structure body is distributed in a configuration selection area, a generated interface diagram as shown in fig. 3 is constructed, then step S101, step S201 or step S301 is carried out, no sequence exists in the steps S101, step S201 and step S301, and a user selects autonomously according to requirements and system hardware configuration.
The loading of the master device starts with step S101: selecting a main device, clicking control information and configuration information of a configuration selection area, and then entering step S102;
step S102: selecting a page component, dragging a label option for editing the page component of the main equipment to a main working area in a control selection area, and then entering step S103;
step S103: selecting a component attribute, setting the component attribute in an attribute modification area, and then proceeding to step S104;
step S104: judging whether other attributes exist or not, if so, the user judges according to the requirements and the actual system hardware configuration, if so, the step S102 is skipped, otherwise, the step S105 is entered.
The loading of the child device starts with step S201: newly adding a piece of sub-equipment, performing point selection on the configuration of the sub-equipment in the configuration selection area, adding the names, the type codes and the number of the sub-equipment, and then entering step 202;
step S202: selecting a page component, clicking configuration information under the configuration of the sub-equipment, dragging label options describing the sub-equipment to a main working area in a control selection area, and then entering step S203;
step S203: setting component attributes, setting component attributes in an attribute modification area and then proceeding to step 204;
step S204: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the actual system hardware configuration, if so, jumping to the step S202, otherwise, entering the step S205;
step S205: judging whether an instruction is needed, if yes, entering a step S206, otherwise, entering a step S105;
step S206: a new instruction is added, control information of the configuration selection area is selected, and then step S207 is carried out;
step S207: the configuration instruction, clicking the control selection area to drag the label options of the editing instruction component to the main working area, editing the attribute in the attribute modification area, and then entering step S208;
step S208: judging whether other instructions exist or not, if so, the user judges according to the requirements and the system hardware configuration, if so, the step S206 is skipped, otherwise, the step S105 is entered.
The loading of the sensor starts in step S301: newly adding a sensor, clicking the sensor configuration of the configuration selection area, and then entering step S302;
step S302: selecting a page component, dragging a label option for editing the sensor control to a main working area in a control selection area, and then entering step S303;
step S303: setting component attributes, setting the component attributes in an attribute modification area, and then entering step 304;
step S304: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the system hardware configuration, if so, jumping to the step S302, otherwise, entering the step S305;
step S305: judging whether an instruction is needed, if yes, entering a step S306, otherwise, entering a step S105;
step S306: a new instruction is added, control information of the configuration selection area is selected, and then step S307 is carried out;
step S307: the configuration instruction, clicking the control selection area to drag the label options of the editing instruction component to the main working area, editing the attribute in the attribute modification area, and then entering step S308;
step S308: judging whether other instructions exist, if yes, jumping to the step S306, otherwise, entering the step S105;
step S105, integrally storing and generating a JSON description file, as shown in FIG. 4, clicking a ROOT node, and seeing the details of the JSON description file, wherein the JSON description file is formatted, is convenient to read and supports one-key copying.
The foregoing is illustrative of the best mode of carrying out the invention, and is not presented in any detail as is known to those of ordinary skill in the art. The protection scope of the invention is defined by the claims, and any equivalent transformation based on the technical teaching of the invention is also within the protection scope of the invention.
Claims (6)
1. The intelligent agriculture Internet of things equipment description file generation method is characterized by comprising the following steps of:
beginning at S1 and then proceeding to step S2;
step S2: defining a device description specification, normalizing basic description items of the device, and then entering step S3;
step S3, defining a page component, namely processing all data items used in the equipment description specification defined in the step S2, finishing the data items into the page component capable of displaying, dragging and modifying the attribute on the WEB page, and then entering the step S4;
s4, loading a page component and a loading device structure; comprising
Loading all data items used in the equipment description specification and the equipment description specification into a computer memory, initializing, distributing the generated page components in a control selection area in a label mode, and distributing an equipment structure body in a configuration selection area;
the user autonomously selects the loading of the main equipment or the sub equipment or the loading of the sensor according to the requirements and the system hardware configuration, and after the loading is completed, the whole is stored to generate a JSON description file;
the loading of the master device comprises the following steps:
starting at step S101: selecting a main device, clicking control information and configuration information of a configuration selection area, and then entering step S102;
step S102: selecting a page component, dragging a label option for editing the page component of the main equipment to a main working area in a control selection area, and then entering step S103;
step S103: selecting a component attribute, setting the component attribute in an attribute modification area, and then proceeding to step S104;
step S104: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the actual system hardware configuration, if so, jumping to the step S102, otherwise, entering the step S105;
step 105, integrally storing and generating a JSON description file;
the loading of the sub-device comprises the following steps:
starting at step S201: newly adding a piece of sub-equipment, performing point selection on the configuration of the sub-equipment in the configuration selection area, adding the names, the type codes and the number of the sub-equipment, and then entering step 202;
step S202: selecting a page component, clicking configuration information under the configuration of the sub-equipment, dragging label options describing the sub-equipment to a main working area in a control selection area, and then entering step S203;
step S203: setting component attributes, setting component attributes in an attribute modification area and then proceeding to step 204;
step S204: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the actual system hardware configuration, if so, jumping to the step S202, otherwise, entering the step S205;
step S205: judging whether an instruction is needed, if yes, entering a step S206, otherwise, entering a step S105;
step S206: a new instruction is added, control information of the configuration selection area is selected, and then step S207 is carried out;
step S207: the configuration instruction, clicking the control selection area to drag the label options of the editing instruction component to the main working area, editing the attribute in the attribute modification area, and then entering step S208;
step S208: judging whether other instructions exist or not, if so, judging by a user according to the requirements and the system hardware configuration, if so, jumping to a step S206, otherwise, entering a step S105;
step 105, integrally storing and generating a JSON description file;
the loading of the sensor comprises the following steps:
starting at step S301: newly adding a sensor, clicking the sensor configuration of the configuration selection area, and then entering step S302;
step S302: selecting a page component, dragging a label option of the editing sensor component to a main working area in a control selection area, and then entering step S303;
step S303: setting component attributes, setting the component attributes in an attribute modification area, and then entering step 304;
step S304: judging whether other attributes exist or not, if so, judging by a user according to the requirements and the system hardware configuration, if so, jumping to the step S302, otherwise, entering the step S305;
step S305: judging whether an instruction is needed, if yes, entering a step S306, otherwise, entering a step S105;
step S306: a new instruction is added, control information of the configuration selection area is selected, and then step S307 is carried out;
step S307: the configuration instruction, clicking the control selection area to drag the label options of the editing instruction control to the main working area, editing the attribute in the attribute modification area, and then entering step S308;
step S308: judging whether other instructions exist, if yes, jumping to the step S306, otherwise, entering the step S105;
and step 105, integrally storing and generating a JSON description file, clicking a ROOT node, and viewing the details of the JSON description file.
2. The intelligent agriculture internet of things device description file generation method according to claim 1, wherein: the basic description items that all devices have include name-name, type-type, identification code-code, parameter object list-params, instruction object list-cmds, sensor list-sensors, the device contains zero to multiple sub-devices-items, as well as the description items of each sub-device.
3. The intelligent agriculture internet of things device description file generation method of claim 2, wherein: description of parameter object list: the parameter object list-params comprises a parameter name-name, a parameter identification code-key, a parameter type-propertyTYPE, a parameter default value-value, and whether the parameter is editable or not.
4. The intelligent agriculture internet of things device description file generation method of claim 2, wherein: description of instruction object list: the instruction object list-cmds comprises an instruction name-name, a display type-displaypype of an instruction on a platform, an instruction identification code-key and an instruction processor-handlecode.
5. The intelligent agriculture internet of things device description file generation method of claim 2, wherein: the description of the sensor list, wherein the sensor list-sensors comprises a sensor identification code-key, a transmission data type-dataType, an upper data alarm threshold limit-upper limit and a lower data alarm threshold limit-lower limit.
6. The intelligent agriculture internet of things device description file generation method according to claim 1, wherein: the details of the JSON description file are formatted, so that the reading is convenient, and one-key copying is supported.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110133489.XA CN112764637B (en) | 2021-02-01 | 2021-02-01 | Intelligent agriculture Internet of things equipment description file generation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110133489.XA CN112764637B (en) | 2021-02-01 | 2021-02-01 | Intelligent agriculture Internet of things equipment description file generation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112764637A CN112764637A (en) | 2021-05-07 |
| CN112764637B true CN112764637B (en) | 2023-06-20 |
Family
ID=75704250
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110133489.XA Active CN112764637B (en) | 2021-02-01 | 2021-02-01 | Intelligent agriculture Internet of things equipment description file generation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112764637B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113448583A (en) * | 2021-08-27 | 2021-09-28 | 深圳市信润富联数字科技有限公司 | Configuration development method and device based on Internet of things, terminal equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105701183A (en) * | 2016-01-07 | 2016-06-22 | 无锡天脉聚源传媒科技有限公司 | User personalized template implementation method and apparatus |
| CN106412031A (en) * | 2016-09-14 | 2017-02-15 | 深圳市丰巨泰科电子有限公司 | Internet of things device discovering and controlling method |
| CN110929489A (en) * | 2019-11-18 | 2020-03-27 | 有时数联科技（北京）有限公司 | Form generation and form data processing method and system |
| CN111459889A (en) * | 2020-03-08 | 2020-07-28 | 中电海康集团有限公司 | Equipment data model generation method and device for Internet of things platform |
| CN111865634A (en) * | 2019-04-29 | 2020-10-30 | 西门子（中国）有限公司 | Method and device for generating configuration file of site in Internet of things system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8516392B2 (en) * | 2010-08-31 | 2013-08-20 | Daniel Reuven Ostroff | Interactive generic configurator program |
-
2021
- 2021-02-01 CN CN202110133489.XA patent/CN112764637B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105701183A (en) * | 2016-01-07 | 2016-06-22 | 无锡天脉聚源传媒科技有限公司 | User personalized template implementation method and apparatus |
| CN106412031A (en) * | 2016-09-14 | 2017-02-15 | 深圳市丰巨泰科电子有限公司 | Internet of things device discovering and controlling method |
| CN111865634A (en) * | 2019-04-29 | 2020-10-30 | 西门子（中国）有限公司 | Method and device for generating configuration file of site in Internet of things system |
| CN110929489A (en) * | 2019-11-18 | 2020-03-27 | 有时数联科技（北京）有限公司 | Form generation and form data processing method and system |
| CN111459889A (en) * | 2020-03-08 | 2020-07-28 | 中电海康集团有限公司 | Equipment data model generation method and device for Internet of things platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112764637A (en) | 2021-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108351636B (en) | Engineering design tool, system and module | |
| US8776016B2 (en) | Integration of structured profiling data with source data in the eclipse development environment | |
| US9064220B2 (en) | Linear visualization for overview, status display, and navigation along business scenario instances | |
| US20060271908A1 (en) | Method of componentisation of a graphically defined formula | |
| US10705806B1 (en) | Managing an application variable using variable attributes | |
| US20160350079A1 (en) | Method and system of editing workflow logic and screens with a gui tool | |
| US20170192877A1 (en) | Mobile application development and deployment | |
| US20120226967A1 (en) | Spreadsheet-Based Graphical User Interface for Modeling of Products Using the Systems Engineering Process | |
| EP1027647A1 (en) | Method of generating a display for a dynamic simulation model utilizing node and link representations | |
| KR20090120481A (en) | A consistent method system and computer program for developing software asset based solutions | |
| US7752574B2 (en) | System, method and article for displaying data distributions in data trees | |
| US8839186B2 (en) | Entity morphing in metamodel-based tools | |
| US20100287459A1 (en) | Reusable business logic across user interface containers | |
| US20110125667A1 (en) | Process Pattern Automation in Tools for Business Process Modeling | |
| US8972224B2 (en) | Computer systems for data manipulation and related methods | |
| US20100153907A1 (en) | Configurable Unified Modeling Language Building Blocks | |
| US8230319B2 (en) | Web-based visualization, refresh, and consumption of data-linked diagrams | |
| CN112764637B (en) | Intelligent agriculture Internet of things equipment description file generation method | |
| CN113535135B (en) | Software development method and device, computer equipment and storage medium | |
| CN113836877A (en) | Text labeling method, device, equipment and storage medium | |
| KR20150110063A (en) | Apparatus and method of integrating mapreduce for big data processing | |
| CN101710275B (en) | Gui tool is utilized to carry out the method and system of editing stream logic and screens | |
| JP2008003803A (en) | Project management system and its program | |
| CN113138760A (en) | Page generation method and device, electronic equipment and medium | |
| US20030126004A1 (en) | Method and system for a graphical view of selectable work items |
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 |