CN113364636B - Visual configuration docking method for data of Internet of things - Google Patents

Visual configuration docking method for data of Internet of things Download PDF

Info

Publication number
CN113364636B
CN113364636B CN202110905840.2A CN202110905840A CN113364636B CN 113364636 B CN113364636 B CN 113364636B CN 202110905840 A CN202110905840 A CN 202110905840A CN 113364636 B CN113364636 B CN 113364636B
Authority
CN
China
Prior art keywords
result
conversion
request
source data
configuration
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
Application number
CN202110905840.2A
Other languages
Chinese (zh)
Other versions
CN113364636A (en
Inventor
胡自和
黎长江
王洪深
李明海
张东旭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Egova Technology Co ltd
Original Assignee
Beijing Egova Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Egova Technology Co ltd filed Critical Beijing Egova Technology Co ltd
Priority to CN202110905840.2A priority Critical patent/CN113364636B/en
Publication of CN113364636A publication Critical patent/CN113364636A/en
Application granted granted Critical
Publication of CN113364636B publication Critical patent/CN113364636B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16YINFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y30/00IoT infrastructure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0246Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0253Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/561Adding application-functional data or data for application control, e.g. adding metadata

Abstract

The application discloses a visual configuration docking method for data of the Internet of things, which comprises the following steps: configuring operation and storing; triggering and executing the configured operation according to a preset timing task to obtain source data; and converting the source data into an entity to obtain a result array. According to the data mapping method, the http request and the data of the database are acquired in a step-by-step configuration mode by means of a visual interface developed in a matched mode, so that the method for monitoring the data of the Internet of things equipment is achieved, and meanwhile, the communication and development workload in the docking process is effectively reduced.

Description

Visual configuration docking method for data of Internet of things
Technical Field
The application relates to the technical field of computers, in particular to a visual configuration docking method for data of an internet of things.
Background
With the rapid development of the internet of things technology and the popularization of 5G communication, the prices of various internet of things monitoring devices are continuously lowered. Along with the comprehensive expansion of digital city management and city comprehensive management platforms in the whole country, the monitoring and monitoring of industries such as municipal administration, gardens, environmental sanitation and the like by using Internet of things equipment in city management becomes a conventional method, so that various stocks and newly-built Internet of things monitoring data access systems become indispensable links in the implementation process of the city comprehensive management platforms.
In certain industries, such as environmental protection: and the national standard HJ/T212 protocol is used for transmitting environment-friendly monitoring data. The monitoring instrument is connected to an independent data transmission and acquisition instrument through a digital output interface, and the data transmission and acquisition instrument transmits data to a target address. The protocol is based on TCP, and data is organized into messages with a fixed format, analyzed and then stored by a server.
Under the drive of the development of 4G and 5G mobile networks, NB-IOT and MQTT protocols become a mode of data transmission preference of the Internet of things. The NB-IOT protocol is in a physical layer, and the equipment does not need a gateway and can be directly connected with a service provider. The NBIOT is a low-power-consumption and wide-coverage data transmission protocol and has the characteristics of wide coverage, more connections, high speed, low cost, low power consumption and the like. While MQTT is at the application layer, the lightweight structure may enable it to provide reliable messaging services to remote devices using very little code and bandwidth based on a publish/subscribe model.
Whether the relatively general MQTT protocol or the industry-related HJ/T212 protocol, they can be implemented for devices that support the protocol. However, in the actual project implementation process, party a purchases various types of hardware from different manufacturers, and since the city management field relates to a plurality of types of equipment, and the hardware communication modes produced by different hardware parties are different, even if the same protocol is used, a plurality of customized parts exist in the concrete implementation, so that the same protocol is difficult to support the access of all data, and finally, the data access workload is huge. Most hardware parties have own platforms to monitor the internet of things equipment, and meanwhile, an http (hypertext transfer protocol) interface is provided to enable a third party (such as a city integrated management platform) to obtain data for secondary development. Meanwhile, some old systems do not have ready interfaces, and data exchange is generally carried out in a mode of providing a middle library. The http interface is easy to call, but different manufacturer system designs directly result in different formats of interface return data, data of a plurality of manufacturers are accessed on the same project, the data are processed into an agreed unified format, and except that time is consumed in communication, customized development is needed for each manufacturer to realize data access work. Of course, the intermediate library format also suffers from the same problem.
Disclosure of Invention
The method for the visual configuration and the butt joint of the data of the Internet of things is achieved by the data mapping method, the http request and the data of the database are obtained in a step-by-step configuration mode by means of a visual interface developed in a matched mode, and meanwhile communication and development workload in the butt joint process is effectively reduced.
In order to achieve the above object, the present application provides a method for visual configuration docking of data of an internet of things, including: configuring operation and storing; triggering and executing the configured operation according to a preset timing task to obtain source data; and converting the source data into an entity to obtain a result array.
As above, wherein the configuration operation comprises the steps of: configuring basic information; after the basic information configuration is completed, configuring global variables; after the global variable configuration is completed, configuring the newly added steps, judging the step types of the newly added steps needing to be configured, and configuring according to the step types; wherein the step types include: http step and database step; after the configuration of the newly added step is completed, judging whether the newly added step needs to be added or not, and if so, configuring the newly added step again; and if not, configuring the data conversion, and storing the configured operation after the configuration is finished.
As above, when the step types of the new steps are: and in the http step, setting an http parameter, and configuring according to the step type, wherein the step is as follows: setting an http request, wherein the setting of the http request comprises: setting an http parameter, setting an http request header and setting step parameters; judging whether paging is needed, and if so, performing paging configuration; if not, the configuration is output.
As above, when the step types of the new steps are: database step, connecting configuration, the configuration step according to step type is as follows: configuring a structured query statement request; and outputting the configuration after the request of the structured query statement is completed.
As above, wherein the configured operation is triggered and executed according to the preset timing task, the substep of obtaining the source data is as follows: triggering operation and execution according to a preset timing task, and initializing a global variable; after the global variable initialization is completed, acquiring operation step information; traversing the operation, judging the step type, executing the operation according to the step information and the step type, obtaining an output result, and storing the output result as source data; judging whether traversal is finished, if so, finishing operation; if not, the operation steps are traversed again.
As above, when the step type is the http step, the step is traversed, the step type is determined, the operation is executed according to the step information and the step type, the output result is obtained, and the sub-step of storing the output result as the source data is as follows: constructing request parameters; constructing a request head; constructing a request, wherein the constructed request comprises: a request method, a request address, a request parameter and a request header; judging whether paging is needed, if so, setting paging parameters according to the step information, and executing the constructed request after the paging parameters are set; and if not, executing the constructed request, and acquiring and storing the output result.
As above, when the step type is a database step, the substeps of traversing the step, determining the step type, performing an operation according to the step information and the step type, obtaining an output result, and storing the output result as source data are as follows: acquiring a database configuration; and establishing connection with a database, operating a structured query statement according to the step information to obtain an output result, and storing the output result as source data.
As above, wherein for source data conversion into entities, the sub-steps of obtaining the result array are as follows: initializing conversion meta information; initializing target meta information; initializing a result array; and traversing the source data, converting the source data by using the conversion meta information and the target meta information to obtain a conversion result, and storing the conversion result into the initialization result array to obtain a result array.
As above, the sub-steps of traversing the source data, transforming the source data by using the transformation meta-information and the target meta-information, obtaining the transformation result, and storing the transformation result in the initialized result array, and obtaining the result array are as follows: s13041: traversing the source data, judging whether the traversal is finished, and if the traversal is finished, executing S13042; if the traversal is not finished, executing S13043; s13042: judging whether sub-conversion is needed, if so, outputting a field value, saving a conversion result, and judging whether traversal is finished again; if not, saving the result array; s13043: initializing a result, acquiring a field value, judging whether the field value is an array, and if so, executing S13041; if not, outputting the field value, saving the conversion result, and judging whether the traversal is finished or not again; s13044: and saving the conversion result to obtain a result array.
As above, the conversion fault detection is performed on the conversion result to generate a detection result, if the detection result is that the conversion is damaged, the source data is traversed again, and the source data is converted by using the conversion meta information and the target meta information to obtain a conversion result; if the detection result is that the conversion is complete, the conversion result is saved.
According to the data mapping method, the http request and the data of the database are acquired in a step-by-step configuration mode by means of a visual interface developed in a matched mode, so that the method for monitoring the data of the Internet of things equipment is achieved, and meanwhile, the communication and development workload in the docking process is effectively reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a flow chart of an embodiment of a method for visual configuration docking of data of the Internet of things;
FIG. 2 is a flow diagram of one embodiment of a configuration operation;
FIG. 3 is a flow diagram of one embodiment of performing operations;
FIG. 4 is a flow diagram of one embodiment of a conversion entity.
Detailed Description
The technical solutions in the embodiments of the present invention are clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, the application provides a method for visual configuration docking of data of an internet of things, which includes the following steps:
s110: configuring operation and saving.
Further, as shown in fig. 2, the configuration operation includes the following steps:
s1101: and configuring basic information.
Specifically, a cron (scheduled task) expression is set, and after the setting is finished, the operation can be automatically triggered and executed according to a preset timing task; if not, the operation cannot be automatically triggered and executed according to the preset timing task.
S1102: and after the basic information configuration is completed, configuring the global variable.
Specifically, the global variable is used to configure the constant, and includes predefined values of a plurality of parameters, and when a parameter is marked as using the global variable, the predefined value corresponding to the parameter can be read from the global variable.
S1103: after the global variable configuration is completed, configuring the newly added steps, judging the step types of the newly added steps needing to be configured, and configuring according to the step types; wherein the step types include: http step and database step.
Further, when the step types of the new adding step are: and in the http step, setting an http parameter, and configuring according to the step type, wherein the step is as follows:
s11031: setting an http request, wherein the setting of the http request comprises: setting http parameters, setting http request headers and setting step parameters.
Specifically, the substep of setting the http request is as follows:
t1: setting an http parameter, wherein the http parameter comprises: name, value, and des.
Specifically, name is a parameter name, value is a parameter value, des is a parameter description, and if the http parameter is marked as using a global variable, a predefined value corresponding to the http parameter is obtained from the global variable through the value. And if the http parameter is not a global variable, directly reading the value of the value.
T2: setting an http request header, wherein the http request header comprises: name, value, and des.
Specifically, name is a parameter name, value is a parameter value, des is a parameter description, and if the parameter is marked as using a global variable, a predefined value corresponding to the parameter is acquired from the global variable through the value; if the parameter is not a global variable, the value is read directly.
The http message structure comprises a request method, a request address, a protocol version, an http request header and request data. And the http request header and the http parameter are positioned at different positions of the message.
T3: setting step parameters, wherein the step parameters comprise: and configuring the address of the http request and a request method.
Specifically, the request method includes: GET (requests data from a specified resource) and POST (submits data to be processed to a specified resource), the request method is an integral part of the http message.
S11032: judging whether paging is needed, and if so, performing paging configuration; if not, the configuration is output.
Specifically, whether paging is needed or not is judged, if yes, paging configuration is performed, and if yes, device paging parameters are configured. If not, the configuration is output.
Because the data volume is large, part of http requests are paged when data is returned, so that page numbers and paging sizes need to be transmitted to acquire the data in several times, and the configured device paging parameters comprise: a page number parameter name, a page size parameter name, and a page size.
Wherein, setting the field name of the output result: target _ param _ name; and outputting the configuration according to the set output result field name.
Further, when the step types of the new adding step are: database step, connecting configuration, the configuration step according to step type is as follows:
s11031': configure SQL (structured query statement) requests.
T1': setting SQL configuration, including: the jdbc (java data connection) data source address, username and password are configured.
T2': and configuring the SQL statement.
Specifically, the configuration method of the SQL statement is as follows: directly inputting the data in the input box, and acquiring the data from the source database by using a select format.
S11032': and outputting the configuration after the SQL request configuration is completed.
Specifically, the output result field name is set: target _ param _ name; and outputting the configuration according to the set output result field name.
S1104: after the configuration of the new step is completed, judging whether the new step needs to be added, if so, executing S1103; if not, S1105 is executed.
Specifically, after the configuration is output, whether a new step needs to be added is judged, if the new step needs to be added, the new step is executed again, and the step type of the new step is judged; if no addition is required, the data conversion is configured.
S1105: and configuring the data conversion, and storing the configured operation after the configuration is completed.
Further, configuring the data conversion includes the following steps:
u1: a translation data source is configured.
Specifically, the configured conversion data source is: source _ param _ name.
U2: the conversion entity is configured.
Specifically, the configuration conversion entity is a format of a predefined target object.
U3: configuring a conversion field, wherein the conversion field comprises: source field name, destination field name, field type, field value format, and from _ global, which means: whether it is a global variable.
Specifically, the source field name: source _ param _ name; target field name: target _ param _ name; the field type: value _ type; field value format: and (5) format. Since each configuration does not have a global variable, and the determination needs to be made according to the actual situation, it needs to determine whether the conversion field is from a global variable (from _ global), if true, obtain a corresponding value from the global variable through a source field name (source _ param _ name), and if not true, directly obtain data from the conversion source according to the source field name (source _ param _ name).
S120: and triggering and executing the configured operation according to a preset timing task to obtain source data.
Specifically, as shown in fig. 3, the configured operation is triggered and executed according to a preset timing task, and the substeps of obtaining source data are as follows:
s1201: triggering operation and execution according to a preset timing task, and initializing a global variable (globalParam).
Specifically, the global variable is read from the database, the global variable is stored as a json object in a key-value (key value) form, initialization is completed, and when the initialized global variable needs to be used, a specific value corresponding to the key is matched through a variable name. Json is a lightweight data storage format independent of development language.
S1202: and after the global variable initialization is completed, acquiring the step information of the operation.
Specifically, the step information refers to information of a step of an operation to be performed. Reading step information from a database, wherein the step information comprises a database connection address, a user name, a password and an SQL statement if the step is a database step; if the http step is performed, the step information includes a request address, a request method, a request parameter, a request header, and a paging parameter.
S1203: and traversing operation steps (steps), judging step types, executing operation according to step information and step types, obtaining output results, and storing the output results as source data.
Specifically, a complete operation is composed of one or more steps, and a traversal step is a step of the traversal operation, and the purpose is to obtain data by using http or sql.
Further, when the step type is an http step, traversing the steps (steps), judging the step type, executing operation according to the step information and the step type, obtaining an output result, and storing the output result as source data, wherein the substep is as follows:
s12031: request parameters (params) are constructed.
S12032: request headers (headers) are constructed.
S12033: constructing a request, wherein the constructed request comprises: request method, request address (url), request parameters, and request header.
S12034: judging whether paging is needed, if so, setting paging parameters according to the step information, and executing the constructed request after the paging parameters are set; and if not, executing the constructed request, and acquiring and storing the output result.
Specifically, the page number and the page size are configured in the request parameter. And executing the request (the paging request is executed circularly according to the paging parameters) to obtain an output result, and storing the output result serving as source data into the globalParam according to the output field (target _ param _ name).
Further, when the step type is a database step, the step (steps) is traversed, the step type is judged, operation is executed according to the step information and the step type, an output result is obtained, and the substep of storing the output result as source data is as follows:
s12031': a database configuration is obtained.
Specifically, obtaining the configuration from the database includes: a connection address, a username, and a password.
S12032': and establishing connection with a database, operating the SQL statement according to the step information to obtain an output result, and storing the output result as source data.
Specifically, the operation of the SQL statement requires that a connection is established with the database through a connection address, a user name and a password, and then a driver is matched, the SQL statement can be executed, an output result is obtained, and the output result is stored into globalParam as source data according to an output field (target _ param _ name).
S1204: judging whether traversal is finished, if so, finishing operation; if not, S1203 is executed.
S130: and converting the source data into an entity to obtain a result array.
Further, as shown in fig. 4, for the source data converted into the entity, the sub-steps of obtaining the result array are as follows:
s1301: the conversion meta information (cMeta) is initialized.
Specifically, conversion meta-information is initialized, and the conversion meta-information is used for providing field relationships between data to be acquired and entities for operation steps to be performed.
S1302: target meta information (tMeta) is initialized.
Specifically, target meta information is initialized, the target meta information is predefined, and the target meta information: the method comprises the following steps: the field name and the field type are used for storing the field information of the entity.
S1303: the result array is initialized.
Specifically, a null array is created and used as an initialization result array for storing an entity obtained after the source data conversion.
S1304: and traversing the source data, converting the source data by using the conversion meta information and the target meta information to obtain a conversion result, and storing the conversion result into the initialization result array to obtain a result array.
Specifically, the conversion result is an entity of the source data obtained by converting the source data.
Furthermore, traversing the source data, converting the source data by using the conversion meta information and the target meta information to obtain a conversion result, and storing the conversion result into the initialized result array, wherein the substep of obtaining the result array is as follows:
s13041: traversing the source data, judging whether the traversal is finished, and if the traversal is finished, executing S13042; if the traversal is not finished, S13043 is performed.
S13042: judging whether sub-conversion is needed, if so, outputting a field value, saving a conversion result, and judging whether traversal is finished again; if not, the result array is saved.
Specifically, if the obtained field value is an array, sub-conversion is required to be performed for conversion of a complex object whose field value of the target object is an array, the conversion result is also an array, and the conversion result is not stored in the result array, but is stored in the result object. The result array is the data which needs to be saved finally.
S13043: initializing a result, acquiring a field value, judging whether the field value is an array, and if so, executing S13041; if not, outputting the field value, saving the conversion result, and judging whether the traversal is finished or not again.
Specifically, the result is initialized (the result is a common object, the array is a carrier for storing the result, and a plurality of results are put into the data to form a result array), and the result acquires a corresponding value from the source according to source _ param _ name in the cMeta (conversion meta information), and if from _ global is a global variable, acquires the value from the global variable globalparam. If the data is an array, the data is used as source data, a sub-conversion is executed once, and then the result of the sub-conversion is saved in a corresponding field of the conversion result. And acquiring a target data type from the tMeta according to the target _ field _ name in the cMeta, converting the target data type into a corresponding type by using a value, and acquiring a conversion result after the conversion is finished.
Further, performing conversion fault detection on the conversion result to generate a detection result, if the detection result is conversion damage, traversing the source data again, and converting the source data by using the conversion meta information and the target meta information to obtain a conversion result; if the detection result is that the conversion is complete, the conversion result is saved.
Further, the conversion fault detection is performed on the conversion result through a preset conversion fault detection model, wherein an expression of the conversion fault detection model is as follows:
Figure 165066DEST_PATH_IMAGE001
wherein the content of the first and second substances,
Figure 114830DEST_PATH_IMAGE002
the average value of the difference values of the feature distribution rates of the source data and the conversion result;
Figure 628988DEST_PATH_IMAGE003
is the first in the source data
Figure 820935DEST_PATH_IMAGE004
A value of a distribution rate of the data features;
Figure 369728DEST_PATH_IMAGE005
is the first of the conversion results
Figure 988928DEST_PATH_IMAGE004
The number of distribution rates of the data features,
Figure 990382DEST_PATH_IMAGE006
Figure 986020DEST_PATH_IMAGE007
the total number of the data features in the conversion result;
Figure 389319DEST_PATH_IMAGE008
is a proportionality coefficient;
Figure 179421DEST_PATH_IMAGE009
is as follows
Figure 668171DEST_PATH_IMAGE004
The characteristic value of the data characteristic is calculated,
Figure 201920DEST_PATH_IMAGE010
when in use
Figure 459726DEST_PATH_IMAGE002
If the difference is larger than the preset allowable difference, the junction is detectedThe fruit is damaged by conversion; when in use
Figure 686308DEST_PATH_IMAGE002
If the difference is smaller than or equal to the preset allowable difference, the detection result is that the conversion is complete.
S13044: and saving the conversion result to obtain a result array.
Specifically, the conversion result is stored in the result according to the target _ field _ name, the result is stored in the initial result array, and the result array is obtained after the storage is completed.
According to the method for visually configuring and docking the data of the Internet of things, the http request and the data of the database are acquired in a step-by-step configuration mode by means of the provided data mapping method and with the help of the visual interface developed in a matched mode, so that the method for monitoring the data of the Internet of things equipment is achieved, and meanwhile, the communication and development workload in the docking process is effectively reduced.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, the scope of protection of the present application is intended to be interpreted to include the preferred embodiments and all variations and modifications that fall within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (1)

1. A method for visual configuration docking of data of an Internet of things is characterized by comprising the following steps:
configuring operation and storing;
triggering and executing the configured operation according to a preset timing task to obtain source data;
converting source data into an entity to obtain a result array;
wherein the configuration operation comprises the steps of:
configuring basic information;
after the basic information configuration is completed, configuring global variables;
after the global variable configuration is completed, configuring the newly added steps, judging the step types of the newly added steps needing to be configured, and configuring according to the step types; wherein the step types include: http step and database step;
after the configuration of the newly added step is completed, judging whether the newly added step needs to be added or not, and if so, configuring the newly added step again; if not, configuring the data conversion, and storing the configured operation after the configuration is completed;
wherein, when the step types of the newly added step are: and in the http step, setting an http parameter, and configuring according to the step type, wherein the step is as follows:
setting an http request, wherein the setting of the http request comprises: setting an http parameter, setting an http request header and setting step parameters;
judging whether paging is needed, and if so, performing paging configuration; if not, outputting the configuration;
wherein, when the step types of the newly added step are: database step, connecting configuration, the configuration step according to step type is as follows:
configuring a structured query statement request;
outputting configuration after the request of the structured query statement is completed;
the method comprises the following steps of triggering and executing configured operation according to a preset timing task, and obtaining source data as follows:
triggering operation and execution according to a preset timing task, and initializing a global variable;
after the global variable initialization is completed, acquiring operation step information;
traversing the operation, judging the step type, executing the operation according to the step information and the step type, obtaining an output result, and storing the output result as source data;
judging whether traversal is finished, if so, finishing operation; if not, the operation is traversed again;
when the step type is an http step, traversing the step, judging the step type, executing operation according to the step information and the step type to obtain an output result, and storing the output result as source data, wherein the substep is as follows:
constructing request parameters;
constructing a request head;
constructing a request, wherein the constructed request comprises: a request method, a request address, a request parameter and a request header;
judging whether paging is needed, if so, setting paging parameters according to the step information, and executing the constructed request after the paging parameters are set; if not, executing the constructed request, and acquiring and storing an output result;
wherein, when the step type is a database step, traversing the step, judging the step type, executing operation according to the step information and the step type, obtaining an output result, and storing the output result as source data, wherein the substeps are as follows:
acquiring a database configuration;
establishing connection with a database, operating a structured query statement according to the step information to obtain an output result, and storing the output result as source data;
the substep of converting the source data into the entity and obtaining the result array is as follows:
initializing conversion meta information;
initializing target meta information;
initializing a result array;
traversing source data, converting the source data by using the conversion meta information and the target meta information to obtain a conversion result, and storing the conversion result into an initialization result array to obtain a result array;
the method comprises the following steps of traversing source data, converting the source data by using conversion meta information and target meta information to obtain a conversion result, storing the conversion result into an initialization result array, and obtaining the result array according to the following substeps:
s13041: traversing the source data, judging whether the traversal is finished, and if the traversal is finished, executing S13042; if the traversal is not finished, executing S13043;
s13042: judging whether sub-conversion is needed, if so, outputting a field value, saving a conversion result, and judging whether traversal is finished again; if not, saving the result array;
s13043: initializing a result, acquiring a field value, judging whether the field value is an array, and if so, executing S13041; if not, outputting the field value, saving the conversion result, and judging whether the traversal is finished or not again;
s13044: storing the conversion result to obtain a result array;
performing conversion fault detection on a conversion result to generate a detection result, traversing source data again if the detection result is conversion damage, and converting the source data by using conversion meta information and target meta information to obtain a conversion result; if the detection result is that the conversion is complete, the conversion result is saved.
CN202110905840.2A 2021-08-09 2021-08-09 Visual configuration docking method for data of Internet of things Active CN113364636B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110905840.2A CN113364636B (en) 2021-08-09 2021-08-09 Visual configuration docking method for data of Internet of things

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110905840.2A CN113364636B (en) 2021-08-09 2021-08-09 Visual configuration docking method for data of Internet of things

Publications (2)

Publication Number Publication Date
CN113364636A CN113364636A (en) 2021-09-07
CN113364636B true CN113364636B (en) 2021-11-02

Family

ID=77540741

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110905840.2A Active CN113364636B (en) 2021-08-09 2021-08-09 Visual configuration docking method for data of Internet of things

Country Status (1)

Country Link
CN (1) CN113364636B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110661820A (en) * 2019-12-02 2020-01-07 武汉慧联无限科技有限公司 Internet of things data processing method and device, equipment and storage medium
CN111818184A (en) * 2020-08-31 2020-10-23 创业慧康科技股份有限公司 Medical Internet of things message routing device and method based on visual convenient flow calculation
CN112714193A (en) * 2021-03-26 2021-04-27 深圳佳兆业科技集团有限公司 Community data processing system, method, device and equipment based on Internet of things platform
CN112866191A (en) * 2020-12-28 2021-05-28 武汉虹信科技发展有限责任公司 OT and IT integrated system based on 5G DTU system
CN113110206A (en) * 2021-04-28 2021-07-13 南京奥拓电子科技有限公司 Internet of things control system and equipment control method for bank outlets

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10831565B2 (en) * 2017-09-28 2020-11-10 Sap Se Fault tolerant adapter system to consume database as a service

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110661820A (en) * 2019-12-02 2020-01-07 武汉慧联无限科技有限公司 Internet of things data processing method and device, equipment and storage medium
CN111818184A (en) * 2020-08-31 2020-10-23 创业慧康科技股份有限公司 Medical Internet of things message routing device and method based on visual convenient flow calculation
CN112866191A (en) * 2020-12-28 2021-05-28 武汉虹信科技发展有限责任公司 OT and IT integrated system based on 5G DTU system
CN112714193A (en) * 2021-03-26 2021-04-27 深圳佳兆业科技集团有限公司 Community data processing system, method, device and equipment based on Internet of things platform
CN113110206A (en) * 2021-04-28 2021-07-13 南京奥拓电子科技有限公司 Internet of things control system and equipment control method for bank outlets

Also Published As

Publication number Publication date
CN113364636A (en) 2021-09-07

Similar Documents

Publication Publication Date Title
US11740950B2 (en) Application program interface analyzer for a universal interaction platform
US9128979B2 (en) Enriching database query responses using data from external data sources
CN102395950B (en) With the communication of data-storage system
AU2021212135A1 (en) Building and managing data-processing attributes for modelled data sources
WO2017156916A1 (en) Data access method and device
AU2012271083A1 (en) Enriching database query responses using data from external data sources
US10135764B2 (en) Universal interaction platform for people, services, and devices
EP1766824A2 (en) System and method for extending business systems to a mobile workforce
CN102567026B (en) Mobile solution constructing system and Mobile solution construction method
US20100121923A1 (en) Multi-tenancy engine
CN111556158A (en) Access method, access device, access equipment and storage medium of Internet of things platform
CN109241384A (en) A kind of method for visualizing and device of scientific research information
US10313421B2 (en) Providing Odata service based on service operation execution flow
CN110633959A (en) Method, device, equipment and medium for creating approval task based on graph structure
CN102833015B (en) Method for determining public software interface of satellite automatic testing system
CN111522840B (en) Label configuration method, device, equipment and computer readable storage medium
CN113364636B (en) Visual configuration docking method for data of Internet of things
CN113111109A (en) Interface warehousing analysis access method of data source
CN115333943B (en) Deterministic network resource allocation system, method, device and storage medium
CN115118794A (en) Data standardization processing method and device and electronic equipment
WO2019061346A1 (en) Resource integration processing method and apparatus, and storage medium
CN112130817A (en) Multi-version interface implementation method, system, device and readable storage medium
US20130031116A1 (en) Modeled business object data import
CN111062682B (en) Work order processing method and device
CN116028563A (en) OPC UA-based data asset management method, device, equipment and storage medium

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