CN111930372B - Service arrangement solution method and system realized through draggable flow chart - Google Patents
Service arrangement solution method and system realized through draggable flow chart Download PDFInfo
- Publication number
- CN111930372B CN111930372B CN202010784750.8A CN202010784750A CN111930372B CN 111930372 B CN111930372 B CN 111930372B CN 202010784750 A CN202010784750 A CN 202010784750A CN 111930372 B CN111930372 B CN 111930372B
- Authority
- CN
- China
- Prior art keywords
- node
- service flow
- service
- template
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- 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
- G06F8/35—Creation or generation of source code model driven
Abstract
The invention discloses a service arrangement solution method and a system realized by a draggable flow chart, belonging to the technical field of flow image processing and comprising the following steps: s1: generating a service flow node; s2: associating service flow nodes; s3: editing basic information of the nodes; s4: releasing a service flow template; s5: and adding service flow node resources. In step S1, the service flow node information includes a service flow template ID, a service flow node type, and a service flow node name. The service process arrangement is visualized through the jsPlumb drawing component, so that the service process arrangement is simplified, and the operation and use difficulty is reduced; and the service flow information is generated into an apache camel routing rule in an xml format, so that the gateway can call corresponding service resources, and the method is worthy of popularization and use.
Description
Technical Field
The invention relates to the technical field of process image processing, in particular to a service arrangement solution method and a system realized by a draggable flow chart, which can visualize the arrangement image of a service flow and reduce the use difficulty of flow design.
Background
With the rapid development of the internet, the progress of the internet networking of the system is accelerated, and the demand of telecommunication operators for service integration systems capable of providing personalized functions is increasing, and the standards are also increasing. The interface platform can clear up the integration relation between systems in the same layer and the integration relation between the systems and other external systems, solve the problem of interface expansion after the demand of interface services is increased, realize the management in the aspects of unified and centralized registration, arrangement, monitoring and the like of the interface services, and realize the combing, packaging, combination, sharing and multiplexing of the services.
However, in the prior art, service integration systems such as an interface platform adopt a form input mode in service flow arrangement, so that service flow processing is not visual and clear enough, and the operation is complex. Meanwhile, the service process is privatized, and a service process template cannot be formed, so that the reusability of the service process is reduced. Therefore, a service arrangement solution method and system realized by a draggable flowchart are provided.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: how to solve the problems of insufficient intuition and clarity, complex operation, low reusability and the like in the conventional service flow arrangement, and provides a service arrangement solution method realized by a draggable flow diagram.
The invention solves the technical problems through the following technical scheme, and the invention comprises the following steps:
s1: service flow node generation
Generating an instance by using a jsPlumb drawing component when a browser window is loaded, and drawing and generating a service flow chart; newly building a service flow template, selecting a service flow node type, dragging a node generated by a vuedragable dragging component to a canvas, triggering a makeSource and makeTarget parameter method built in a JsPlumb drawing component example, transmitting parameter parameters into the two methods, wherein the parameters comprise a node shape, a node connection pattern and the like, the JsPlumb drawing component example forms a node pattern according to the transmitted parameters, storing service flow node information in a database, and sequentially generating three service flow nodes of groovy, http and groovy types;
s2: service flow node association
Clicking an initial node to drag a connecting line to a target node to form a node association relation, and monitoring a connection event by using a drawing assembly to store node connecting line information in real time;
s3: editing of basic information of nodes
Clicking a node information editing button to modify the basic information of the node;
s4: service flow template publishing
Issuing a service flow template, and automatically generating a routing rule of an apache camel (rule engine) in an xml format according to the service flow;
s5: service flow node resource addition
And selecting a corresponding service flow template for the service, clicking the node to add the resource, and finishing the service flow definition.
Further, in the step S1, the service flow node information includes a service flow template ID, a service flow node type, and a service flow node name.
Still further, the service flow node types include, but are not limited to, http, groovy, jdbc, and activemq.
Further, in the step S2, the node connection information includes a service flow template ID, a service flow start node ID, and a service flow target node ID.
Further, in step S2, the jsplubb.bind ("connection", function (info) { }) method is to bind the connection event to the jsplubb component instance, the connection monitors all node connection events, and the function (info) { } is a callback function triggered when the node connection event is monitored, where the parameters info include a connection start node ID and a target node ID, the callback start node ID and the target node ID are written in the function (info) { } function, and when the nodes form a connection relationship, the ssplubb component instance triggers the connection callback function after monitoring the connection event, and stores the node connection information such as the connection start node ID and the target node ID in the database. Further, in the step S3, the node basic information includes a node name and node remark information.
Further, the apache camel rules engine can load text in parsed xml format, and route messages according to xml tags such as "from", "to", etc. Acquiring a service flow template ID, wherein the service flow template ID is an identifier of a route, splicing the service flow template ID with the uri of direct: template- "as an attribute of a" from "label to generate a text in an xml format, storing the text in a database, reading and loading by a gateway, reading the uri of the direct: template-service flow template ID by an apache cache rule engine when calling a certain route template, and positioning the route to the route template. In the steps S4 and S5, the generated routing rule of the rule engine is identified by the service flow template ID for being loaded by the gateway, and the resource bound by the corresponding service is called.
Further, in the steps S4 and S5, the generated routing rule of the rule engine is identified by the service flow template ID for loading by the gateway, and the resource bound by the corresponding service is called.
Further, in the step S5, when the same service flow node adds multiple resources, the resource invocation policy is any one of random, polling or weighted.
Furthermore, the service flow template has one and only one service flow starting node, and the loop can cause the service flow to have no starting node and no ending node, so that a dead loop is formed, and the service flow cannot have the loop.
The invention also provides a service arrangement solution system realized by the draggable flow chart, which comprises the following steps:
the node generation module is used for creating a service flow template, selecting a service flow node type, dragging the service flow template to a canvas through a dragging component, calling a drawing component to generate a node graph, and storing service flow node information to a database;
the node association module is used for clicking the starting node to drag the connecting line to the target node to form a node association relation, and monitoring a connection event by using the drawing component to store the node connecting line information in real time;
the information editing module is used for clicking the node information to edit and modify the basic node information;
the template issuing module is used for issuing a service flow template and automatically generating a routing rule of a rule engine in an xml format according to a service flow;
the resource adding module is used for selecting a corresponding service flow template for the service, clicking the node to add the resource and finishing the definition of the service flow;
the control processing module is used for sending instructions to each module to complete corresponding actions;
the node generation module, the node association module, the information editing module, the template release module and the resource adding module are all electrically connected with the control processing module.
Compared with the prior art, the invention has the following advantages: according to the service arrangement solution method realized through the draggable flow diagram, the service flow arrangement is visualized through the jsPlumb drawing component, the service flow arrangement is simplified, and the operation and use difficulty is reduced; and the service flow information is generated into an apache camel routing rule in an xml format, so that the gateway can call corresponding service resources, and the method is worthy of popularization and use.
Drawings
FIG. 1 is a flow chart illustrating a service orchestration solution according to an embodiment of the invention;
fig. 2 is a flowchart of an implementation of a service orchestration solution according to a second embodiment of the present invention.
Detailed Description
The following examples are given for the detailed implementation and specific operation of the present invention, but the scope of the present invention is not limited to the following examples.
As shown in fig. 1, the present embodiment provides a technical solution: a service orchestration solution implemented through a draggable flow diagram, comprising the steps of:
s1: service flow node generation
Generating an instance by using a jsPlumb drawing component when a browser window is loaded, and drawing and generating a service flow chart; newly building a service flow template, selecting a service flow node type, dragging a node generated by a vuedragable dragging component to a canvas, triggering a makeSource and makeTarget parameter method built in a JsPlumb drawing component example, transmitting parameter parameters into the two methods, wherein the parameters comprise a node shape, a node connection pattern and the like, the JsPlumb drawing component example forms a node pattern according to the transmitted parameters, storing service flow node information in a database, and sequentially generating three service flow nodes of groovy, http and groovy types;
s2: service flow node association
Clicking an initial node to drag a connecting line to a target node to form a node association relation, and monitoring a connection event by using a drawing assembly to store node connecting line information in real time;
s3: editing of basic information of nodes
Clicking a node information editing button to modify the basic node information;
s4: service flow template publishing
Issuing a service flow template, and automatically generating a routing rule of an apache camel (rule engine) in an xml format according to the service flow;
s5: service flow node resource addition
And selecting a corresponding service flow template for the service, clicking the node to add the resource, and finishing the service flow definition.
In step S1, the service flow node information includes a service flow template ID, a service flow node type, and a service flow node name.
Service flow node types include, but are not limited to, http, groovy, jdbc, and activemq.
In step S2, the node connection information includes a service flow template ID, a service flow start node ID, and a service flow target node ID.
In step S2, the jsplumb.bind ("connection", function (info)) { } method binds a connection event for the jsPlumb drawing component instance, monitors all node connection events, and the function (info)) { } is a callback function triggered when the node connection event is monitored, where the information included in the parameter info includes a connection start node ID and a destination node ID, writes a method of storing the connection start node ID and the destination node ID in the database in the function (info)) { } callback function, and when a connection relationship is formed between nodes, the jsPlumb drawing component instance triggers the connection callback function after monitoring the connection event, and stores the node connection information such as the connection start node ID and the destination node ID in the database.
In step S3, the node basic information includes a node name and node remark information.
In step S4, the apache camel rule engine can load the text in the parsed xml format, and route the message according to xml tags such as "from", "to", and the like. Acquiring a service flow template ID, wherein the service flow template ID is an identifier of a route, splicing the service flow template ID with the uri of direct: template- "as an attribute of a" from "label to generate a text in an xml format, storing the text in a database, reading and loading by a gateway, reading the uri of the direct: template-service flow template ID by an apache cache rule engine when calling a certain route template, and positioning the route to the route template.
In the steps S4 and S5, the generated routing rule of the rule engine is identified by the service flow template ID for being loaded by the gateway, and the resource bound by the corresponding service is called.
In step S5, when multiple resources are added to the same service flow node, the resource invocation policy is any one of random, round robin, or weighted.
The service flow template has only one service flow starting node, and the loop can cause the service flow to have no starting node and ending node, so that a dead loop is formed, and the service flow cannot have the loop.
The embodiment further provides a service orchestration solution system implemented by a draggable flowchart, including:
the node generation module is used for newly building a service flow template, selecting a service flow node type, dragging the service flow template to canvas through a dragging component, calling a drawing component to generate a node pattern, and storing service flow node information to a database;
the node association module is used for clicking the starting node to drag the connecting line to the target node to form a node association relation, and monitoring a connection event by using the drawing component to store the node connecting line information in real time;
the information editing module is used for clicking the node information to edit and modify the basic node information;
the template issuing module is used for issuing a service flow template and automatically generating a routing rule of a rule engine in an xml format according to a service flow;
the resource adding module is used for selecting a corresponding service flow template for the service, clicking the node to add the resource and finishing the definition of the service flow;
the control processing module is used for sending instructions to each module to complete corresponding actions;
the node generation module, the node association module, the information editing module, the template publishing module and the resource adding module are all electrically connected with the control processing module.
Example two
As shown in fig. 2, the present embodiment provides a service orchestration solution implemented by a draggable flowchart, including the following steps:
step S1, the service flow node generates:
the jsPlumb drawing component generates an example when a browser window is loaded, and is used for drawing and generating a service flow chart; newly building a service flow template, selecting a service flow node type, dragging a node generated by a vuedragable dragging component to a canvas, triggering makeSource and makeTarget parameter methods built in a JsPlumb drawing component example, transmitting parameter parameters into the two methods, wherein the parameters comprise a node shape, a node connection line pattern and the like, forming a node pattern by the JsPlumb drawing component example according to the transmitted parameters, storing service flow node information in a database, and sequentially generating three service flow nodes of groovy, http and groovy types;
step S2, service flow node association:
clicking a starting node to drag a connecting line to a target node to form a node association relation, monitoring a connection event by using jsPlumb to store node connecting line information in real time, and sequentially connecting a groovy request conversion script node, an http resource node and a groovy response conversion script node;
step S3, editing node basic information:
clicking a node information editing button can modify the basic information of the node, including the name of the node, the remark information of the node and the like;
step S4, service flow template publishing:
issuing a service flow template, and automatically generating a routing rule of an apache camel (rule engine) in an xml format according to the service flow;
step S5, adding service flow node resources:
selecting a corresponding service flow template for the service, clicking the node to add the resource, completing the definition of the service flow, adding a groovy script for the groovy request conversion script node and the groovy response conversion script node, and adding a service interface address for the http resource node.
In step S1, the service flow node information includes a service flow template ID, a service flow node type, and a service flow node name, where the service flow node type includes, but is not limited to, http, groovy, jdbc, and activemq.
In step S2, the node connection information includes a service flow template ID, a service flow start node ID, and a service flow target node ID.
In step S2, the jsplus graphics.bind ("connection", function (info)) { } method is to bind a connection event to a jsplus drawing component instance, the connection monitors all node connection events, and the function (info)) { } is a callback function triggered when the node connection event is monitored, where the information included in the parameter info includes a connection start node ID and a destination node ID, the method of storing the connection start node ID and the destination node ID in the database is written in the function (info)) { } callback function, and when a connection relationship is formed between nodes, the jsplus drawing component instance triggers the connection callback function after monitoring the connection event, and stores node connection information such as the connection start node ID and the destination node ID in the database.
In step S3, the basic node information includes a node name and node remark information.
In step S4, the apache camel rule engine can load and parse the text in xml format, and route the message according to xml tags such as "from", "to", and the like. Acquiring a service flow template ID, wherein the service flow template ID is an identifier of a route, splicing the service flow template ID with the uri of direct: template- "as an attribute of a" from "label to generate a text in an xml format, storing the text in a database, reading and loading by a gateway, reading the uri of the direct: template-service flow template ID by an apache cache rule engine when calling a certain route template, and positioning the route to the route template.
In the steps S4 and S5, the generated routing rule of the apache camel is identified by the service flow template ID for the gateway to load, and the resource bound by the corresponding service is called.
In step S5, when multiple resources are added to the same service flow node, the resource invocation policy includes random, polling, or weight.
The service flow template has only one service flow starting node, and the loop can cause the service flow to have no starting node and ending node, so that a dead loop is formed, and the service flow cannot have the loop.
It should be noted that, in the foregoing system embodiment, each unit included is only divided according to functional logic, but is not limited to the above division as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
In addition, it is understood by those skilled in the art that all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing associated hardware, and the corresponding program may be stored in a computer-readable storage medium.
The jsPlumb framework is a Web application suitable for rendering streamlining, and an application or workflow designer similar to Visio can be provided through the jsPlumb framework. It may be consolidated for each processing node of the service flow. The service flow arrangement is visualized through the jsPlumb drawing component, so that the service flow arrangement is simplified, and the operation and use difficulty is reduced; and generating the service flow information into an apache camel routing rule in an xml format for the gateway to call corresponding service resources.
To sum up, in the service orchestration solution implemented by the draggable flow diagram in the embodiment, the service flow is orchestrated and visualized by the jsPlumb drawing component, so that the service flow orchestration is simplified, and the operation and use difficulty is reduced; and the service flow information is generated into an apache camel routing rule in an xml format, so that the gateway can call corresponding service resources, and the method is worthy of popularization and use.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (8)
1. A service orchestration solution implemented through a draggable flow diagram, comprising the steps of:
s1: service flow node generation
The method comprises the steps that a drawing component generates an instance when a browser window is loaded, a service flow template is newly built, a service flow node type is selected, a node generated by a dragging component is dragged to a canvas, a parameter method built in the drawing component instance is triggered, parameters are transmitted to the parameter method, the parameters comprise node shapes and node connection patterns, the drawing component instance forms a node pattern according to the transmitted parameters, and service flow node information is stored in a database;
s2: service flow node association
Clicking an initial node to drag a connecting line to a target node to form a node association relation, monitoring a connection event by using a drawing assembly and storing node connecting line information in real time;
s3: editing of basic information of nodes
Clicking a node information editing button to modify the basic node information;
s4: service flow template publishing
Releasing a service flow template, and automatically generating a routing rule of a rule engine in an xml format according to a service flow;
s5: service flow node resource addition
Selecting a corresponding service flow template for the service, clicking a node to add resources, and completing service flow definition;
in step S1, the service flow node information includes a service flow template ID, a service flow node type, and a service flow node name;
in step S4, the rule engine loads and analyzes the text in xml format, performs routing on the message according to the xml tag, obtains the service flow template ID, where the service flow template ID is the identifier of the route, concatenates the service flow template ID as the attribute of the "from" tag, generates the text in xml format, stores the text in the database, and after the gateway reads and loads the text, when a certain routing template is called, the rule engine reads the uri of "direct: template-service flow template ID" and locates the route to the routing template.
2. The method for service orchestration solution through draggable flow graph according to claim 1, wherein: the types of the service flow nodes comprise http, groovy, jdbc and activemq.
3. The method for service orchestration solution through draggable flow graph according to claim 2, wherein: in the step S2, the node connection information includes a service flow template ID, a service flow start node ID, and a service flow target node ID, and in the step S3, the node basic information includes a node name and node remark information.
4. The method for service orchestration solution through draggable flow graph according to claim 3, wherein: in step S2, the drawing component is jsPlumb, a connection event is bound for the drawing component instance by using a jsPlumb binding method, all node connection events are monitored through the connection, and a callback function triggered when a node connection event is monitored is function (info) { }, where the information included in the parameter info includes a connection start node ID and a destination node ID, a method for storing the connection start node ID and the destination node ID in the callback function is written in the callback function, and when a connection relationship is formed between nodes, the drawing component instance triggers the callback function after monitoring the connection event, and stores the node connection information in the database.
5. The method for service orchestration solution through draggable flow graph according to claim 4, wherein: in the steps S4 and S5, the generated routing rule of the rule engine is identified by the service flow template ID for being loaded by the gateway, and the resource bound by the corresponding service is called.
6. The method for service orchestration solution through draggable flow graph according to claim 5, wherein: in step S5, when multiple resources are added to the same service flow node, the resource invocation policy is any one of random, round robin, or weighted.
7. The method for service orchestration solution through draggable flow graph according to claim 6, wherein: the service flow template has one or more service flow starting nodes, and the service flow of the service flow template has no loop.
8. A service orchestration solution system implemented by a draggable flowchart, wherein the service orchestration solution method according to any one of claims 1 to 7 is used for orchestrating a service flow, and the service orchestration solution system comprises:
the node generation module is used for creating a service flow template, selecting a service flow node type, dragging the service flow template to a canvas through a dragging component, calling a drawing component to generate a node graph, and storing service flow node information to a database;
the node association module is used for clicking the starting node to drag the connecting line to the target node to form a node association relation, and monitoring a connection event by using the drawing component to store the node connecting line information in real time;
the information editing module is used for clicking the node information to edit and modify the basic node information;
the template issuing module is used for issuing a service flow template and automatically generating a routing rule of a rule engine in an xml format according to a service flow;
the resource adding module is used for selecting a corresponding service flow template for the service, clicking the node to add the resource and finishing the definition of the service flow;
the control processing module is used for sending instructions to each module to complete corresponding actions;
the node generation module, the node association module, the information editing module, the template release module and the resource adding module are all electrically connected with the control processing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010784750.8A CN111930372B (en) | 2020-08-06 | 2020-08-06 | Service arrangement solution method and system realized through draggable flow chart |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010784750.8A CN111930372B (en) | 2020-08-06 | 2020-08-06 | Service arrangement solution method and system realized through draggable flow chart |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111930372A CN111930372A (en) | 2020-11-13 |
| CN111930372B true CN111930372B (en) | 2022-09-20 |
Family
ID=73307694
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010784750.8A Active CN111930372B (en) | 2020-08-06 | 2020-08-06 | Service arrangement solution method and system realized through draggable flow chart |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111930372B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112685011B (en) * | 2020-12-21 | 2022-06-07 | 福建新大陆软件工程有限公司 | AI application visualization arrangement method based on Vue |
| CN114691308A (en) * | 2020-12-25 | 2022-07-01 | 第四范式（北京）技术有限公司 | Online task arranging method and online task arranging device |
| CN113256095A (en) * | 2021-05-17 | 2021-08-13 | 广州嘉为科技有限公司 | Draggable configured agile flow service construction method, system, device and medium |
| CN113554412A (en) * | 2021-06-29 | 2021-10-26 | 国网山东省电力公司东营供电公司 | Engine system for establishing approval process |
| CN113794636B (en) * | 2021-08-11 | 2022-11-18 | 科大国创云网科技有限公司 | Dynamic routing arrangement method and system based on Spring Cloud Gateway |
| CN114157567A (en) * | 2021-11-19 | 2022-03-08 | 浙江惠瀜网络科技有限公司 | Routing engine configuration method and device, storage medium and electronic device |
| CN114168113B (en) * | 2022-02-10 | 2022-06-07 | 湖南新云网科技有限公司 | Business process management and control configuration method |
| CN114640618B (en) * | 2022-03-15 | 2024-03-12 | 平安国际智慧城市科技股份有限公司 | Cluster route scheduling method and device, electronic equipment and readable storage medium |
| CN114385233B (en) * | 2022-03-24 | 2022-08-02 | 山东省计算中心（国家超级计算济南中心） | Cross-platform adaptive data processing workflow system and method |
| CN115237295A (en) * | 2022-06-09 | 2022-10-25 | 中银金融科技有限公司 | Method, electronic equipment and medium for generating flow chart through visual dragging |
| CN115277817A (en) * | 2022-07-23 | 2022-11-01 | 江苏南大先腾信息产业股份有限公司 | Method for realizing visualized data processing by establishing API gateway through flow service arrangement |
| CN116185425B (en) * | 2023-03-23 | 2024-02-23 | 苏州峰之鼎信息科技有限公司 | Event flow arrangement method, device, equipment and medium based on node combination |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018036342A1 (en) * | 2016-08-23 | 2018-03-01 | 中兴通讯股份有限公司 | Csar-based template design visualization method and device |
| CN108681451A (en) * | 2018-05-14 | 2018-10-19 | 浪潮软件集团有限公司 | Visual kubernets micro-service arrangement implementation method |
| CN108768688A (en) * | 2018-04-11 | 2018-11-06 | 无锡华云数据技术服务有限公司 | Visual mixing cloud resource method of combination and device |
| CN109683868A (en) * | 2018-12-28 | 2019-04-26 | 成都康赛信息技术有限公司 | A kind of web flow journey design method based on jsPlumb technology |
| CN110750254A (en) * | 2019-10-18 | 2020-02-04 | 浪潮云信息技术有限公司 | Flowchart editor implementation method based on Angular |
| CN110912724A (en) * | 2018-09-18 | 2020-03-24 | 亿阳信通股份有限公司 | Parameter-driven automatic service arrangement method and device |
| CN111081356A (en) * | 2019-11-07 | 2020-04-28 | 福建亿能达信息技术股份有限公司 | Method for flow management based on WEB |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3155525A2 (en) * | 2014-06-13 | 2017-04-19 | Convida Wireless, LLC | Automated service profiling and orchestration |
| US10331419B2 (en) * | 2017-11-30 | 2019-06-25 | International Business Machines Corporation | Creating composite templates for service instances |
-
2020
- 2020-08-06 CN CN202010784750.8A patent/CN111930372B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018036342A1 (en) * | 2016-08-23 | 2018-03-01 | 中兴通讯股份有限公司 | Csar-based template design visualization method and device |
| CN108768688A (en) * | 2018-04-11 | 2018-11-06 | 无锡华云数据技术服务有限公司 | Visual mixing cloud resource method of combination and device |
| CN108681451A (en) * | 2018-05-14 | 2018-10-19 | 浪潮软件集团有限公司 | Visual kubernets micro-service arrangement implementation method |
| CN110912724A (en) * | 2018-09-18 | 2020-03-24 | 亿阳信通股份有限公司 | Parameter-driven automatic service arrangement method and device |
| CN109683868A (en) * | 2018-12-28 | 2019-04-26 | 成都康赛信息技术有限公司 | A kind of web flow journey design method based on jsPlumb technology |
| CN110750254A (en) * | 2019-10-18 | 2020-02-04 | 浪潮云信息技术有限公司 | Flowchart editor implementation method based on Angular |
| CN111081356A (en) * | 2019-11-07 | 2020-04-28 | 福建亿能达信息技术股份有限公司 | Method for flow management based on WEB |
Non-Patent Citations (1)
| Title |
|---|
| 面向随选网络的业务编排系统研发实践;罗光峰;《电信科学》;20171231;148-156 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111930372A (en) | 2020-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111930372B (en) | Service arrangement solution method and system realized through draggable flow chart | |
| Grefen et al. | Dynamic business network process management in instant virtual enterprises | |
| CN103984818A (en) | AUV (autonomous underwater vehicle) design flow visualization modeling method based on Flex technology | |
| CN114115852A (en) | Visual service arranging method, device, equipment and medium | |
| Kozma et al. | Data-driven Workflow Management by utilising BPMN and CPN in IIoT Systems with the Arrowhead Framework | |
| CN108229779A (en) | A kind of Intelligent Dynamic service combining method and system towards producing line | |
| CN106528169A (en) | Web system development reusable method based on AnGo dynamic evolution model | |
| US20060020948A1 (en) | Real-time multi-modal business transformation interaction | |
| US10083010B2 (en) | Extensible meta model for capturing solution patterns | |
| CN112558968B (en) | Method, device, equipment and storage medium for generating resource tree view | |
| CN115774573B (en) | Application integration method, device, electronic equipment and storage medium | |
| CN102073505A (en) | Service composition-oriented declarative transaction integration method and system | |
| Foster et al. | UML extensions for service-oriented systems | |
| CN107896242A (en) | One kind service sharing method and device | |
| CN115237295A (en) | Method, electronic equipment and medium for generating flow chart through visual dragging | |
| Zinnikus et al. | A model-driven, agent-based approach for the integration of services into a collaborative business process | |
| CN103064688A (en) | Workflow universal service method and system | |
| CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium | |
| CN110083350A (en) | A kind of micro services Adaptive evolution method based on RMAE under cloud computing environment | |
| CN114819483A (en) | Flexible service arranging system and method for industrial robot | |
| Lillo et al. | An ECA-based semantic architecture for IoT building automation systems | |
| CN114610454A (en) | Micro-service architecture operation resource scheduling method and device | |
| CN111061723B (en) | Workflow realization method and device | |
| Seo et al. | Automating the DEVS modeling and simulation interface to web services | |
| Ning et al. | BPELGEN: an algorithm of automatically converting from web services composition plan to BPEL4WS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |