CN112286530A - JavaScript-based Internet of things equipment data format conversion system and method - Google Patents
JavaScript-based Internet of things equipment data format conversion system and method Download PDFInfo
- Publication number
- CN112286530A CN112286530A CN202011265525.XA CN202011265525A CN112286530A CN 112286530 A CN112286530 A CN 112286530A CN 202011265525 A CN202011265525 A CN 202011265525A CN 112286530 A CN112286530 A CN 112286530A
- Authority
- CN
- China
- Prior art keywords
- script
- data
- module
- current
- simulation
- 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
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 29
- 238000000034 method Methods 0.000 title claims abstract description 17
- 238000004088 simulation Methods 0.000 claims abstract description 81
- 244000035744 Hura crepitans Species 0.000 claims abstract description 16
- 238000007781 pre-processing Methods 0.000 claims description 8
- 230000003993 interaction Effects 0.000 abstract description 3
- 230000002085 persistent effect Effects 0.000 abstract description 2
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- QVFWZNCVPCJQOP-UHFFFAOYSA-N chloralodol Chemical compound CC(O)(C)CC(C)OC(O)C(Cl)(Cl)Cl QVFWZNCVPCJQOP-UHFFFAOYSA-N 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a JavaScript-based data format conversion system of an Internet of things device, which belongs to a data format conversion method of the Internet of things device.A user writes a JS script and simulation data aiming at a class of devices through a browser, and the JS script calls a core service to carry out persistent storage after the JS script passes through execution in a sandbox through a JS engine by using the simulation data; if the JS script which does not pass is executed, only the draft state can be stored; the converter loads the JS script (formal) and the device identification. The device side accesses the system through the protocol gateway, and the protocol gateway performs data conversion through the converter to complete interaction.
Description
Technical Field
The invention relates to a data format conversion method for equipment of the Internet of things, in particular to a data format conversion system for the equipment of the Internet of things based on JavaScript.
Background
With the rise of the application of the internet of things, various sensing devices emerge endlessly. Due to different usage scenarios, access networks and protocols are different, such as NB-IoT, LoRa, Wi-Fi and 4G, which are most commonly used. Common internet of things application layer protocols generally include MQTT, HTTP, XMPP, CoAP, and the like, where MQTT is more commonly used. For the MQTT protocol, different device data formats are different, such as JSON, binary, and the like. The current method is hard code conversion, and different equipment data formats write a set of code logic to process; during the demand phase, the class of devices and the associated protocols and data formats must be determined, at least prior to encoding. If the system is deployed, in operation: if the device is changed or the device version upgrade data format is adjusted to some extent, the interaction between the device and the system will fail: for example, data cannot be correctly parsed or even lost, the solution must be re-encoded, upgraded, and re-deployed to solve the problem. Therefore, the workload of the docking equipment is very large, the expansibility is poor, and in order to solve the problem that different codes are required to be written for realizing different data formats of the same protocol, the application procedures are more, the efficiency is low, and research and improvement are needed to be performed on the problems.
Disclosure of Invention
One of the purposes of the present invention is to solve the above-mentioned deficiencies, and provide a data format conversion system for internet of things devices based on JavaScript, so as to solve the technical problems in the prior art that different data formats of the same protocol need to be written with different codes, which results in multiple application procedures and low efficiency.
In order to solve the technical problems, the invention adopts the following technical scheme:
the invention provides a JavaScript-based Internet of things equipment data format conversion system on one hand, which comprises the following components:
the simulation service module is used for receiving the JS script of the user side and verifying and judging the current JS script, if the judgment result is yes, the core service module is called to store the current JS script as a draft, otherwise, a prompt is returned to the user side; the simulation service module is also used for receiving simulation data after the current JS script is stored as a draft, and transmitting the current JS script and the simulation data to the script engine module as parameters;
the script engine module is used for preprocessing the simulation data and the JS script and then executing the current JS script and the simulation data in the sandbox module; the script engine module is also used for acquiring the execution result of the current JS script and the simulation data and feeding the execution result back to the simulation service module;
the simulation service module is used for calling the core service module to modify the state of the current JS script into a formal state when a result of successful execution is obtained, and returning the result to the user side; otherwise, directly feeding back the result of execution failure to the user side;
the core service module is used for transmitting the JS script modified into the formal state to the converter module;
the converter module is used for searching a corresponding JS script in the JS script pool for replacement according to the equipment identifier in the JS script after receiving the JS script in the formal state, and otherwise, newly adding a JS script; waiting to accept data on the device side.
Preferably, the further technical scheme is as follows: and the converter module receives data of the equipment side through the protocol gateway.
The further technical scheme is as follows: the converter module is also used for receiving data of the equipment side, searching the JS script corresponding to the data in the JS script pool according to the equipment identification in the data, and then transmitting the current JS script and the data of the equipment side to the script engine module as parameters; after the script engine module preprocesses the current JS script and the data on the equipment side, the current JS script is executed in the sandbox module, and an execution result is obtained and fed back to the converter; the converter module is used for transmitting the current execution result to the core service module; the core module is used for feeding back the execution result to the current equipment.
Further technical aspects can be: before preprocessing the analog data and the JS script, the script engine module firstly acquires the started JS service, and if the JS service is not started, a JS service is additionally started.
Further technical aspects can be: : and after feeding back the result of the failed execution to the user side, the simulation service module receives the modified simulation data again until the result of the successful execution is obtained.
The invention also provides a JavaScript-based data format conversion method for the Internet of things equipment, which comprises the following steps:
step A, the simulation service module receives a JS script of a user side, checks and judges the current JS script, if the judgment result is yes, the core service module is called to store the current JS script as a draft, otherwise, a prompt is returned to the user side;
b, after the current JS script is stored as a draft, the simulation service module receives simulation data and transmits the current JS script and the simulation data as parameters to the script engine module;
step C, the script engine module preprocesses the simulation data and the JS script, and then the current JS script and the simulation data are executed in the sandbox module;
d, the script engine module acquires the execution result of the current JS script and the simulation data and feeds the execution result back to the simulation service module;
step E, when the simulation service module obtains a result of successful execution, the simulation service module calls a core service module to modify the state of the current JS script into a formal state, and returns the result to the user side; otherwise, directly feeding back the result of execution failure to the user side;
step F, the core service module transmits the JS script modified into the formal state to the converter module;
step G, after the converter module receives the JS script in the formal state, finding out a corresponding JS script in the JS script pool for replacement according to the equipment identification in the JS script, and otherwise, newly adding a JS script; waiting to accept data on the device side.
The further technical scheme is as follows: the method further comprises the following steps:
step H, the converter module receives data of the equipment side, a JS script corresponding to the data is searched in the JS script pool according to the equipment identification in the data, and then the current JS script and the data of the equipment side are used as parameters to be transmitted to the script engine module;
step I, after the script engine module preprocesses the current JS script and the data on the equipment side, executing the current JS script in the sandbox module, and obtaining an execution result and feeding the execution result back to the converter;
step J, the converter module is used for transmitting the current execution result to the core service module;
and K, the core module is used for feeding back the execution result to the current equipment.
Preferably, the further technical scheme is as follows: in the step C, before the simulation data and the JS script are preprocessed, the script engine module firstly acquires the started JS service, and if the JS service is not started, a JS service is additionally started.
The further technical scheme is as follows: in the step E, after the simulation service module feeds back the result of the execution failure to the user side, the step B and the step C are repeated, and the modified simulation data is received again until the result of the execution success is obtained.
Compared with the prior art, the invention has the following beneficial effects:
aiming at the same protocol, conversion of different data formats is realized by executing the JS script, and an editable entry is provided for changing the JS script so as to achieve expandability and real-time updating. And the simulator mode is provided, so that the user can input simulation data to verify the correctness of the JS script, and the debugging complexity and difficulty are reduced. The converter saves loading time and improves conversion performance by caching the JS script in the memory. Meanwhile, the data format conversion system of the Internet of things equipment is realized based on mature JavaScript, is suitable for performing format conversion on data of various Internet of things sensing layer equipment, and has a wide application range.
Drawings
FIG. 1 is a block diagram of a system architecture for illustrating one embodiment of the invention;
FIG. 2 is a system flow diagram illustrating one embodiment of the invention.
Detailed Description
The invention is further elucidated with reference to the drawing.
One embodiment of the invention is a JavaScript-based Internet of things equipment data format conversion system, which comprises a core service module, an analog service module, a script engine module, a converter module and a sandbox module, wherein the relation of the modules is shown in figure 1, and the following JS script is the JavaScript script. As shown in conjunction with fig. 2, wherein:
the simulation service module is used for receiving the JS script of the user side and verifying and judging the current JS script, if the judgment result is yes, the core service module is called to store the current JS script as a draft, otherwise, a prompt is returned to the user side; the simulation service module is also used for receiving simulation data after the current JS script is stored as a draft, and transmitting the current JS script and the simulation data to the script engine module as parameters;
the script engine module is used for preprocessing the simulation data and the JS script and then executing the current JS script and the simulation data in the sandbox module; the script engine module is also used for acquiring the execution result of the current JS script and the simulation data and feeding the execution result back to the simulation service module; preferably, before preprocessing the analog data and the JS script, the script engine module first acquires the started JS service, and if the JS service is not started, another JS service is started;
in addition, the simulation service module is used for calling the core service module to modify the state of the current JS script into a formal state when a result of successful execution is obtained, and returning the result to the user side; otherwise, directly feeding back the result of execution failure to the user side; preferably, after the simulation service module feeds back the result of the execution failure to the user side, the simulation service module receives the modified simulation data again until the result of the execution success is obtained;
the core service module is used for transmitting the JS script modified into the formal state to the converter module;
the converter module is used for searching a corresponding JS script in the JS script pool for replacement according to the equipment identifier in the JS script after receiving the JS script in the formal state, and otherwise, newly adding a JS script; waiting to accept data on the device side.
In this embodiment, the device in the sensing layer of the internet of things can access the system through the protocol gateway, and on the basis, the converter module is further configured to receive data on the device side through the protocol gateway, search for a JS script corresponding to the JS script in the JS script pool according to a device identifier in the data, and transmit the current JS script and the data on the device side to the script engine module as parameters;
after the script engine module preprocesses the current JS script and the data on the equipment side, the current JS script is executed in the sandbox module, and an execution result is obtained and fed back to the converter; the converter module is used for transmitting the current execution result to the core service module; the core module is used for feeding back the execution result to the current equipment.
Based on the above embodiments, in the system provided by the present invention, for the same protocol, conversion of different data formats is realized by executing the JS script, and an editable entry is provided to change the JS script so as to achieve scalability and real-time update. Meanwhile, a simulator mode is provided, so that the user can input simulation data to verify the correctness of the JS script, and the debugging complexity and difficulty are reduced. The converter saves loading time and improves conversion performance by caching the JS script in the memory.
In the embodiment, a user writes a JS script and simulation data aiming at one type of equipment through a browser, and after the JS script passes through a sandbox by using the simulation data through a JS engine, a core service is called for persistent storage; if the JS script which does not pass is executed, only the draft state can be stored; the converter loads the JS script (formal) and the device identification. The device side accesses the system through the protocol gateway, and the protocol gateway performs data conversion through the converter to complete the interaction, and the flow is shown in fig. 2.
Similar to the above embodiment, the system based on the above functions of the present invention further provides a method corresponding to the system, that is, a JavaScript-based internet of things device data format conversion method, where the method includes and preferably is executed according to the following steps:
step S1, the simulation service module receives the JS script at the user end and checks and judges the current JS script, if the judgment result is yes, the core service module is called to store the current JS script as a draft, otherwise, a prompt is returned to the user end;
step S2, after the current JS script is stored as a draft, the simulation service module receives simulation data, and transmits the current JS script and the simulation data as parameters to the script engine module;
step S3, the script engine module preprocesses the simulation data and the JS script, and then executes the current JS script and the simulation data in the sandbox module; in the step, before preprocessing the analog data and the JS script, the script engine module firstly acquires the started JS service, and if the JS service is not started, a JS service is additionally started;
step S4, the script engine module acquires the current JS script and the execution result of the simulation data and feeds the current JS script and the execution result back to the simulation service module;
step S5, when the simulation service module obtains the result of successful execution, the simulation service module calls the core service module to modify the state of the current JS script into formal state, and returns the result to the user side; otherwise, directly feeding back the result of execution failure to the user side; in this step, after the simulation service module feeds back the result of the execution failure to the user side, the step B and the step C are repeated, and the modified simulation data is received again until the result of the execution success is obtained.
Step S6, the core service module transmits the JS script modified into the formal state to the converter module;
step S7, after the converter module receives the JS script in the formal state, finding out a corresponding JS script in the JS script pool for replacement according to the equipment identification in the JS script, and otherwise, adding a new JS script; waiting for receiving data of the equipment side;
in this embodiment, the following steps are continuously performed:
step S8, the converter module receives data of the equipment side, a JS script corresponding to the data is searched in the JS script pool according to the equipment identification in the data, and then the current JS script and the data of the equipment side are used as parameters to be transmitted to the script engine module;
step S9, after the script engine module preprocesses the current JS script and the data on the equipment side, the current JS script is executed in the sandbox module, and the execution result is obtained and fed back to the converter;
step S10, the converter module is configured to transmit the current execution result to the core service module;
and step S11, the core module is used for feeding back the execution result to the current equipment.
In practical use, the above preferred embodiment of the present invention generally operates as follows:
1) and the user writes the JS script and stores the simulation data in a specified directory through a text editor or other JS file editors.
2) And loading and executing the stored JS script and simulation data by manually calling the trigger script engine module, and displaying an execution result.
3) If the execution result of the step 2) does not pass, modifying the JS script and the simulation data; continuing the step 2).
4) And if the execution result of the step 2) is that the JS script is marked as formal.
5) And the core service module loads the formal JS script into the memory and transmits the formal JS script to the converter for updating.
6) After the converter receives the JS script, searching a corresponding JS script in the JS pool according to the equipment identifier; if found, replace it; if not, a new strip is added.
7) The equipment accesses the system through the protocol gateway, and transmits the data reported by the equipment side to the converter.
8) And the converter calls a script engine and takes the JS script and the data transmitted by the protocol gateway as parameters to be transmitted.
9) And the script engine module preprocesses the JS script and the equipment reported data and then executes the JS script on the sandbox module.
10) And the script engine module acquires the execution result of the JS service and returns the result to the converter.
11) After the converter module takes the execution result, the data is transmitted to the core service; and returning the execution result to the protocol gateway.
12) And the protocol gateway returns the result to the equipment of the sensing layer of the Internet of things.
In addition to the foregoing, it should be noted that reference throughout this specification to "one embodiment," "another embodiment," "an embodiment," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment described generally throughout this application. The appearances of the same phrase in various places in the specification are not necessarily all referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with any embodiment, it is submitted that it is within the scope of the invention to effect such feature, structure, or characteristic in connection with other embodiments.
Although the invention has been described herein with reference to a number of illustrative embodiments thereof, it should be understood that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the spirit and scope of the principles of this disclosure. More specifically, various variations and modifications are possible in the component parts and/or arrangements of the subject combination arrangement within the scope of the disclosure, the drawings and the appended claims. In addition to variations and modifications in the component parts and/or arrangements, other uses will also be apparent to those skilled in the art.
Claims (9)
1. A JavaScript-based Internet of things device data format conversion system is characterized by comprising:
the simulation service module is used for receiving the JS script of the user side and verifying and judging the current JS script, if the judgment result is yes, the core service module is called to store the current JS script as a draft, otherwise, a prompt is returned to the user side;
the simulation service module is also used for receiving simulation data after the current JS script is stored as a draft, and transmitting the current JS script and the simulation data to the script engine module as parameters;
the script engine module is used for preprocessing the simulation data and the JS script and then executing the current JS script and the simulation data in the sandbox module;
the script engine module is also used for acquiring the execution result of the current JS script and the simulation data and feeding the execution result back to the simulation service module;
the simulation service module is used for calling the core service module to modify the state of the current JS script into a formal state when a result of successful execution is obtained, and returning the result to the user side; otherwise, directly feeding back the result of execution failure to the user side;
the core service module is used for transmitting the JS script modified into the formal state to the converter module;
the converter module is used for searching a corresponding JS script in the JS script pool for replacement according to the equipment identifier in the JS script after receiving the JS script in the formal state, and otherwise, newly adding a JS script; waiting to accept data on the device side.
2. The JavaScript-based internet of things device data format conversion system of claim 1, wherein:
the converter module is also used for receiving data of the equipment side, searching the JS script corresponding to the data in the JS script pool according to the equipment identification in the data, and then transmitting the current JS script and the data of the equipment side to the script engine module as parameters;
the script engine module is used for preprocessing the current JS script and data on the equipment side, then executing the current JS script in the sandbox module, and acquiring an execution result and feeding the execution result back to the converter;
the converter module is used for transmitting the current execution result to the core service module;
the core module is used for feeding back the execution result to the current equipment.
3. The JavaScript-based internet of things device data format conversion system of claim 2, wherein: and the converter module receives data of the equipment side through the protocol gateway.
4. The JavaScript-based internet of things device data format conversion system of claim 1, wherein: before preprocessing the analog data and the JS script, the script engine module firstly acquires the started JS service, and if the JS service is not started, a JS service is additionally started.
5. The JavaScript-based internet of things device data format conversion system of claim 1, wherein: and after feeding back the result of the failed execution to the user side, the simulation service module receives the modified simulation data again until the result of the successful execution is obtained.
6. A JavaScript-based Internet of things device data format conversion method is characterized by comprising the following steps:
step A, the simulation service module receives a JS script of a user side, checks and judges the current JS script, if the judgment result is yes, the core service module is called to store the current JS script as a draft, otherwise, a prompt is returned to the user side;
b, after the current JS script is stored as a draft, the simulation service module receives simulation data and transmits the current JS script and the simulation data as parameters to the script engine module;
step C, the script engine module preprocesses the simulation data and the JS script, and then the current JS script and the simulation data are executed in the sandbox module;
d, the script engine module acquires the execution result of the current JS script and the simulation data and feeds the execution result back to the simulation service module;
step E, when the simulation service module obtains a result of successful execution, the simulation service module calls a core service module to modify the state of the current JS script into a formal state, and returns the result to the user side; otherwise, directly feeding back the result of execution failure to the user side;
step F, the core service module transmits the JS script modified into the formal state to the converter module;
step G, after the converter module receives the JS script in the formal state, finding out a corresponding JS script in the JS script pool for replacement according to the equipment identification in the JS script, and otherwise, newly adding a JS script; waiting to accept data on the device side.
7. The JavaScript-based data format conversion method of an Internet of things device of claim 6, further comprising:
step H, the converter module receives data of the equipment side, a JS script corresponding to the data is searched in the JS script pool according to the equipment identification in the data, and then the current JS script and the data of the equipment side are used as parameters to be transmitted to the script engine module;
step I, after the script engine module preprocesses the current JS script and the data on the equipment side, executing the current JS script in the sandbox module, and obtaining an execution result and feeding the execution result back to the converter;
step J, the converter module is used for transmitting the current execution result to the core service module;
and K, the core module is used for feeding back the execution result to the current equipment.
8. The JavaScript-based data format conversion method of an Internet of things device of claim 6, wherein: in the step C, before the simulation data and the JS script are preprocessed, the script engine module firstly acquires the started JS service, and if the JS service is not started, a JS service is additionally started.
9. The JavaScript-based data format conversion method of an Internet of things device of claim 6, wherein: in the step E, after the simulation service module feeds back the result of the execution failure to the user side, the step B and the step C are repeated, and the modified simulation data is received again until the result of the execution success is obtained.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011265525.XA CN112286530A (en) | 2020-11-12 | 2020-11-12 | JavaScript-based Internet of things equipment data format conversion system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011265525.XA CN112286530A (en) | 2020-11-12 | 2020-11-12 | JavaScript-based Internet of things equipment data format conversion system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112286530A true CN112286530A (en) | 2021-01-29 |
Family
ID=74398683
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011265525.XA Pending CN112286530A (en) | 2020-11-12 | 2020-11-12 | JavaScript-based Internet of things equipment data format conversion system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112286530A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102375778A (en) * | 2010-08-17 | 2012-03-14 | 中兴通讯股份有限公司 | Method and system for automatically testing digital signal processor (DSP) |
| CN105812441A (en) * | 2014-12-31 | 2016-07-27 | 青岛中科软件股份有限公司 | Internet of things equipment control device |
| CN108923999A (en) * | 2018-05-31 | 2018-11-30 | 苏州蜗牛数字科技股份有限公司 | A kind of net surfing server automatic performance test method and system |
| EP3457295A2 (en) * | 2017-09-19 | 2019-03-20 | Screenshare Technology Ltd. | Method for recording, editing and reproduction of computer session |
| CN111083225A (en) * | 2019-12-19 | 2020-04-28 | 远景智能国际私人投资有限公司 | Data processing method and device in Internet of things platform and Internet of things platform |
| CN111459135A (en) * | 2020-04-02 | 2020-07-28 | 张瑞华 | Intelligent home fault state tracing method based on Internet of things and central control center |
-
2020
- 2020-11-12 CN CN202011265525.XA patent/CN112286530A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102375778A (en) * | 2010-08-17 | 2012-03-14 | 中兴通讯股份有限公司 | Method and system for automatically testing digital signal processor (DSP) |
| CN105812441A (en) * | 2014-12-31 | 2016-07-27 | 青岛中科软件股份有限公司 | Internet of things equipment control device |
| EP3457295A2 (en) * | 2017-09-19 | 2019-03-20 | Screenshare Technology Ltd. | Method for recording, editing and reproduction of computer session |
| CN108923999A (en) * | 2018-05-31 | 2018-11-30 | 苏州蜗牛数字科技股份有限公司 | A kind of net surfing server automatic performance test method and system |
| CN111083225A (en) * | 2019-12-19 | 2020-04-28 | 远景智能国际私人投资有限公司 | Data processing method and device in Internet of things platform and Internet of things platform |
| CN111459135A (en) * | 2020-04-02 | 2020-07-28 | 张瑞华 | Intelligent home fault state tracing method based on Internet of things and central control center |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101930400B (en) | SDK (Software Development Kit) automatic test system and method | |
| CN110457143B (en) | Micro-service calling method and device | |
| CN110032697A (en) | Image processing method, device, computer equipment and storage medium | |
| CN106547683B (en) | A kind of redundant code detection method and device | |
| CN105204917B (en) | The method and device of loading configuration file in application program launching | |
| CN106919511B (en) | Application simulation method, simulation application, operation method thereof and simulation system | |
| CN110515827A (en) | Automated testing method, device, computer equipment and storage medium | |
| CN114691398A (en) | Rule-based fault analysis method, device, equipment and storage medium | |
| CN112181477A (en) | Complex event processing method and device and terminal equipment | |
| CN115480753A (en) | Application integration system and corresponding computer device and storage medium | |
| CN115329170A (en) | Webpage crawling method, device, equipment and storage medium | |
| CN104347081A (en) | Method and device for testing scene statement coverage | |
| CN112286530A (en) | JavaScript-based Internet of things equipment data format conversion system and method | |
| US20200286012A1 (en) | Model application method, management method, system and server | |
| CN109446146B (en) | State transition sequence generation method of application layer communication protocol | |
| CN112416747A (en) | Test case execution method, device, equipment and medium | |
| CN108173957B (en) | Rapid configuration joint debugging platform for Http interface | |
| CN114385493A (en) | Performance test method and device, electronic equipment and storage medium | |
| CN112711602B (en) | Method and device for running stored procedure, database system and storage medium | |
| CN110912741A (en) | Intelligent label generation method and device based on reverse analysis | |
| CN108694046B (en) | Container assembly method and apparatus | |
| CN112148854B (en) | Dialogue management method and device | |
| CN116795424B (en) | Workflow engine-based commonality model assembling and debugging method and system | |
| CN118259946A (en) | Data updating method and data updating device | |
| CN116599814A (en) | MML command execution method, device, equipment and medium of operation maintenance center |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210129 |
|
| RJ01 | Rejection of invention patent application after publication |