WO2014075471A1 - 一种物联网终端应用一体化生成系统和方法 - Google Patents
一种物联网终端应用一体化生成系统和方法 Download PDFInfo
- Publication number
- WO2014075471A1 WO2014075471A1 PCT/CN2013/081430 CN2013081430W WO2014075471A1 WO 2014075471 A1 WO2014075471 A1 WO 2014075471A1 CN 2013081430 W CN2013081430 W CN 2013081430W WO 2014075471 A1 WO2014075471 A1 WO 2014075471A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- platform
- business logic
- side application
- application business
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 230000008569 process Effects 0.000 claims abstract description 35
- 238000004891 communication Methods 0.000 claims description 60
- 238000004088 simulation Methods 0.000 claims description 51
- 238000012544 monitoring process Methods 0.000 claims description 22
- 230000001960 triggered effect Effects 0.000 claims description 17
- 238000004458 analytical method Methods 0.000 claims description 6
- 230000008676 import Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 13
- 238000011161 development Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000006243 chemical reaction Methods 0.000 description 6
- 238000012795 verification Methods 0.000 description 5
- 230000001419 dependent effect Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 239000003086 colorant Substances 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000003032 molecular docking Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
Definitions
- the present invention relates to the field of Internet of Things technologies, and in particular, to an integrated generation system and method for an Internet of Things terminal application.
- the Internet of Things refers to the acquisition of information about the physical world by deploying various terminal devices with certain sensing, computing, execution, and communication capabilities. The transmission, coordination, and processing of information through the network enables a wide range of people, objects, objects, and objects. An interconnected network of information exchanges.
- the Internet of Things involves Internet of Things platforms, IoT terminals, IoT applications and other intermediate networks, with the IoT platform providing various functional interfaces to different IoT applications.
- the IoT application includes two parts of logic: platform-side application business logic and terminal-side application business logic.
- Figure 1 shows the development mode of the two parts of the application business logic in the related art, and the two are independently developed, tested, and deployed. It generally includes the following steps:
- Step 1 Develop and test the application logic of the IoT terminal side separately.
- Step 2 Develop and test the application logic of the IoT platform side separately.
- Step 3 Deploy the two parts of the application service logic to the platform and the terminal respectively, and perform the debugging of the platform side application service logic and the terminal side application service logic.
- the platform-side application business logic and the terminal-side application business logic are related, and have close upper and lower process relationships.
- the current practical application of the Internet of Things is to separate the two. Therefore, before the IoT application is officially launched, a large number of docking debugging work is required on the platform side and the terminal side. Especially if the platform side application business logic and the terminal side application business logic are respectively developed by different vendors, the debugging process will be more Repeatedly, debugging time often
- the embodiment of the present invention provides an IoT platform and an IoT terminal integrated generation system and method.
- An embodiment of the present invention provides an integrated method for generating an Internet of Things terminal application, including: providing a terminal component and a platform component required by the Internet of Things terminal application;
- the terminal component and the platform component are arranged to form an application business process, and after the programming ends, the platform side application service logic and the terminal side application service logic are generated.
- the orchestration is performed in an orchestration area, and the arranged object includes the following elements: a node, the terminal component, the platform component, a trigger service encapsulated by the terminal component, and encapsulated by the platform component.
- the trigger service is performed in an orchestration area, and the arranged object includes the following elements: a node, the terminal component, the platform component, a trigger service encapsulated by the terminal component, and encapsulated by the platform component.
- the trigger service is performed in an orchestration area, and the arranged object includes the following elements: a node, the terminal component, the platform component, a trigger service encapsulated by the terminal component, and encapsulated by the platform component.
- the step of generating the terminal side application service logic and the platform side application service logic includes:
- the terminal side application service logic and the platform side application service logic are generated according to the parsing judgment of the element type.
- the method further includes:
- the step of performing analog debugging on the terminal side application service logic and the platform side application service logic includes:
- the terminal side application service logic and the platform side application service logic are adjusted according to the operation situation.
- the method further includes:
- the method further includes:
- the step of publishing the terminal side application service logic and the platform side application service logic includes:
- the platform-side application service logic is directly deployed to the platform execution system, and the terminal-side application service logic is deployed to the terminal execution system, or the platform-side application service logic and the terminal-side application service logic are first processed.
- the platform side service logic application package and the terminal side service logic application package are generated, and then the platform side service logic application package is deployed to the platform execution system and the terminal side service logic application package is deployed to the terminal execution system.
- the embodiment of the present invention further provides an integrated generation system for an Internet of Things terminal application, comprising: a component module, configured to: provide a terminal component and a platform component required for the application of the Internet of Things terminal;
- the orchestration module is configured to: arrange the terminal component and the platform component to form an application business process, and after the programming ends, generate platform-side application business logic and terminal-side application business logic.
- the orchestration module provides an orchestration area, where the arrangement is performed in the arrangement area, and the object of the arrangement includes the following elements: a node, the terminal component, the platform component, and the packaged by the terminal component Trigger service and trigger service encapsulated by the platform component.
- the orchestration module is configured to generate terminal side application service logic and platform side application service logic in the following manner:
- system further includes:
- the debugging module is configured to: establish an information channel between the terminal-side application service logic platform and the side application service logic, to perform simulation debugging on the terminal-side application service logic and the platform-side application service logic.
- the debugging module is configured to perform analog debugging on the terminal side application service logic and the platform side application service logic in the following manner:
- the operation of the terminal-side application service logic and the operation of the platform-side application service logic are simulated by the communication channel, and the terminal-side application service logic and the platform-side application are adjusted according to the operation situation.
- Business logic The operation of the terminal-side application service logic and the operation of the platform-side application service logic are simulated by the communication channel, and the terminal-side application service logic and the platform-side application are adjusted according to the operation situation.
- Business logic The operation of the terminal-side application service logic and the operation of the platform-side application service logic are simulated by the communication channel, and the terminal-side application service logic and the platform-side application are adjusted according to the operation situation. Business logic.
- the debugging module is further configured to: before simulating the running status of the application logic of the terminal side and the running status of the application logic of the platform side, determining a type of the current element, when the current element is a terminal In the class, the terminal side application business logic is used for simulation; when the current element is a platform class, the platform side application business logic is used for simulation; and when the current element is a general class, according to the process connection line The type of the previous element is judged.
- system further includes:
- a publishing module configured to: after the simulation debugging of the debugging module ends, issue the terminal side application service logic and the platform side application service logic;
- the publishing module is configured to issue the terminal side application service logic and the platform side application service logic in the following manner:
- the terminal side service logic application package and the platform side service logic application package are generated, and then the terminal side service logic application package is deployed into the terminal execution system and the platform side service logic application package is deployed to the platform execution system.
- An embodiment of the present invention further provides an Internet of Things terminal execution system, including:
- a terminal component module configured to: load a component required by the terminal side application business logic, and execute and maintain the component;
- a terminal parsing execution module configured to: parse and trigger the terminal side application service logic to execute the terminal side application service logic
- the terminal communication module is configured to: communicate with a platform corresponding to the terminal execution system, and send a result of the terminal execution system executing the terminal side application service logic to the platform.
- the terminal parsing execution module is configured to trigger the terminal side application service logic in the following manner:
- the terminal side application service logic is triggered by starting a node, a message instruction from the platform, or a terminal collecting data.
- system further includes:
- the terminal monitoring module is configured to: monitor the execution result of the terminal executing the business logic of the terminal side by the system, and display the execution result when needed.
- An embodiment of the present invention further provides an Internet of Things platform execution system, including:
- a platform component module configured to: load components required by the platform side application business logic, and execute and maintain the components;
- a platform parsing execution module configured to: parse and trigger the platform side application business logic
- the platform communication module is configured to: perform communication between the terminal and the platform, and receive a result of the terminal performing the terminal side application service logic.
- the platform parsing execution module is configured to trigger the platform side application service logic in the following manner:
- the platform side application service logic is triggered by a start node or a message instruction from the terminal.
- the system further includes:
- the platform monitoring module is configured to: receive or import the terminal monitoring package by using the platform communication module, obtain an execution result of the terminal side application service logic, and display the execution result when needed.
- unified debugging and debugging of the programmed application service logic flow can be directly performed on the terminal side and the platform side after debugging, without repeated joint debugging, thereby eliminating the on-line deployment.
- the joint adjustment step reduces the joint debugging time of the IoT application platform side and the terminal side, and expands the terminal's ability to run, upgrade, update, and debug during the service operation.
- the service logic of the Internet of Things application can display the execution performance of the business logic on the platform side and the terminal side through the monitoring function, which facilitates tracking and troubleshooting the operation of the business logic to ensure long-term stability of the system. run.
- FIG. 1 is a system diagram of an IoT application scheme in the related art.
- FIG. 2 is a flow chart of a method for integrally generating an Internet of Things terminal application according to an embodiment of the present invention.
- FIG. 3 is a structural block diagram of an integrated generation system for an Internet of Things terminal application according to an embodiment of the present invention.
- 4 is a system diagram of an Internet of Things application solution in an embodiment of the present invention.
- FIG. 5 is a schematic structural diagram of a component module in an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a layout module in an embodiment of the present invention.
- FIG. 7 is a flowchart of analyzing application logic of a terminal side according to an embodiment of the present invention.
- FIG. 8 is a flowchart of analyzing application logic of a platform side according to an embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of a debugging module in an embodiment of the present invention.
- FIG. 10 is an analysis flowchart before simulation debugging in the embodiment of the present invention.
- FIG. 11 is a schematic structural diagram of a publishing module in an embodiment of the present invention.
- FIG. 12 is a structural diagram of an Internet of Things terminal execution system in an embodiment of the present invention.
- 13-15 are schematic diagrams of various functional modules of the Internet of Things terminal execution system in the embodiment of the present invention.
- 16 is a structural diagram of an Internet of Things platform execution system in an embodiment of the present invention.
- 17 and 18 are schematic diagrams of various functional modules of the Internet of Things platform execution system in the embodiment of the present invention.
- FIG. 2 is a flowchart of a method for integrally generating an Internet of Things terminal application according to an embodiment of the present invention, which includes the following steps:
- Step S101 providing terminal components and platform components required for the Internet of Things terminal application.
- Step S102 The terminal component and the platform component are arranged to form an application service flow, and after the programming ends, the platform side application service logic and the terminal side application service logic are generated.
- the above-mentioned methods are used to uniformly organize the terminal components and platform components to form a unified application business process.
- the application business logics applicable to the terminal side and the platform side are automatically generated, so that the business logic of the Internet of Things application can be directly integrated and developed. It is not necessary to distinguish between terminal-side application business logic or platform-side application business logic, and the development efficiency is high.
- an information channel is established between the two to debug the two.
- the terminal side application service logic and the platform side application service logic are released, the terminal side application service logic is deployed to the terminal execution system, and the platform side application service logic is deployed to the platform execution system.
- FIG. 3 is a structural block diagram of an IOT terminal application integration generation system according to an embodiment of the present invention.
- the system includes a component module 10, a layout module 11, a debugging module 12, and a distribution module 13, wherein the component module 10
- the device is configured to: provide a terminal component and a corresponding platform component required for the Internet of Things terminal application;
- the orchestration module 11 is configured to: arrange the terminal component and the platform component to form an application business process, and after the programming ends, generate a platform
- the application logic and the terminal-side application service logic are configured on the side;
- the debugging module 12 is configured to: establish an information channel between the platform-side application service logic and the terminal-side application service logic, to apply the service logic to the platform-side and the terminal
- the side application service logic performs the simulation debugging; and the publishing module 13 is configured to: after the simulation debugging of the debugging module 12 ends, the platform side application service logic and the terminal side application business logic are released.
- the system is used to develop and debug terminal-side application business logic and platform-side application business logic, and publish terminal-side application business logic and platform-side application business logic and deploy them in their respective execution environments to realize the integration of IoT terminal applications. Development.
- FIG. 4 is a block diagram of an overall structure of an Internet of Things application system according to an embodiment of the present invention.
- the upper part is an integrated generation system used in this embodiment, including a component module 10, a layout module 11, a debugging module 12, and
- the publishing module 13 and the lower part are execution environments of the terminal side application service logic and the platform side application service logic, including the Internet of Things terminal execution system and the Internet of Things platform execution system.
- the integrated application and logic of the terminal side application service logic and the platform side application service logic can be realized by using the Internet of Things application system of the embodiment shown in FIG. 4, and after the debugging is passed, the two parts of the application service logic are respectively deployed on the terminal to execute.
- the system and platform execution system can be used directly.
- the component module 10 is configured to: provide terminal components and platform components required for the Internet of Things terminal application, register, load and manage the components, etc., the components described herein are the minimum functional units called in the application logic, and have unique Component identifier (Identifier, ID).
- the components are classified into two types: a terminal component and a platform component, wherein the terminal component is a component that runs only on the terminal side, and the platform component is a component that runs only on the platform side, and the component module is 10 perform operations such as registration, loading, and management of terminal components and platform components.
- the component module 10 includes a component uploading unit 101, a component registration unit 102, a component storage unit 103, a component interpretation unit 104, and a component upgrading unit 105.
- the component uploading unit 101 is configured to: receive a component package uploaded by the user, and verify the format and size of the component package, upload the component package to the component storage unit 103 after the verification is passed, and notify the component registration unit 102 to load the component package. jobs.
- the component package is a collection of files that satisfy certain rules of the component, usually in the form of a compressed package.
- the component registration unit 102 is configured to: after receiving the component package loading notification message of the component uploading unit 101, read the component package to be registered from the component storage unit 103. According to the component description rule, the legality verification of the file collection in the component package is performed, and the file collection includes: component element
- the legality verification includes: verification of an execution method, an input parameter, and an output parameter. After the component package that needs to be registered is verified, the component package is converted into an organization form inside the component. In the component storage unit 103, the metadata of the component, the execution file, and the dependency file are saved.
- the component storage unit 103 can save the component package after the component uploading unit 101 verifies the verification, and can save the component metadata and the component method execution file after the component registration unit 102 verifies the passing.
- the component interpreting unit 104 can parse the metadata of the component for use by the orchestration module 11; can load the execution file and the dependency file of the component for use by the debugging module 12;
- the batch component method relies on files for processing, filtering out a minimal set of dependent files for use by the publishing module 13.
- the component upgrading unit 105 is capable of replacing components having the same component ID. After the component package of the component registration unit 102 is verified, the component upgrading unit 105 first determines whether it is the same component according to the component ID, and if so, removes the metadata, the execution file, and the dependency file of the original component in the component storage unit 103, and The original component package was removed. The component registration unit 102 is then notified to continue the conversion of the component package.
- the orchestration module 11 is configured to: arrange the business logic flow of the Internet of Things application online. When orchestrating, whether it is platform-side business logic or terminal-side business logic, all business logic processes are visually arranged in the layout area. All nodes, components, and triggering services that appear in the orchestration area are collectively referred to as elements, where all elements except the end node and the triggering service have only one input connection line; all elements can have multiple output connection lines. Among them, the starting node is abstracted into an output-only element; the ending node is abstracted into an input-only element; other nodes, triggering services, components, and sub-services can be abstracted into elements that contain both input and output.
- the orchestration module 11 includes a node providing unit 111, a component presentation unit 112, a trigger service unit 113, a sub-service unit 114, a layout drawing unit 115, a layout analysis unit 116, an arrangement generation unit 117, and an arrangement storage unit 118.
- the node providing unit 111 provides the most basic orchestration elements of the application business logic, including: a start node, an end node, an expression node, an operation node, and a communication node. Among them, a business logic is triggered by a start node and completed by an end node.
- the expression node defines the variables in the business logic flow.
- the arithmetic node performs logical operations on variables in the business logic flow.
- the operations include: four arithmetic operations, generating random numbers, obtaining current time, and string operations.
- Communication nodes are implicit in the business logic flow and are only simulated or generated when debugging or publishing.
- the node providing unit 111 is built in the system, and the other nodes are common except that the starting node and the ending node have the difference between the terminal class and the platform class, that is, the other nodes are not distinguished by the terminal class or Platform class, the type of other nodes is a generic class.
- the component presentation unit 112 is arranged to: present components managed by the component module 10.
- the component presentation unit 112 can invoke the component interpretation unit 104 in the component module 10 to display the metadata of the component.
- Component presentation unit 112 may present states such as additions, deletions, and upgrades of components.
- the trigger service unit 113 is configured to: expand a trigger condition of the application service logic, encapsulate the component, and form a trigger service.
- the trigger service receives the relevant parameters, it can immediately trigger the business logic flow and start the component to run.
- the trigger service since the component has a type distinction between the terminal side and the platform side, the trigger service also has a distinction between the terminal side and the platform side.
- the sub-service unit 114 invokes another service logic flow in a business logic flow, and the called party is called a sub-service of the caller.
- the sub-service unit 114 is arranged to: display the services already existing in the component storage unit 103 for the orchestration drawing unit 115 to arrange in the arrangement area.
- the orchestration drawing unit 115 is configured to: provide a layout area of the business logic flow, arrange and graphically display the nodes, components, and trigger services in the orchestration area, and connect the nodes, components, and trigger services through the process connection line, To form a complete business logic process.
- the orchestration drawing unit 115 can arrange the sub-services as a special node in the orchestration area, and connect the sub-services with the related nodes, components, and trigger services through the process connection lines to form a complete business logic flow.
- the orchestration drawing unit 115 is further configured to: maintain nodes, components, trigger services, and sub-services.
- the orchestration drawing unit 115 names the name of the node in the business logic flow; wherein, for the expression node, the orchestration drawing unit 115 can define variables required for the business logic flow; for the operation node, arrange the drawing unit 115 can select various variables defined by the expression, and can select various logical operations of the operation node.
- the orchestration drawing unit 115 names the name of the component in the business logic flow; and binds the input parameter of the component to the variable defined by the expression node, and assigns the output parameter of the component to the variable defined by the expression node. on.
- the orchestration drawing unit 115 names the name of the trigger service in the business logic flow; and assigns the output parameter of the trigger service to the variable defined by the expression node.
- the orchestration drawing unit 115 names the name of the sub-service in the business logic flow; and binds the input parameter of the sub-service to the variable defined by the expression node, and assigns the output parameter of the sub-service to the expression On the variable defined by the node.
- the orchestration parsing unit 116 can sequentially parse the unified application service logic flow generated by the orchestration drawing unit 115 according to the process connection line direction, and generate the terminal side application service logic and the platform side application service according to the parsing judgment of the element type. logic.
- FIG. 7 is a flowchart of parsing application logic of the terminal side according to an embodiment of the present invention.
- the parsing parsing unit 116 performs sequential parsing in the direction of the connecting line, and first determines the type of the current element. If the current element type is a terminal class, the information of the element is directly notified to the orchestration generating unit 117.
- the current element type is a platform class and is resolved to the platform class element for the first time, a terminal class communication node is generated, and the node and the current element are notified to the orchestration generating unit 117, and the message interface of the communication node is According to the message type of the previous terminal class element of the process connection line; if the element type is a platform class, but not the first time to resolve to the platform class element, skip the element to continue parsing. If the current element type is a generic class, the generation type of the current element is determined according to the type of the previous element of the process connection line.
- the previous element type is a terminal class
- the current element is notified to the orchestration generating unit 117; if the previous element type is a platform class, skip the element to continue parsing; if the previous element type is a general class, continue Look for the judgment of the previous element of the process connection line.
- the orchestration generating unit 117 After all the elements of the entire business logic flow are parsed, the orchestration generating unit 117 generates terminal-side application business logic according to the analysis result, and stores it in the arrangement storage unit 118.
- FIG. 8 is a flowchart of parsing application logic of platform-side application according to an embodiment of the present invention, and the parsing parsing unit 116 performs sequential parsing in a connection line direction. If the element type is a platform class, the element is directly notified to the orchestration generating unit 117. If the element type is a terminal
- 11 181304132 a class, and the first time to resolve to a terminal class element, generate a platform class communication node, notify the orchestration generating unit 117 of the node, and the message interface of the communication node is based on a previous platform class of the process connection line
- the message type of the element is determined; if the element type is a terminal class, but not the first time to resolve to the terminal class element, then skip the element to continue parsing. If the element type is a generic class, the generation type of the current element is determined according to the type of the previous element of the process connection line.
- the previous element type is a platform class
- the current element is notified to the orchestration generating unit 117; if the previous element type is a terminal class, the element is skipped to continue parsing; if the previous element type is a general class, then continue Look for the judgment of the previous element of the process connection line.
- the orchestration generating unit 117 After all the elements of the entire business logic flow are parsed, the orchestration generating unit 117 generates platform-side application business logic according to the parsing result, and stores it in the orchestration storage unit 118.
- the orchestration storage unit 118 is configured to: save metadata of the terminal side application service logic and the platform side application service logic generated by the orchestration generation unit 117, where the metadata includes: service logic flow description information, elements in the arrangement area Relative position information and element self information.
- the orchestration parsing unit 116 reads various metadata of the sub-service logic flow, and starts parsing the sub-service logic flow according to the sub-service logic flow description information, and the parsing method is the same as above.
- the debugging module 12 is configured to: simulate and debug the terminal side application business logic and the platform side application business logic. As shown in FIG. 9, the debug module 12 includes: a parsing execution unit 121, a platform emulation unit 122, a terminal emulation unit 123, a communication emulation unit 124, and a display unit 125.
- the parsing execution unit 121 reads various metadata of the terminal side application service logic and the platform side application service logic from the orchestration storage unit 118 of the orchestration module 11, and starts simulation for the two-part application service logic according to the service logic flow description information. debugging. If the business logic flow starts with the start node, the startup debugging process is triggered immediately; if the business logic flow is triggered by the trigger service, the startup debugging process is triggered after the user inputs the trigger service parameter. The parsing execution unit 121 can parse the relative position of each element in the business logic flow, and send it to the display unit 125 for display.
- the parsing execution unit 121 also parses each element, notifies the terminal emulation unit 123 to perform simulation, and receives the terminal emulation unit. Returning the result of 123, and notifying the result of the return to the display unit 125; and, the parsing execution unit 121 further parses each element, notifying the platform emulation unit 122 to perform the simulation, and receiving the return result of the platform emulation unit 122, and Notify the results of the return to the exhibition
- the platform simulation unit 122 can simulate the actual execution of the platform-side environment, and can perform simulation execution on the expression node, the operation node, and the platform-side component, and return the execution result.
- the terminal emulation unit 123 can simulate the real execution of the terminal side environment, and can perform simulation execution on the expression node, the operation node, and the terminal side component, and return the execution result.
- the communication simulation unit 124 is capable of simulating a communication protocol and a communication interface between the terminal side and the platform side.
- the communication protocol and the communication interface are all agreed in advance by the terminal and the platform in the IoT application.
- the analog terminal side communicates with the platform side communication interface; when the communication simulation unit 124 receives the communication simulation request from the platform side to the terminal side, the simulation platform laterally Communication interface on the terminal side.
- the display unit 125 can read the relative positions of various elements of the application service logic flow in the layout area, display in the debug area, and can also receive the return result of the terminal simulation unit 123, the platform simulation unit 122, and the communication simulation unit 124. According to the returned execution result is normal, abnormal or not executed, the elements are respectively set in different colors in the debug area to distinguish them. Then, according to the execution result, the application business logics on the terminal side and the platform side are adjusted as necessary to match the two.
- FIG. 10 is a flowchart of simulated debugging in an embodiment of the present invention, and the parsing execution unit 121 parses each element by: determining the type of the current element. As shown in FIG. 10, if the current element type is a general class, the simulation execution unit corresponding to the current element is determined according to the type of the previous element of the process connection line; wherein, if the previous element type is a platform class, the platform is notified The simulation unit performs simulation. If the previous element type is a terminal class, the terminal simulation unit is notified to perform simulation; if the previous element type is a general class, the determination is continued to the previous element of the process connection line.
- the simulation execution unit of the current element is determined according to the type of the previous element of the process connection line. If the previous element type is a terminal class, the terminal simulation unit is directly notified to perform simulation; if the previous element type is a platform class, the communication simulation unit is first notified to perform simulation, and the communication simulation result is returned, and the return result is notified. Giving the display unit, and then notifying the terminal simulation unit to perform simulation; if the previous element type is a general class, proceed to the previous element search judgment of the process connection line.
- the simulation execution unit of the current element is determined according to the type of the previous element of the process connection line. If the previous element type is a platform class, the platform simulation unit is directly notified to perform simulation; if the previous element type is a terminal class, the communication simulation unit is first notified to perform simulation, and the communication simulation result is returned, and the return result is notified. Giving the display unit, and then notifying the platform simulation unit to perform simulation; if the previous element type is a general class, then continuing to look for the previous element of the process connection line.
- the metadata of the sub-service logic flow is read, and the debugging of the sub-service logic flow is started according to the sub-service logic flow description information.
- the publishing module 13 is configured to: publish the saved terminal-side application business logic and the platform-side application business logic. As shown in FIG. 11, the distribution module 13 includes a reading unit 131 and a distribution unit 132.
- the reading unit 131 is capable of reading metadata of the terminal side application service logic and the platform side application service logic from the arrangement storage unit 118 of the orchestration module 11.
- the issuing unit 132 deploys the terminal-side application service logic and the platform-side application service logic sent by the reading unit 131 to the terminal execution environment and the platform execution environment respectively, and is used online after deployment.
- the two parts of the logic can be directly deployed to the terminal execution environment and the platform execution environment.
- the two parts of the logic can be processed to generate the terminal side business logic application package and the platform side business logic application package, and then release and deploy.
- the terminal side business logic application package and the platform side business logic application package are the business logic of the entire IoT application.
- the terminal side application service logic is directed to the terminal execution system, and the terminal execution system can be installed on different terminal systems, such as Apple OS/Android (iphone Operation System (iOS) / Android);
- the application business logic is for the platform execution system, which can be installed on different platform systems, such as Windows/Linux.
- the embodiment of the present invention further provides an Internet of Things terminal execution system.
- the system includes: a terminal basic module 20, a terminal component module 21, a terminal resolution execution module 22, a terminal communication module 23, and a terminal monitoring module. twenty four.
- the terminal base module 20 is configured to: provide an interface to receive the terminal side application service logic, and perform data conversion; the terminal component module 21 is configured to: load the components required by the terminal side application service logic,
- the terminal resolution execution module 22 is configured to: parse and trigger the terminal side application service logic, and start the service logic flow;
- the terminal communication module 23 is configured to: perform communication between the terminal and the platform And transmitting, by the terminal, the result of executing the terminal-side application service logic to the platform;
- the terminal monitoring module 24 is configured to: monitor execution of the application logic of the terminal-side application, and export the execution result for display.
- the terminal side application service logic can provide three trigger modes: (1) triggering with the start node, (2) triggering with the message instruction of the platform, and (3) triggering the data with the terminal. If the terminal side application service logic is triggered by the start node, it is triggered immediately after startup; if triggered by the platform message instruction, triggered after receiving the message instruction of the platform; and if triggered by the terminal collection data, receiving the trigger service Trigger on the terminal side related parameters.
- FIG. 13 is a terminal basic module 20 according to an embodiment of the present invention, including: an interface unit 201, a converting unit 202, and an access unit 203.
- the interface unit 201 can provide a unified terminal access interface to all elements, receive data sent by the interface caller, and send data to the conversion unit in the downlink according to the interface type; and can receive trigger data of the conversion unit 202, And notify the interface caller to receive.
- the converting unit 202 can receive the downlink data sent by the interface unit 201, perform data stream transcoding according to the operating system type of the terminal, and access the terminal device through the access unit 203, or access the platform execution system, so that the trigger service has the terminal. After the data is collected, the trigger and the platform message instruction are triggered in two forms; and the information of the terminal device can be received by the access unit 203, and the data stream is transcoded and sent to the interface unit 201.
- the access unit 203 is capable of accessing various functions provided by the terminal device on the terminal operating system and is capable of communicating with the conversion unit 202.
- FIG. 14 is a terminal component module 21 according to an embodiment of the present invention, which includes: a terminal component storage unit 211, a terminal component loading unit 212, a terminal component parsing unit 213, and a terminal component executing unit 214.
- the terminal component storage unit 211 holds metadata of the component, an execution file, and a dependent file.
- the terminal component loading unit 212 can be loaded in the end of the integrated application development environment.
- the terminal component parsing unit 213 is capable of parsing the component metadata in the terminal component storage unit 211 and notifying the terminal component execution unit 214 to run the component.
- the terminal component execution unit 214 is capable of running a specific function of the component through an execution file of the component, a dependent file. Since the component is developed based on the terminal base module 20 of the terminal, the terminal component execution unit 214 transmits the component data to the interface unit 201 of the terminal base module 20.
- FIG. 15 is a terminal parsing execution module 22 according to an embodiment of the present invention.
- the terminal parsing and executing module 22 is configured to: parse and execute a terminal side application logic execution package.
- the terminal resolution execution module 22 includes: a terminal parsing unit 221, a terminal node executing unit 222, and a terminal component executing unit 223.
- the terminal parsing unit 221 can sequentially analyze each element according to the terminal side business logic flow description information. If the element is a node, the calling node execution unit runs and receives the running result; if the element is a component, the calling component execution unit executes and receives the running result.
- the terminal parsing unit 221 is configured to: when the service logic flow is started by a start node, trigger the terminal side application logic immediately; when the service logic flow is started by a terminal trigger service, the terminal base is monitored.
- the interface unit 201 of the module 20 triggers the terminal side application logic when there is an input condition of the trigger service and receives the relevant parameter.
- the terminal analyzing unit 221 can send the information of the element and the running result to the platform execution environment through the terminal communication module 23.
- the terminal node execution unit 222 can execute the logic of the node and return the running result.
- the terminal component execution unit 223 can call the terminal component analysis unit 213 of the terminal component module 21 to execute the function of the component and return the running result.
- the terminal communication module 23 is configured to: communicate between the terminal and the platform.
- the communication protocol and communication interface provided by the terminal communication module 23 are uniformly agreed between the terminal and the platform in the Internet of Things application.
- the terminal communication module 23 uses the terminal when communicating with the platform execution environment
- the terminal monitoring module 24 is configured to: monitor execution of the application logic of the terminal side application, and export the execution result for display. For example, if the terminal communication module 23 encounters a communication link abnormality, the terminal monitoring module 24 can buffer the execution result of the terminal, and derive the execution result in the form of the terminal monitoring package.
- the above-mentioned Internet of Things terminal execution system receives, parses, and executes the terminal-side application service logic, monitors the execution status, and sends each component information and operation result in the terminal-side application service logic to the platform to implement the Internet of Things terminal application.
- an embodiment of the present invention further provides an Internet of Things platform execution system.
- the system includes: a platform basic module 30, a platform component module 31, a platform parsing execution module 32, a platform communication module 33, and a platform. Monitoring module 34.
- the platform basic module 30 is configured to: provide an interface to receive platform-side application business logic, and perform data conversion; the platform component module 31 is configured to: load components required by the platform-side application business logic, and execute and maintain the components;
- the parsing execution module 32 is configured to: parse and trigger the platform side application service logic;
- the platform communication module 33 is configured to: perform communication between the terminal and the platform, and receive the result of the terminal executing the terminal side application service logic;
- the platform monitoring module 34 It is configured to: receive or import the terminal monitoring package by the platform communication module 33, and obtain the execution result of the terminal side application service logic and display it.
- the platform-side application business logic can provide two trigger modes: (1) triggering with the start node and (2) triggering with the message command of the terminal. If the platform-side application service logic is triggered by the start node, triggering immediately after the startup; if the platform-side application service logic is triggered by the terminal's message instruction, the platform-side application is triggered after receiving the message instruction of the terminal. Business logic.
- the platform component module 31 includes: a platform component storage unit 311, a platform component loading unit 312, a platform component parsing unit 313, and a platform component execution unit 314.
- the platform component storage unit 311 holds metadata of components, execution files, and dependent files.
- the platform component loading unit 312 is capable of loading platform class components in the integrated application development environment, and adding, deleting, and upgrading components by component IDs. Able to group
- the platform component parsing unit 313 can parse the component metadata in the platform component storage unit 311, and notify the platform component execution unit 314 to run the component.
- the platform component execution unit 314 is capable of running a particular function of the component through an execution file, a dependency file of the component.
- the platform parsing execution module 32 includes: a platform parsing unit 321, a platform node executing unit 322, and a platform component executing unit 323.
- the platform parsing unit 321 can parse each element in turn according to the description information of the platform side application service logic. If the element is a node, the platform node execution unit 322 is invoked to run and receive the running result; if the element is a component, the platform component execution unit 323 is invoked to run and receive the running result. The platform parsing unit 321 sends the two-part operation result to the platform monitoring module 34.
- the platform communication module 33 is configured to: communicate between the platform and the terminal, and after receiving the information instruction of the terminal, start the platform side application service logic by triggering the service.
- the platform communication module 33 also receives the running result of the terminal side application service logic from the terminal, and sends the running result to the platform monitoring module 34.
- the communication protocol and the communication interface provided by the platform communication module 33 are uniformly agreed by the platform and the terminal in the Internet of Things application.
- the platform monitoring module 34 can receive or import the terminal monitoring package through the platform communication module 33, obtain the terminal side application service logic execution result, and combine the platform side application from the platform parsing unit 321 and the platform communication module 33.
- the execution result of the business logic displays the execution result graphically in the monitoring area. In the case where the returned execution result is normal, abnormal, not executed, etc., the display area is displayed in different colors in different colors.
- the above-mentioned Internet of Things platform execution system can receive the execution result of the application logic of the terminal side, and implement the execution and monitoring functions of the integrated business logic in combination with the execution of the application logic of the platform side application.
- each module/unit in the foregoing embodiment may be implemented in the form of hardware, or may be implemented in the form of a software function module.
- Embodiments of the invention are not limited to any specific form of combination of hardware and software.
- the development efficiency is improved; the joint debugging time of the IoT application platform side and the terminal side is reduced, and the capability of the terminal to operate, upgrade, update, and debug during the service operation is expanded; Track and troubleshoot the operation of business logic to ensure long-term stable operation of the system.
Abstract
一种物联网终端应用一体化生成方法和系统。所述方法包括：提供物联网终端应用所需要的终端组件和平台组件；以及对终端组件和平台组件进行编排以形成一个应用业务流程，编排结束后，生成平台侧应用业务逻辑和终端侧应用业务逻辑。
Description
一种物联网终端应用一体化生成系统和方法 技术领域
本发明涉及物联网技术领域， 尤其涉及一种物联网终端应用一体化生成 系统和方法。
背景技术
随着科学技术的发展， 物联网技术逐渐成熟， 各类物联网应用孕育而生， 涉及到人们生活中的方方面面， 这一切都给物联网领域的相关厂商带来了巨 大的商机。 物联网是指通过部署具有一定感知、 计算、 执行和通信能力的各 种终端设备获得物理世界的信息， 通过网络实现信息的传输、 协同和处理， 从而实现广域的人与物、 物与物之间信息交换的互联的网络。 物联网涉及物 联网平台、 物联网终端、 物联网应用和其它中间网络， 其中物联网平台将各 种功能接口提供给不同的物联网应用。 通常地， 物联网应用包括两部分逻辑： 平台侧应用业务逻辑和终端侧应用业务逻辑， 图 1为相关技术中这两部分应 用业务逻辑的开发模式， 两者是独立开发、 测试并部署的， 大致包括如下步 骤：
步骤 1、 单独开发、 测试物联网终端侧应用业务逻辑。
步骤 2、 单独开发、 测试物联网平台侧应用业务逻辑。
步骤 3、 将两部分应用业务逻辑分别部署到平台和终端， 进行平台侧应 用业务逻辑和终端侧应用业务逻辑的对接调试。
如果对接不成功， 要反复进行步骤 1-3 , 直至对接成功， 形成整个物联网 应用系统。
在一个实际的物联网应用中， 其平台侧应用业务逻辑和终端侧应用业务 逻辑是相关的， 有着密切的上、 下流程关系， 但是， 目前的物联网实际应用 是将两者分离开来的， 导致在物联网应用正式上线之前， 需要平台侧和终端 侧进行大量的对接调试工作， 特别是如果平台侧应用业务逻辑和终端侧应用 业务逻辑分别由不同的厂商开发， 则调试的过程将多次反复， 调试时间往往
1 181304132
发明内容
为了解决相关技术中物联网平台应用业务逻辑和物联网终端应用业务逻 辑分离的问题， 本发明实施例提供了一种物联网平台和物联网终端一体化生 成系统和方法。
本发明实施例提供一种物联网终端应用一体化生成方法， 包括： 提供所述物联网终端应用所需要的终端组件和平台组件； 以及
对所述终端组件和所述平台组件进行编排以形成一个应用业务流程， 编 排结束后， 生成平台侧应用业务逻辑和终端侧应用业务逻辑。
可选地， 所述编排在编排区域进行， 编排的对象包括以下元素： 节点、 所述终端组件、 所述平台组件、 由所述终端组件封装而成的触发服务和由所 述平台组件封装而成的触发服务。
可选地， 所述生成终端侧应用业务逻辑和平台侧应用业务逻辑的步骤包 括：
根据对元素类型的解析判断， 生成所述终端侧应用业务逻辑和所述平台 侧应用业务逻辑。
可选地， 所述方法还包括：
在生成所述终端侧应用业务逻辑和所述平台侧应用业务逻辑之后， 在所 述平台侧应用业务逻辑和所述终端侧应用业务逻辑之间建立通信通道， 以对 所述平台侧应用业务逻辑和所述终端侧应用业务逻辑进行模拟调试。
可选地， 所述对所述终端侧应用业务逻辑和所述平台侧应用业务逻辑进 行模拟调试的步骤包括：
通过所述通信通道， 模拟所述终端侧应用业务逻辑的运行情况和所述平 台侧应用业务逻辑的运行情况； 以及
根据所述运行情况， 调整所述终端侧应用业务逻辑和所述平台侧应用业 务逻辑。
2 181304132
可选地， 所述方法还包括：
在模拟所述终端侧应用业务逻辑的运行情况和所述平台侧应用业务逻辑 的运行情况之前， 判断当前元素的类型， 当所述当前元素为终端类时， 使用 所述终端侧应用业务逻辑进行模拟； 当所述当前元素为平台类时， 使用所述 平台侧应用业务逻辑进行模拟； 以及当所述当前元素为通用类时， 根据流程 连接线前一个元素的类型进行判断。
可选地， 所述方法还包括：
在所述模拟调试结束后， 对所述终端侧应用业务逻辑和所述平台侧应用 业务逻辑进行发布；
其中， 所述对所述终端侧应用业务逻辑和所述平台侧应用业务逻辑进行 发布的步骤包括：
直接将所述平台侧应用业务逻辑部署到平台执行系统和将所述终端侧应 用业务逻辑部署到终端执行系统中， 或者， 先将所述平台侧应用业务逻辑和 所述终端侧应用业务逻辑处理生成平台侧业务逻辑应用包和终端侧业务逻辑 应用包， 然后将所述平台侧业务逻辑应用包部署到平台执行系统和将所述终 端侧业务逻辑应用包部署到终端执行系统中。
本发明实施例还提供一种物联网终端应用一体化生成系统， 包括： 组件模块， 其设置成： 提供所述物联网终端应用所需要的终端组件和平 台组件； 以及
编排模块， 其设置成： 对所述终端组件和所述平台组件进行编排以形成 一个应用业务流程， 编排结束后， 生成平台侧应用业务逻辑和终端侧应用业 务逻辑。
可选地， 所述编排模块提供编排区域， 所述编排在所述编排区域中进行， 编排的对象包括以下元素： 节点、 所述终端组件、 所述平台组件、 由所述终 端组件封装而成的触发服务和由所述平台组件封装而成的触发服务。
可选地， 所述编排模块是设置成以如下方式生成终端侧应用业务逻辑和 平台侧应用业务逻辑：
根据对元素类型的解析判断， 生成所述终端侧应用业务逻辑和所述平台
3 181304132
侧应用业务逻辑。
可选地， 所述系统还包括：
调试模块， 其设置成： 在所述终端侧应用业务逻辑平台和所述侧应用业 务逻辑之间建立信息通道， 以对所述终端侧应用业务逻辑和所述平台侧应用 业务逻辑进行模拟调试。
可选地， 所述调试模块是设置成以如下方式对所述终端侧应用业务逻辑 和所述平台侧应用业务逻辑进行模拟调试：
通过所述通信通道， 模拟所述终端侧应用业务逻辑的运行情况和所述平 台侧应用业务逻辑的运行情况， 并根据所述运行情况， 调整所述终端侧应用 业务逻辑和所述平台侧应用业务逻辑。
可选地， 所述调试模块还设置成： 在模拟所述终端侧应用业务逻辑的运 行情况和所述平台侧应用业务逻辑的运行情况之前， 判断当前元素的类型， 当所述当前元素为终端类时， 使用所述终端侧应用业务逻辑进行模拟； 当所 述当前元素为平台类时， 使用所述平台侧应用业务逻辑进行模拟； 以及当所 述当前元素为通用类时， 根据流程连接线前一个元素的类型进行判断。
可选地， 所述系统还包括：
发布模块， 其设置成： 在所述调试模块的模拟调试结束后， 对所述终端 侧应用业务逻辑和所述平台侧应用业务逻辑进行发布；
其中， 所述发布模块是设置成以如下方式对所述终端侧应用业务逻辑和 所述平台侧应用业务逻辑进行发布：
直接将所述终端侧应用业务逻辑部署到终端执行系统中和将所述平台侧 应用业务逻辑部署到平台执行系统中， 或者， 先将所述终端侧应用业务逻辑 和所述平台侧应用业务逻辑处理生成终端侧业务逻辑应用包和平台侧业务逻 辑应用包， 然后将所述终端侧业务逻辑应用包部署到终端执行系统中和将所 述平台侧业务逻辑应用包部署到平台执行系统中。
本发明实施例还提供了一种物联网终端执行系统， 包括：
终端组件模块， 其设置成： 加载终端侧应用业务逻辑所需组件， 并对所 述组件进行执行和维护；
4 181304132
终端解析执行模块， 其设置成： 解析并触发所述终端侧应用业务逻辑， 以执行所述终端侧应用业务逻辑； 以及
终端通信模块， 其设置成： 与本终端执行系统对应的平台进行通信， 将 本终端执行系统执行所述终端侧应用业务逻辑的结果发送给所述平台。
可选地， 所述终端解析执行模块是设置成以如下方式触发所述终端侧应 用业务逻辑：
通过开始节点、 来自平台的消息指令或终端釆集数据， 触发所述终端侧 应用业务逻辑。
可选地， 所述系统还包括：
终端监控模块， 其设置成： 监控本终端执行系统对所述终端侧应用业务 逻辑的执行结果， 并在需要时对所述执行结果进行展示。
本发明实施例还提供了一种物联网平台执行系统， 包括：
平台组件模块， 其设置成： 加载平台侧应用业务逻辑所需组件， 并对所 述组件进行执行和维护；
平台解析执行模块， 其设置成： 解析并触发所述平台侧应用业务逻辑； 以及
平台通信模块， 其设置成： 进行终端与平台之间的通信， 接收所述终端 执行所述终端侧应用业务逻辑的结果。
可选地， 所述平台解析执行模块是设置成以如下方式触发所述平台侧应 用业务逻辑：
通过开始节点或者来自终端的消息指令，触发所述平台侧应用业务逻辑。 可选地， 所述系统还包括：
平台监控模块， 其设置成： 通过所述平台通信模块接收或者导入终端监 控包， 获取所述终端侧应用业务逻辑的执行结果， 并在需要时对所述执行结 果进行展示。
本发明实施例的有益效果说明如下：
1、本发明实施例中， 平台侧和终端侧的所有应用业务逻辑流程均在编排
5 181304132
区域进行统一编排， 使得物联网应用业务逻辑能够直接一体化开发， 不需区 分是终端侧应用业务逻辑还是平台侧应用业务逻辑， 提高了开发效率。
2、 本发明实施例中， 对编排好的应用业务逻辑流程进行统一模拟调试， 调试通过后可以直接在终端侧和平台侧分别进行部署，而不需反复进行联调， 省去了上线部署后的联调步骤，降低物联网应用平台侧和终端侧的联调时间， 扩展终端在业务运行期间的运行、 升级、 更新、 调测等能力。
3、物联网应用业务逻辑在终端和平台分别运行时， 能够通过监控功能将 平台侧与终端侧的业务逻辑执行情况展示出来， 方便了对业务逻辑运行情况 的跟踪和问题排查， 确保系统长期稳定运行。
附图概述
图 1是相关技术中物联网应用方案的系统图。
图 2是本发明实施例的物联网终端应用一体化生成方法的流程图。
图 3是本发明实施例的物联网终端应用一体化生成系统的结构框图。 图 4是本发明实施例中的物联网应用方案的系统图。
图 5是本发明实施例中组件模块的结构示意图。
图 6是本发明实施例中编排模块的结构示意图。
图 7为本发明实施例中针对终端侧应用业务逻辑的解析流程图。
图 8为本发明实施例中针对平台侧应用业务逻辑的解析流程图
图 9是本发明实施例中的调试模块的结构示意图。
图 10是本发明实施例中模拟调试前的解析流程图
图 11是本发明实施例中的发布模块的结构示意图。
图 12是本发明实施例中的物联网终端执行系统的结构图。
图 13-15是本发明实施例中的物联网终端执行系统各功能模块的示意图。 图 16是本发明实施例中的物联网平台执行系统的结构图。
图 17和 18是本发明实施例中的物联网平台执行系统各功能模块的示意
6 181304132
本发明的较佳实施方式
以下结合附图对本发明实施例进行详细说明。 应当理解， 在不冲突的情 况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
如图 2所示， 图 2为本发明实施例的物联网终端应用一体化生成方法的 流程图， 包括如下步骤：
步骤 S101 , 提供物联网终端应用所需要的终端组件和平台组件。
步骤 S102, 对所述终端组件和所述平台组件进行编排以形成一个应用业 务流程， 编排结束后， 生成平台侧应用业务逻辑和终端侧应用业务逻辑。
利用上述方法对终端组件和平台组件进行统一编排， 形成统一的应用业 务流程， 编排完成后再自动生成适用于终端侧和平台侧的应用业务逻辑， 使 得物联网应用业务逻辑能够直接一体化开发， 不需区分是终端侧应用业务逻 辑还是平台侧应用业务逻辑， 开发效率高。
在生成终端侧应用业务逻辑和平台侧应用业务逻辑之后， 在两者之间建 立信息通道， 以对两者进行调试。 调试完成后对终端侧应用业务逻辑和平台 侧应用业务逻辑进行发布， 将终端侧应用业务逻辑部署于终端执行系统以及 将平台侧应用业务逻辑部署于平台执行系统。
这样处理的好处是， 由于在部署前已调试到理想的状态， 所以在正式上 线之前不需再次调试， 省去了原先的联调步骤， 降低物联网应用平台侧和终 端侧的联调时间， 提升了竟争力。
如图 3所示， 图 3是本发明实施例的物联网终端应用一体化生成系统的 结构框图， 该系统包括组件模块 10、 编排模块 11、 调试模块 12和发布模块 13 , 其中， 组件模块 10设置成： 提供物联网终端应用所需要的终端组件和对 应的平台组件； 编排模块 11设置成： 对所述终端组件和所述平台组件进行编 排以形成一个应用业务流程， 编排结束后， 生成平台侧应用业务逻辑和终端 侧应用业务逻辑； 调试模块 12设置成： 在所述平台侧应用业务逻辑和终端侧 应用业务逻辑之间建立信息通道， 以对所述平台侧应用业务逻辑和所述终端
7 181304132
侧应用业务逻辑进行模拟调试； 以及发布模块 13设置成： 在调试模块 12的 模拟调试结束后， 对平台侧应用业务逻辑和终端侧应用业务逻辑进行发布。
利用该系统对终端侧应用业务逻辑和平台侧应用业务逻辑进行统一编排 开发和调试， 发布终端侧应用业务逻辑和平台侧应用业务逻辑并部署于各自 的执行环境， 实现了物联网终端应用的一体化开发。
如图 4所示， 图 4为本发明实施例的物联网应用系统的整体结构框图， 上半部分为本实施例使用的一体化生成系统，包括组件模块 10、编排模块 11、 调试模块 12和发布模块 13 , 下半部分为终端侧应用业务逻辑和平台侧应用 业务逻辑的执行环境， 包括物联网终端执行系统和物联网平台执行系统。
利用图 4所示的本实施例的物联网应用系统， 可实现终端侧应用业务逻 辑和平台侧应用业务逻辑的一体化开发和调试， 调试通过后， 将两部分应用 业务逻辑分别部署于终端执行系统和平台执行系统， 即可直接上线使用。
组件模块 10设置成： 提供物联网终端应用所需要的终端组件和平台组 件， 并对组件进行注册、 加载和管理等， 这里所述的组件是在应用逻辑中调 用的最小功能单元， 具备唯一的组件标识（Identifier, ID )。 在本发明实施例 中， 所述的组件按属性分为终端组件和平台组件两类， 其中， 终端组件就是 仅在终端侧运行的组件， 平台组件就是仅在平台侧运行的组件， 由组件模块 10对终端组件和平台组件执行注册、 加载和管理等动作。 如图 5所示， 组件 模块 10包括组件上传单元 101、 组件注册单元 102、 组件存储单元 103、 组 件解释单元 104和组件升级单元 105。
所述组件上传单元 101设置成： 接收用户上传的组件包， 并险证组件包 的格式、 大小， 验证通过后将组件包上传至组件存储单元 103 , 并通知组件 注册单元 102进行组件包的加载工作。 所述组件包是满足所述组件的一定规 则的文件集合， 通常是一个压缩包的形式。
所述组件注册单元 102设置成： 接收到组件上传单元 101的组件包加载 通知消息后， 从组件存储单元 103中读取需要注册的组件包。 根据组件描述 规则， 对组件包中的文件集合进行合法性验证， 所述文件集合包括： 组件元
8 181304132
数据、 组件方法执行文件、 以及组件方法依赖文件。 所述合法性验证包括： 对执行方法、 输入参数、 以及输出参数的验证。 需要注册的组件包验证通过 后， 将组件包转换成组件内部的组织形式。 在组件存储单元 103中， 保存组 件的元数据、 执行文件、 以及依赖文件。
所述组件存储单元 103能够保存组件上传单元 101验证通过后的组件包， 并能够保存组件注册单元 102验证通过后的组件元数据、组件方法执行文件。
所述组件解释单元 104能够对所述组件的元数据进行解析， 供所述编排 模块 11使用； 能够对所述组件的执行文件和依赖文件进行加载， 供所述调试 模块 12使用； 以及能够对批量的组件方法依赖文件进行处理， 过滤出最小依 赖文件集合， 供发布模块 13使用。
所述组件升级单元 105能够替换具有相同组件 ID的组件。组件注册单元 102的组件包通过验证后， 组件升级单元 105首先根据组件 ID判断是否是相 同的组件， 若是， 则将组件存储单元 103中原组件的元数据、 执行文件、 以 及依赖文件移除， 将原组件包移除。 再通知组件注册单元 102继续进行对组 件包的转换。
编排模块 11设置成： 在线编排物联网应用业务逻辑流程。 编排时， 不区 分是平台侧业务逻辑还是终端侧业务逻辑， 所有业务逻辑流程均在编排区域 可视化地进行编排。 在编排区域出现的所有节点、 组件和触发服务， 统称为 元素， 其中， 除结束节点和触发服务外， 所有元素只有一个输入连接线； 所 有元素可以有多个输出连接线。 其中， 将开始节点抽象成一个只有输出的元 素； 将结束节点抽象成一个只有输入的元素； 其他节点、 触发服务、 组件、 以及子业务等， 都可以抽象成同时包含输入和输出的元素。
如图 6所示， 编排模块 11包括节点提供单元 111、 组件展现单元 112、 触发服务单元 113、 子业务单元 114、 编排绘制单元 115、 编排解析单元 116、 编排生成单元 117和编排存储单元 118。
所述节点提供单元 111提供应用业务逻辑的最基本的编排元素， 包括： 开始节点、 结束节点、 表达式节点、 运算节点、 以及通信节点。 其中， 一个 业务逻辑通过一个开始节点触发， 以一个结束节点完成。 表达式节点定义业 务逻辑流程中的变量。 运算节点对业务逻辑流程中的变量进行逻辑运算， 所
9 181304132
述运算包括： 四则运算、 产生随机数、 获取当前时间、 以及字符串操作等。 通信节点隐含在业务逻辑流程中， 只有在调试或发布时才被模拟或生成。 另 夕卜， 所述节点提供单元 111是系统内置的， 除开始节点和结束节点有终端类 和平台类的区别之外， 其它节点都是通用的， 即， 对于其它节点不区分是终 端类还是平台类， 其它节点的类型为通用类。
所述组件展现单元 112设置成： 展现所述组件模块 10所管理的组件。 所 述组件展现单元 112能够调用组件模块 10中的组件解释单元 104来展示组件 的元数据。 组件展现单元 112可展现组件的增加、 删除和升级等状态。
所述触发服务单元 113设置成： 扩展应用业务逻辑的触发条件， 对组件 进行封装， 形成触发服务。 当触发服务接收到相关参数后， 可以立即触发业 务逻辑流程， 启动组件运行。 另外， 由于组件有终端侧、 平台侧的类型区分， 因此所述触发服务也存在终端侧、 平台侧的区分。
所述子业务单元 114在一个业务逻辑流程中调用了另外一个业务逻辑流 程， 被调用方称为调用方的子业务。 所述子业务单元 114设置成： 展示在组 件存储单元 103中已存在的业务， 以供编排绘制单元 115在编排区域进行编 排。
所述编排绘制单元 115设置成： 提供业务逻辑流程的编排区域， 对节点、 组件和触发服务在编排区域进行编排和图形化展示， 并通过流程连接线将节 点、 组件、 以及触发服务连接起来， 以组成一个完整的业务逻辑流程。 例如， 编排绘制单元 115可将子业务作为一个特殊节点， 在编排区域进行编排， 通 过流程连接线将子业务和与其相关的节点、 组件、 以及触发服务连接起来， 以组成完整的业务逻辑流程。
此外， 所述编排绘制单元 115还设置成： 对节点、 组件、 触发服务和子 业务进行维护。
对于节点的维护： 编排绘制单元 115对节点在业务逻辑流程中的名称进 行命名； 其中， 对于表达式节点， 编排绘制单元 115能够定义业务逻辑流程 所需变量； 对于所述运算节点， 编排绘制单元 115能够选择表达式定义的各 类变量， 并能够选择运算节点的各类逻辑运算。
10 181304132
对于组件的维护： 编排绘制单元 115对组件在业务逻辑流程中的名称进 行命名； 以及绑定组件的输入参数到表达式节点定义的变量上， 将组件的输 出参数赋值到表达式节点定义的变量上。
对于触发服务的维护： 编排绘制单元 115对触发服务在业务逻辑流程中 的名称进行命名； 以及将触发服务的输出参数赋值到表达式节点定义的变量 上。
对于子业务的维护： 编排绘制单元 115对子业务在业务逻辑流程中的名 称进行命名； 以及绑定子业务的输入参数到表达式节点定义的变量上， 将子 业务的输出参数赋值到表达式节点定义的变量上。
所述编排解析单元 116能够按流程连接线方向对所述编排绘制单元 115 生成的统一应用业务逻辑流程进行顺序解析，并根据对元素类型的解析判断， 生成终端侧应用业务逻辑和平台侧应用业务逻辑。
如图 7所示， 图 7为本发明实施例中针对终端侧应用业务逻辑的解析流 程图， 所述编排解析单元 116以连接线方向进行顺序解析， 先判断当前元素 的类型。 若当前元素类型是终端类， 则直接将该元素的信息通知所述编排生 成单元 117。 若当前元素类型是平台类， 且是第一次解析到平台类元素， 则 生成一个终端类通信节点， 将该节点和当前元素通知给所述编排生成单元 117 ,所述通信节点的消息接口是根据流程连接线前一个终端类元素的消息类 型来确定； 若元素类型是平台类， 但不是第一次解析到平台类元素， 则跳过 该元素继续解析。 若当前元素类型是通用类， 则根据流程连接线前一个元素 的类型， 判定当前元素的生成类型。 若前一个元素类型是终端类， 则将当前 元素通知给所述编排生成单元 117; 若前一个元素类型是平台类， 则跳过该 元素继续解析； 若前一个元素类型是通用类， 则继续往流程连接线的再前一 个元素查找判断。
当整个业务逻辑流程的所有元素解析完成后， 所述编排生成单元 117根 据解析结果生成终端侧应用业务逻辑， 存入编排存储单元 118。
如图 8所示， 图 8为本发明实施例中的针对平台侧应用业务逻辑的解析 流程图， 所述编排解析单元 116以连接线方向进行顺序解析。 若元素类型是 平台类， 则直接将该元素通知给所述编排生成单元 117。 若元素类型是终端
11 181304132
类， 且是第一次解析到终端类元素， 则生成一个平台类通信节点， 将该节点 通知给所述编排生成单元 117 , 所述通信节点的消息接口， 是根据流程连接 线前一个平台类元素的消息类型来确定； 若元素类型是终端类， 但不是第一 次解析到终端类元素， 则跳过该元素继续解析。 若元素类型是通用类， 则根 据流程连接线前一个元素的类型， 判定当前元素的生成类型。 若前一个元素 类型是平台类， 则将当前元素通知给所述编排生成单元 117; 若前一个元素 类型是终端类， 则跳过该元素继续解析； 若前一个元素类型是通用类， 则继 续往流程连接线的再前一个元素查找判断。
当整个业务逻辑流程的所有元素解析完成后， 所述编排生成单元 117根 据解析结果生成平台侧应用业务逻辑， 存入编排存储单元 118。
所述编排存储单元 118设置成： 保存所述编排生成单元 117生成的终端 侧应用业务逻辑和平台侧应用业务逻辑的元数据， 所述元数据包括： 业务逻 辑流程描述信息、 元素在编排区域的相对位置信息和元素自身信息。
此外， 若当前元素属于子业务， 则所述编排解析单元 116读取子业务逻 辑流程的各种元数据， 根据子业务逻辑流程描述信息， 启动对该子业务逻辑 流程的解析， 解析方法同上。
调试模块 12设置成：对终端侧应用业务逻辑和平台侧应用业务逻辑进行 模拟调试。 如图 9所示， 调试模块 12包括： 解析执行单元 121、 平台模拟单 元 122、 终端模拟单元 123、 通信模拟单元 124和展示单元 125。
所述解析执行单元 121从编排模块 11的编排存储单元 118中读取终端侧 应用业务逻辑和平台侧应用业务逻辑的各种元数据， 根据业务逻辑流程描述 信息启动针对两部分应用业务逻辑的模拟调试。 若业务逻辑流程是以开始节 点启动， 则立即触发启动调试过程； 若业务逻辑流程是以触发服务启动， 则 在用户输入触发服务参数后触发启动调试过程。 解析执行单元 121可解析各 个元素在业务逻辑流程中的相对位置， 发送给展示单元 125进行显示； 解析 执行单元 121还解析各个元素， 通知所述终端模拟单元 123进行模拟， 接收 所述终端模拟单元 123的返回结果， 并将返回结果通知给所述展示单元 125; 并且， 解析执行单元 121还解析各个元素， 通知所述平台模拟单元 122进行 模拟， 接收所述平台模拟单元 122的返回结果， 并将返回结果通知给所述展
12 181304132
示单元 125。
所述平台模拟单元 122能够模拟平台侧环境的真实执行情况， 能够对表 达式节点、 运算节点、 以及平台侧组件进行模拟执行， 并返回执行结果。
所述终端模拟单元 123能够模拟终端侧环境的真实执行情况， 能够对表 达式节点、 运算节点、 以及终端侧组件进行模拟执行， 并返回执行结果。
所述通信模拟单元 124能够模拟终端侧与平台侧之间的通信协议、 通信 接口。 所述通信协议、 通信接口均为在物联网应用中终端和平台预先一致协 定的。 当通信模拟单元 124接收到终端侧向平台侧的通信模拟请求时， 模拟 终端侧向平台侧的通信接口； 当通信模拟单元 124接收到平台侧向终端侧的 通信模拟请求时， 模拟平台侧向终端侧的通信接口。
所述展示单元 125能够读取应用业务逻辑流程的各种元素在编排区域的 相对位置， 在调试区域进行展示； 还能够接收终端模拟单元 123、 平台模拟 单元 122、 以及通信模拟单元 124的返回结果， 根据返回的执行结果为正常、 异常或未执行等情况， 分别对该元素在调试区域置不同的颜色以示区分。 然 后根据执行结果对终端侧和平台侧的应用业务逻辑做必要的调整， 以使两者 相匹配。
图 10为本发明实施例中的模拟调试的流程图，所述解析执行单元 121解 析各个元素， 该方法为： 判断当前元素的类型。 如图 10所示， 若当前元素类 型是通用类， 则根据流程连接线前一个元素的类型来判定当前元素对应的模 拟执行单元； 其中， 若前一个元素类型是平台类， 则通知所述平台模拟单元 进行模拟， 若前一个元素类型是终端类， 则通知所述终端模拟单元进行模拟； 若前一个元素类型是通用类 ,则继续向流程连接线的再前一个元素查找判断。
如图 10所示， 若当前元素类型是终端类， 则根据流程连接线前一个元素 的类型， 判定当前元素的模拟执行单元。 若前一个元素类型是终端类， 则直 接通知所述终端模拟单元进行模拟； 若前一个元素类型是平台类， 则先通知 通信模拟单元进行模拟， 接收通信模拟结果返回结果， 并将返回结果通知给 所述展示单元， 之后再通知所述终端模拟单元进行模拟； 若前一个元素类型 是通用类， 则继续往流程连接线的再前一个元素查找判断。
13 181304132
如图 10所示， （iii )若当前元素类型是平台类， 则根据流程连接线前一 个元素的类型， 判定当前元素的模拟执行单元。 若前一个元素类型是平台类， 则直接通知所述平台模拟单元进行模拟； 若前一个元素类型是终端类， 则先 通知通信模拟单元进行模拟， 接收通信模拟结果返回结果， 并将返回结果通 知给所述展示单元， 之后再通知所述平台模拟单元进行模拟； 若前一个元素 类型是通用类， 则继续往流程连接线的再前一个元素查找判断。
此外， 若当前元素属于子业务， 则读取子业务逻辑流程的元数据， 根据 子业务逻辑流程描述信息， 启动对该子业务逻辑流程的调试。
发布模块 13设置成：对已保存的终端侧应用业务逻辑和平台侧应用业务 逻辑进行发布。如图 11所示，发布模块 13包括读取单元 131和发布单元 132。
所述读取单元 131能够从所述编排模块 11的编排存储单元 118中读取终 端侧应用业务逻辑和平台侧应用业务逻辑的元数据。
所述发布单元 132将所述读取单元 131发送的终端侧应用业务逻辑和平 台侧应用业务逻辑分别部署到终端执行环境和平台执行环境中， 部署完毕后 上线使用。 可以直接将两部分逻辑相应地部署到终端执行环境和平台执行环 境中， 也可以先对两部分逻辑进行处理， 生成终端侧业务逻辑应用包和平台 侧业务逻辑应用包， 然后再进行发布部署。 这里， 终端侧业务逻辑应用包和 平台侧业务逻辑应用包合起来即是整个物联网应用的业务逻辑。
发布的时候， 终端侧应用业务逻辑针对的是终端执行系统， 这个终端执 行系统可以在不同的终端系统上进行安装， 如， 苹果操作系统 /安卓（iphone Operation System ( iOS ) /Android )等； 平台应用业务逻辑针对的是平台执行 系统， 这个平台执行系统可以在不同的平台系统上进行安装， 如， Windows/Linux等。
本发明实施例还提供了一种物联网终端执行系统， 如图 12所示， 所述系 统包括： 终端基础模块 20、 终端组件模块 21、 终端解析执行模块 22、 终端 通信模块 23和终端监控模块 24。
终端基础模块 20设置成： 提供接口以接收终端侧应用业务逻辑， 并进行 数据转换；终端组件模块 21设置成：加载所述终端侧应用业务逻辑所需组件，
14 181304132
并对所述组件进行执行和维护； 终端解析执行模块 22设置成： 解析并触发所 述终端侧应用业务逻辑， 启动该业务逻辑流程； 终端通信模块 23设置成： 进 行终端与平台之间的通信， 将终端执行所述终端侧应用业务逻辑的结果发送 给平台； 以及终端监控模块 24设置成： 监控对于终端侧应用业务逻辑的执行 情况， 并将执行结果导出进行显示。
其中，终端侧应用业务逻辑可提供三种触发方式： ( 1 )以开始节点触发、 ( 2 ) 以平台的消息指令触发以及（3 ) 以终端釆集数据触发。 如果所述终端 侧应用业务逻辑是以开始节点触发， 启动后立即触发； 如果以平台的消息指 令触发， 接收到平台的消息指令后触发； 以及如果以终端釆集数据触发， 在 接收到触发服务的终端侧相关参数后触发。
如图 13所示， 图 13为本发明实施例的终端基础模块 20, 包括： 接口单 元 201、 转换单元 202和访问单元 203。
所述接口单元 201能够向所有元素提供统一的终端访问接口， 接收接口 调用方发送的数据， 并根据接口类型在下行发送数据至所述转换单元； 以及 能够接收所述转换单元 202的触发数据， 并通知接口调用方接收。
所述转换单元 202能够接收所述接口单元 201下行发送的数据， 根据终 端的操作系统类型， 进行数据流转码， 并通过访问单元 203访问终端设备， 或者访问平台执行系统， 使触发服务具备由终端釆集数据后触发和平台消息 指令触发两种形式； 以及能够通过所述访问单元 203接收终端设备的信息， 对数据流进行转码， 发送给所述接口单元 201。
所述访问单元 203能够在终端操作系统上， 访问终端设备提供的各种功 能并能够与所述转换单元 202通信。
如图 14所示， 图 14为本发明实施例的终端组件模块 21 , 包括： 终端组 件存储单元 211、 终端组件加载单元 212、 终端组件解析单元 213和终端组件 执行单元 214。
所述终端组件存储单元 211保存组件的元数据、 执行文件、 以及依赖文 件。
所述终端组件加载单元 212能够加载在所述一体化应用开发环境中的终
15 181304132
端类组件， 并通过组件 ID对组件进行增加、 删除、 升级； 以及能够将所述组 件在保存在所述终端组件存储单元 211中。
所述终端组件解析单元 213能够解析所述终端组件存储单元 211中的组 件元数据， 并通知所述终端组件执行单元 214运行所述组件。
所述终端组件执行单元 214能够通过所述组件的执行文件、 依赖文件， 运行所述组件的特定功能。 由于所述组件是基于终端的所述终端基础模块 20 进行开发的， 因此， 所述终端组件执行单元 214会将组件数据发送给所述终 端基础模块 20的接口单元 201。
如图 15所示， 图 15为本发明实施例的终端解析执行模块 22, 所述终端 解析执行模块 22设置成： 解析并执行终端侧应用逻辑执行包。 所述终端解析 执行模块 22包括： 终端解析单元 221、 终端节点执行单元 222、 终端组件执 行单元 223。
所述终端解析单元 221能够根据终端侧业务逻辑流程描述信息， 依次解 析各个元素。 若元素是一个节点， 则调用节点执行单元运行， 并接收运行结 果； 若元素是一个组件， 则调用组件执行单元执行， 并接收运行结果。
所述终端解析单元 221设置成： 当该业务逻辑流程是以一个开始节点启 动时， 则立即触发终端侧应用逻辑； 当该业务逻辑流程是以一个终端触发服 务启动时， 则监听所述终端基础模块 20的接口单元 201 , 当有该触发服务的 输入条件并接收到相关参数时触发终端侧应用逻辑。
当启动终端侧执行监控功能时， 所述终端解析单元 221能够将该元素的 信息以及运行结果， 通过所述终端通信模块 23发送给平台执行环境。
所述终端节点执行单元 222能够对节点的逻辑进行执行， 并返回运行结 果。
所述终端组件执行单元 223能够调用所述终端组件模块 21的终端组件解 析单元 213 , 对组件的功能进行执行， 并返回运行结果。
所述终端通信模块 23设置成： 在终端与平台之间进行通信。 所述终端通 信模块 23提供的通信协议、通信接口， 均为终端和平台在物联网应用中一致 协定的。 所述终端通信模块 23在与所述平台执行环境通信时， 使用所述终端
16 181304132
基础模块 20的接口单元 201提供的统一接口。
所述终端监控模块 24设置成： 监控对于终端侧应用业务逻辑的执行情 况， 并将执行结果导出进行显示。 例如， 若终端通信模块 23遇到通信链路异 常， 则所述终端监控模块 24能够緩存终端的执行结果， 以终端监控包的形式 将执行结果导出。
利用上述物联网终端执行系统接收、 解析并执行终端侧应用业务逻辑， 并对执行情况进行监控， 将终端侧应用业务逻辑中的各个组件信息以及运行 结果发送给平台， 实现物联网终端应用。
此外， 本发明实施例还提供了一种物联网平台执行系统， 如图 16所示， 所述系统包括： 平台基础模块 30、 平台组件模块 31、 平台解析执行模块 32、 平台通信模块 33和平台监控模块 34。
平台基础模块 30设置成： 提供接口以接收平台侧应用业务逻辑， 并进行 数据转换； 平台组件模块 31设置成： 加载平台侧应用业务逻辑所需组件， 并 对所述组件进行执行和维护； 平台解析执行模块 32设置成： 解析并触发平台 侧应用业务逻辑； 平台通信模块 33设置成： 进行终端与平台之间的通信， 接 收终端执行所述终端侧应用业务逻辑的结果； 以及平台监控模块 34设置成： 通过所述平台通信模块 33接收或者导入终端监控包，获取终端侧应用业务逻 辑的执行结果并进行展示。
其中， 平台侧应用业务逻辑可提供两种触发方式： （ 1 ) 以开始节点触发 和（2 )以终端的消息指令触发。 如果所述平台侧应用业务逻辑是以开始节点 触发， 则启动后立即触发； 如果所述平台侧应用业务逻辑是以终端的消息指 令触发， 则接收到终端的消息指令后触发所述平台侧应用业务逻辑。
如图 17所示， 所述平台组件模块 31 包括： 平台组件存储单元 311、 平 台组件加载单元 312、 平台组件解析单元 313和平台组件执行单元 314。
所述平台组件存储单元 311保存组件的元数据、 执行文件、 以及依赖文 件。
所述平台组件加载单元 312能够加载在所述一体化应用开发环境中的平 台类组件， 并通过组件 ID对组件进行增加、 删除、 以及升级。 能够将所述组
17 181304132
件保存在所述平台组件存储单元 311中。
所述平台组件解析单元 313能够解析所述平台组件存储单元 311中的组 件元数据， 通知所述平台组件执行单元 314运行所述组件。
所述平台组件执行单元 314能够通过所述组件的执行文件、 依赖文件， 运行所述组件的特定功能。
如图 18所示， 所述平台解析执行模块 32包括： 平台解析单元 321、 平 台节点执行单元 322、 平台组件执行单元 323。
所述平台解析单元 321能够根据平台侧应用业务逻辑的描述信息， 依次 解析各个元素。 若元素是一个节点， 则调用所述平台节点执行单元 322运行， 并接收运行结果； 若元素是一个组件， 则调用平台组件执行单元 323运行， 并接收运行结果。 所述平台解析单元 321将两部分运行结果发送给平台监控 模块 34。
所述平台通信模块 33设置成： 在平台与终端之间进行通信， 当接收到终 端的信息指令后， 可以通过触发服务启动平台侧应用业务逻辑。 所述平台通 信模块 33还接收来自终端的终端侧应用业务逻辑的运行结果，并将运行结果 发送给所述平台监控模块 34。 所述平台通信模块 33提供的通信协议、 通信 接口， 均为平台和终端在物联网应用中一致协定的。
所述平台监控模块 34能够通过所述平台通信模块 33接收或者导入终端 监控包， 获取终端侧应用业务逻辑执行结果， 再结合来自所述平台解析单元 321和所述平台通信模块 33的平台侧应用业务逻辑的执行结果， 在监控区域 以图形化的方式将执行结果展示出来， 对于返回的执行结果正常、 异常、 未 执行等情况， 在监控区域以不同的颜色区分显示。
利用上述物联网平台执行系统， 能够接收终端侧应用业务逻辑的执行结 果， 结合平台侧应用业务逻辑的执行情况， 实现一体化业务逻辑的执行和监 控功能。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读
18 181304132
存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明实施例不限 制于任何特定形式的硬件和软件的结合。
定本发明实施例的实施只局限于这些说明。 对于本发明所属技术领域的普通 技术人员来说， 在不脱离本发明实施例构思的前提下， 还可以做出若干简单 推演或替换， 这些推演或替换都应当视为属于本发明所附权利要求的保护范 围。
工业实用性 本发明实施例中， 提高了开发效率； 降低物联网应用平台侧和终端侧的 联调时间， 扩展终端在业务运行期间的运行、 升级、 更新、 调测等能力； 以 及方便了对业务逻辑运行情况的跟踪和问题排查， 确保系统长期稳定运行。
19 181304132
Claims
1、 一种物联网终端应用一体化生成方法， 包括：
提供所述物联网终端应用所需要的终端组件和平台组件； 以及
对所述终端组件和所述平台组件进行编排以形成一个应用业务流程， 编 排结束后， 生成终端侧应用业务逻辑和平台侧应用业务逻辑。
2、 如权利要求 1所述的方法， 其中，
所述编排在编排区域进行， 编排的对象包括以下元素： 节点、 所述终端 组件、 所述平台组件、 由所述终端组件封装而成的触发服务和由所述平台组 件封装而成的触发服务。
3、 如权利要求 2所述的方法， 其中， 所述生成终端侧应用业务逻辑和平 台侧应用业务逻辑的步骤包括：
根据对元素类型的解析判断， 生成所述终端侧应用业务逻辑和所述平台 侧应用业务逻辑。
4、 如权利要求 1所述的方法， 还包括：
在生成所述终端侧应用业务逻辑和所述平台侧应用业务逻辑之后， 在所 述终端侧应用业务逻辑和所述平台侧应用业务逻辑之间建立通信通道， 以对 所述终端侧应用业务逻辑和所述平台侧应用业务逻辑进行模拟调试。
5、 如权利要求 4所述的方法， 其中， 所述对所述终端侧应用业务逻辑和 所述平台侧应用业务逻辑进行模拟调试的步骤包括：
通过所述通信通道， 模拟所述终端侧应用业务逻辑的运行情况和所述平 台侧应用业务逻辑的运行情况； 以及
根据所述运行情况， 调整所述终端侧应用业务逻辑和所述平台侧应用业 务逻辑。
6、 如权利要求 5所述的方法， 还包括：
在模拟所述终端侧应用业务逻辑的运行情况和所述平台侧应用业务逻辑 的运行情况之前， 判断当前元素的类型， 当所述当前元素为终端类时， 使用 所述终端侧应用业务逻辑进行模拟； 当所述当前元素为平台类时， 使用所述
20 181304132
平台侧应用业务逻辑进行模拟； 以及当所述当前元素为通用类时， 根据流程 连接线前一个元素的类型进行判断。
7、 如权利要求 4所述的方法， 还包括：
在所述模拟调试完成后， 对所述终端侧应用业务逻辑和所述平台侧应用 业务逻辑进行发布；
其中， 所述对所述终端侧应用业务逻辑和所述平台侧应用业务逻辑进行 发布的步骤包括：
直接将所述终端侧应用业务逻辑部署到终端执行系统中和将所述平台侧 应用业务逻辑部署到平台执行系统中， 或者， 先将所述终端侧应用业务逻辑 和所述平台侧应用业务逻辑处理生成终端侧业务逻辑应用包和平台侧业务逻 辑应用包， 然后将所述终端侧业务逻辑应用包部署到终端执行系统中和将所 述平台侧业务逻辑应用包部署到平台执行系统中。
8、 一种物联网终端应用一体化生成系统， 包括：
组件模块， 其设置成： 提供所述物联网终端应用所需要的终端组件和平 台组件； 以及
编排模块， 其设置成： 对所述终端组件和所述平台组件进行编排以形成 一个应用业务流程， 编排结束后， 生成终端侧应用业务逻辑和平台侧应用业 务逻辑。
9、 如权利要求 8所述的系统， 其中，
所述编排模块提供编排区域， 所述编排在所述编排区域中进行， 编排的 对象包括以下元素： 节点、 所述终端组件、 所述平台组件、 由所述终端组件 封装而成的触发服务和由所述平台组件封装而成的触发服务。
10、 如权利要求 9所述的系统， 其中，
所述编排模块是设置成以如下方式生成终端侧应用业务逻辑和平台侧应 用业务逻辑：
根据对元素类型的解析判断， 生成所述终端侧应用业务逻辑和所述平台 侧应用业务逻辑。
21 181304132
11、 如权利要求 8所述的系统， 还包括：
调试模块， 其设置成： 在所述终端侧应用业务逻辑平台和所述侧应用业 务逻辑之间建立信息通道， 以对所述终端侧应用业务逻辑和所述平台侧应用 业务逻辑进行模拟调试。
12、 如权利要求 11所述的系统， 其中，
所述调试模块是设置成以如下方式对所述终端侧应用业务逻辑和所述平 台侧应用业务逻辑进行模拟调试：
通过所述通信通道， 模拟所述终端侧应用业务逻辑的运行情况和所述平 台侧应用业务逻辑的运行情况， 并根据所述运行情况， 调整所述终端侧应用 业务逻辑和所述平台侧应用业务逻辑。
13、 如权利要求 12所述的系统， 其中，
所述调试模块还设置成： 在模拟所述终端侧应用业务逻辑的运行情况和 所述平台侧应用业务逻辑的运行情况之前， 判断当前元素的类型， 当所述当 前元素为终端类时， 使用所述终端侧应用业务逻辑进行模拟； 当所述当前元 素为平台类时， 使用所述平台侧应用业务逻辑进行模拟； 以及当所述当前元 素为通用类时， 根据流程连接线前一个元素的类型进行判断。
14、 如权利要求 11所述的系统， 还包括：
发布模块， 其设置成： 在所述调试模块的模拟调试结束后， 对所述终端 侧应用业务逻辑和所述平台侧应用业务逻辑进行发布；
其中， 所述发布模块是设置成以如下方式对所述终端侧应用业务逻辑和 所述平台侧应用业务逻辑进行发布：
直接将所述终端侧应用业务逻辑部署到终端执行系统中和将所述平台侧 应用业务逻辑部署到平台执行系统中， 或者， 先将所述终端侧应用业务逻辑 和所述平台侧应用业务逻辑处理生成终端侧业务逻辑应用包和平台侧业务逻 辑应用包， 然后将所述终端侧业务逻辑应用包部署到终端执行系统中和将所 述平台侧业务逻辑应用包部署到平台执行系统中。
15、 一种物联网终端执行系统， 包括：
终端组件模块， 其设置成： 加载终端侧应用业务逻辑所需组件， 并对所
22 181304132
述组件进行执行和维护；
终端解析执行模块， 其设置成： 解析并触发所述终端侧应用业务逻辑， 以执行所述终端侧应用业务逻辑； 以及
终端通信模块， 其设置成： 与本终端执行系统对应的平台进行通信， 将 本终端执行系统执行所述终端侧应用业务逻辑的结果发送给所述平台。
16、 如权利要求 15所述的系统， 其中， 所述终端解析执行模块是设置成 以如下方式触发所述终端侧应用业务逻辑：
通过开始节点、 来自平台的消息指令或终端釆集数据， 触发所述终端侧 应用业务逻辑。
17、 如权利要求 15所述的系统， 还包括：
终端监控模块， 其设置成： 监控本终端执行系统对所述终端侧应用业务 逻辑的执行结果， 并在需要时对所述执行结果进行展示。
18、 一种物联网平台执行系统， 包括：
平台组件模块， 其设置成： 加载平台侧应用业务逻辑所需组件， 并对所 述组件进行执行和维护；
平台解析执行模块， 其设置成： 解析并触发所述平台侧应用业务逻辑； 以及
平台通信模块， 其设置成： 进行终端与平台之间的通信， 接收所述终端 执行所述终端侧应用业务逻辑的结果。
19、 如权利要求 18所述的系统， 其中， 所述平台解析执行模块是设置成 以如下方式触发所述平台侧应用业务逻辑：
通过开始节点或者来自终端的消息指令，触发所述平台侧应用业务逻辑。
20、 如权利要求 18所述的系统， 还包括：
平台监控模块， 其设置成： 通过所述平台通信模块接收或者导入终端监 控包， 获取所述终端侧应用业务逻辑的执行结果， 并在需要时对所述执行结 果进行展示。
23 181304132
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP13854976.1A EP2908498B1 (en) | 2012-11-14 | 2013-08-14 | Integrated application generating system and method for internet of things terminal |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210456746.4A CN103812905B (zh) | 2012-11-14 | 2012-11-14 | 一种物联网终端应用一体化生成系统和方法 |
| CN201210456746.4 | 2012-11-14 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2014075471A1 true WO2014075471A1 (zh) | 2014-05-22 |
Family
ID=50709103
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2013/081430 WO2014075471A1 (zh) | 2012-11-14 | 2013-08-14 | 一种物联网终端应用一体化生成系统和方法 |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP2908498B1 (zh) |
| CN (2) | CN103812905B (zh) |
| WO (1) | WO2014075471A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110865852A (zh) * | 2019-11-19 | 2020-03-06 | 北京字节跳动网络技术有限公司 | 网页组件的加载方法、装置、电子设备、及存储介质 |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106534270A (zh) * | 2016-10-21 | 2017-03-22 | 上海庆科信息技术有限公司 | 一种物联网模拟系统 |
| CN111625443B (zh) * | 2019-02-28 | 2023-04-18 | 阿里巴巴集团控股有限公司 | 一种压力测试方法、装置、设备和存储介质 |
| CN113872820B (zh) * | 2020-06-30 | 2023-05-05 | 中国电信股份有限公司 | 物联网业务仿真方法、系统和相关设备 |
| CN113220283A (zh) * | 2021-05-10 | 2021-08-06 | 国网陕西省电力公司信息通信公司 | 一种基于云编排的物联app开发系统 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101872448A (zh) * | 2010-06-23 | 2010-10-27 | 魏强 | 利用手机二维条形码的石油销售客户关系管理系统和方法 |
| CN102271156A (zh) * | 2011-07-20 | 2011-12-07 | 武汉爱迪智能工程有限公司 | 基于物联网的数据共享服务系统 |
| CN102497677A (zh) * | 2011-11-29 | 2012-06-13 | 山东中创软件工程股份有限公司 | 一种物联网业务处理系统及方法 |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6266709B1 (en) * | 1996-07-01 | 2001-07-24 | Sun Microsystems, Inc. | Object-oriented system, method and article of manufacture for a client-server failure reporting process |
| EP0825506B1 (en) * | 1996-08-20 | 2013-03-06 | Invensys Systems, Inc. | Methods and apparatus for remote process control |
| CN101299862B (zh) * | 2008-06-11 | 2011-10-05 | 中国电信股份有限公司 | 一种电信业务生成环境系统 |
| US8495565B2 (en) * | 2009-01-09 | 2013-07-23 | Nec Corporation | Service providing apparatus, service providing system, service providing method, and storage medium |
| CN101557297B (zh) * | 2009-05-14 | 2011-06-22 | 中兴通讯股份有限公司 | 一种基于互联网的开放式电信业务生成系统及方法 |
| CN101902756B (zh) * | 2009-05-27 | 2013-12-11 | 中兴通讯股份有限公司 | M2m业务平台及其工作方法 |
| US9063743B2 (en) * | 2010-11-23 | 2015-06-23 | Sap Se | Model-based programming, configuration, and integration of networked embedded devices |
-
2012
- 2012-11-14 CN CN201210456746.4A patent/CN103812905B/zh active Active
- 2012-11-14 CN CN201710374259.6A patent/CN107122307B/zh active Active
-
2013
- 2013-08-14 EP EP13854976.1A patent/EP2908498B1/en active Active
- 2013-08-14 WO PCT/CN2013/081430 patent/WO2014075471A1/zh active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101872448A (zh) * | 2010-06-23 | 2010-10-27 | 魏强 | 利用手机二维条形码的石油销售客户关系管理系统和方法 |
| CN102271156A (zh) * | 2011-07-20 | 2011-12-07 | 武汉爱迪智能工程有限公司 | 基于物联网的数据共享服务系统 |
| CN102497677A (zh) * | 2011-11-29 | 2012-06-13 | 山东中创软件工程股份有限公司 | 一种物联网业务处理系统及方法 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP2908498A4 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110865852A (zh) * | 2019-11-19 | 2020-03-06 | 北京字节跳动网络技术有限公司 | 网页组件的加载方法、装置、电子设备、及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103812905A (zh) | 2014-05-21 |
| EP2908498A1 (en) | 2015-08-19 |
| CN107122307B (zh) | 2021-01-22 |
| CN103812905B (zh) | 2017-10-24 |
| CN107122307A (zh) | 2017-09-01 |
| EP2908498B1 (en) | 2017-07-26 |
| EP2908498A4 (en) | 2016-02-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101908467B1 (ko) | 가시화된 네트워크 운영 및 유지를 위한 방법 및 장치 | |
| WO2014075471A1 (zh) | 一种物联网终端应用一体化生成系统和方法 | |
| CN107241315B (zh) | 银行网关接口的接入方法、装置及计算机可读存储介质 | |
| CN108228444B (zh) | 一种测试方法和装置 | |
| CN110750458A (zh) | 大数据平台测试方法、装置、可读存储介质及电子设备 | |
| WO2016082476A1 (zh) | 业务测试方法及装置 | |
| US20220237111A1 (en) | Distributed immutable data object testing | |
| CN111258913A (zh) | 算法自动测试方法、装置、计算机系统及可读存储介质 | |
| CN110119350A (zh) | 软件开发工具包测试方法、装置和设备及计算机存储介质 | |
| CN110196804B (zh) | 业务的测试方法和装置、存储介质、电子装置 | |
| WO2008003764A2 (en) | A method and a system for software testing | |
| CN111352778B (zh) | 网络的仿真处理方法、装置、电子设备及存储介质 | |
| Krishna et al. | Rigorous design and deployment of IoT applications | |
| WO2017084388A1 (zh) | 一种网络巡检方法及装置 | |
| CN102752770A (zh) | 一种对业务系统进行巡检的方法及装置 | |
| WO2017113848A1 (zh) | 测试用例的测试方法及测试平台、模拟测试设备 | |
| US9329960B2 (en) | Methods, systems, and computer readable media for utilizing abstracted user-defined data to conduct network protocol testing | |
| CN101969442B (zh) | 基于进程运行环境感知与迁移的网络模拟框架实现方法 | |
| Na et al. | Extension and application based on robot testing framework | |
| CN111737130B (zh) | 公有云多租户认证服务测试方法、装置、设备及储存介质 | |
| CN112306845A (zh) | 一种并发测试方法、装置、设备及介质 | |
| CN111082984A (zh) | 模拟登录网络设备进行命令行交互的方法和装置 | |
| CN115373696B (zh) | 软件资源生成的低代码配置方法、系统、设备及存储介质 | |
| CN103442249B (zh) | 视频会议系统仿真方法和平台 | |
| CN111984523B (zh) | 消息处理任务测试方法、装置、系统、设备及介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13854976 Country of ref document: EP Kind code of ref document: A1 |
|
| REEP | Request for entry into the european phase |
Ref document number: 2013854976 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2013854976 Country of ref document: EP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |