CN111258773B - Service call flow information processing method and device and electronic equipment - Google Patents
Service call flow information processing method and device and electronic equipment Download PDFInfo
- Publication number
- CN111258773B CN111258773B CN201811461098.5A CN201811461098A CN111258773B CN 111258773 B CN111258773 B CN 111258773B CN 201811461098 A CN201811461098 A CN 201811461098A CN 111258773 B CN111258773 B CN 111258773B
- Authority
- CN
- China
- Prior art keywords
- service
- flow
- node
- nodes
- task
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/544—Remote
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the application discloses a service call flow information processing method, a device and electronic equipment, wherein the method comprises the following steps: creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node; providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance; the configured tasks comprise service interface identifiers required to be called and parameter information for positioning service implementation under the service interface. The business scene can be flexibly supported, the access of new merchants is rapidly carried out at low cost, and meanwhile, the compatibility of a workflow mode and a state machine mode is realized.
Description
Technical Field
The present invention relates to the field of service call flow information processing technologies, and in particular, to a service call flow information processing method and apparatus, and an electronic device.
Background
In the online and offline combined business mode of 'new retail' and the like, retailers can provide information of commodity objects through online application programs (apps), and users can conduct browsing, purchasing and other actions through online apps. Meanwhile, retailers can also open off-line physical shops, and users can purchase commodity objects through the off-line physical shops. Meanwhile, the online order can be subjected to a series of processing such as shipment by an offline physical store and finally delivered to a receiving address designated by a user. However, some retailers may be limited by their own resources or capabilities, and may not be able to provide perfect shipping, distribution, etc. services for users, and even when the process of putting on shelves of goods, etc. is performed, there may be some difficulties, resulting in low efficiency, high error rate, etc. To enable such retailers to also be incorporated into a "new retail" system, the "new retail" platform may provide services to the retailers, such as standardized flow processing services, which may complete online and offline integrated sales links by purchasing the platform's services. For example, a retailer may purchase an "on-shelf" service, at which point the platform may provide the retailer with a corresponding solution, and so on.
Typically, services on a particular business link may be provided by the platform side, but as systems evolve, more and more external merchants need to cooperate with the "new retail" platform. For example, an external merchant may be able to offer "on-shelf" services and also wish to add to a "new retail" system, so that other retailers may also purchase the services offered by the external merchant to address a class of problems, and so that such external merchants may also be able to act as another source of revenue by selling such services.
However, merchants who can provide related services on the service link generally use a specific ERP system to manage various information and data. For example, merchant a internally uses an ERP system, where the specific manner in which the product stocking is implemented may be different from the default stocking approach for the "new retail" system platform side. At this time, when the external merchant accesses the platform, it may be hoped to continue to use the processing mode which is customary in the external merchant rather than uniformly using the platform scheme, and the latter needs to modify and upgrade the software and hardware system in the external merchant, which can have high cost.
Therefore, how to flexibly support the service scenario, and quickly and inexpensively access new merchants becomes a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The service call flow information processing method, the device and the electronic equipment can flexibly support service scenes, and realize compatibility of a workflow mode and a state machine mode while accessing a new merchant rapidly and with low cost.
The application provides the following scheme:
a service call flow information processing method includes:
creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node;
providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
A service call flow information processing method includes:
receiving a flow instance created by a client and task information configured for nodes and/or triggering events in the flow instance, wherein the configured task comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
providing identification information for the call flow instance;
and providing the tool package information so that a service calling party operates the flow instance corresponding to the identification information through the tool package, and initiating the call to the service implementation through the service interface in the process of executing the flow instance so as to obtain the service on the corresponding node.
A service call flow information processing method includes:
in the process of executing a specified flow by a service calling party, positioning to a target service to be called according to a specified service interface identifier and call parameter information in a task corresponding to the flow; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
Determining a working mode of a flow engine according to the configuration object category information in the flow instance corresponding to the task;
and returning to the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
A service call flow information processing apparatus comprising:
a flow instance creation unit, configured to create a flow instance according to a received creation request, where the flow instance includes a plurality of nodes and at least one trigger event, where the trigger event is used to trigger switching from one node to the next node;
a configurable object providing unit, configured to provide a configurable object for the flow, where the configurable object includes the node and the trigger event, so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
A service call flow information processing apparatus comprising:
the system comprises a flow instance receiving unit, a processing unit and a processing unit, wherein the flow instance receiving unit is used for receiving a flow instance created by a client and task information configured for nodes and/or triggering events in the flow instance, wherein the configured task comprises a service interface identifier required to be called and parameter information used for positioning service implementation under the service interface; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
the identification providing unit is used for providing identification information for the call flow instance;
and the tool pack providing unit is used for providing tool pack information so that a service calling party can operate the flow instance corresponding to the identification information through the tool pack, and in the process of executing the flow instance, the service interface initiates the call to the service implementation to obtain the service on the corresponding node.
A service call flow information processing apparatus comprising:
the service positioning unit is used for positioning the target service to be invoked according to the service interface identifier and the invoking parameter information appointed in the task corresponding to the flow in the process of executing the appointed flow by the service caller; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
The working mode determining unit is used for determining the working mode of the flow engine according to the configuration object category information in the flow instance corresponding to the task;
and the service address return unit is used for returning the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
An electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node;
providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
An electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
in the process of executing a specified flow by a service calling party, positioning to a target service to be called according to a specified service interface identifier and call parameter information in a task corresponding to the flow; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
determining a working mode of a flow engine according to the configuration object category information in the flow instance corresponding to the task;
and returning to the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
According to a specific embodiment provided by the application, the application discloses the following technical effects:
according to the embodiment of the application, the standard operation program flow in the commodity object service flow is split and abstracted according to the granularity of the logic nodes to define the service interface, and then service implementation is provided for the service interface, so that service implementation corresponding to different nodes in the flow are mutually independent, corresponding flow engines are provided, and the service implementation can be routed to a specific service implementation level, so that each service implementation can be independently developed, independently deployed and independently called. Based on the implementation architecture, the implementation of the method can be realized by creating a flow instance and a task in the process of specifically performing code call on the service interface, wherein the configurable object in the flow instance can be a node or an event, and can be compatible with a workflow mode and a state machine mode, so that the service interface can be arranged in different service scenes by using a plurality of different expression modes.
Of course, not all of the above-described advantages need be achieved at the same time in practicing any one of the products of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a system provided by an embodiment of the present application;
FIG. 2-1 is a workflow pattern flow diagram;
2-2 are state machine mode flowcharts;
FIGS. 2-3 are flow diagrams of workflow mode and state machine mode compatibility provided by embodiments of the present application
FIG. 3 is a flow chart of a first method provided by an embodiment of the present application;
FIGS. 4-1 and 4-2 are task configuration diagrams provided in embodiments of the present application;
FIG. 5 is a flow chart of a second method provided by an embodiment of the present application;
FIG. 6 is a flow chart of a third method provided by an embodiment of the present application;
FIG. 7 is a schematic diagram of a first apparatus provided in an embodiment of the present application;
FIG. 8 is a schematic diagram of a second apparatus provided in an embodiment of the present application;
FIG. 9 is a schematic diagram of a third apparatus provided in an embodiment of the present application;
fig. 10 is a schematic diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.
Firstly, it should be noted that in the service mode of combining online with offline in the "new retail" etc., the service scenario is complex, the service link is long, and a whole set of central station system from the supply chain to the user terminal is realized. In this process, business parties in the service platform often need to handle a variety of standard workflow. For example, for consumer-oriented business parties, processing order flows, shipping flows, etc. may be involved. For business side facing the merchant, the process of loading, stock adjustment, stock replenishment, stock distribution, modification of commodity price, etc. may be more needed. Each process may include a plurality of business logic nodes, for example, for a commodity shelf-loading process, a plurality of nodes such as picking- > packing- > boxing- > shelf-loading are included.
In the prior art, a platform side uses an application-based development mode, and a developer develops codes according to application dimensions, so that an application generally comprises a plurality of nodes in a specific flow. For example, for the commodity loading process in the foregoing example, which includes a plurality of nodes such as picking- > packing- > boxing- > loading, in the prior art, implementation codes on each node in the process are combined together and bound in the same unit, developed together, deployed together, and provided with services together. At this time, if the platform side can provide the corresponding implementation for the package service in the above-mentioned flow, and two cooperated merchants A, B can also provide the respective implementation, the package service needs to be added to the above-mentioned flow, but the original implementation in the flow may not meet the requirements of the new merchant. Such as: the original flow is Start- > node A- > node B- > node C- > End. When a new merchant needs to join the process, the service implementation corresponding to the node A is realized according to the default mode of the platform, the requirement of the merchant A cannot be met, and an implementation mode needs to be newly added to the node A: "implementation of a service 2". At this time, if the conventional flow engine is adopted, there are several schemes as follows: scheme 1: redefining a new flow, still comprising 'Start- > node A- > node B- > node C- > End', modifying the implementation of 'service A' to 'implementation of A service 2'. Scheme 2: the original flow is used, but the code corresponding to the flow needs to be modified, and a conditional statement is written in the code to judge which calling service is selected, namely, the hard coding mode. Scheme 3: on the basis of the original flow, a branch flow, namely a selection node is newly added, a judgment condition is added on the selection node, and meanwhile, the selection corresponding to the new condition is selected and called according to the judgment condition. These three schemes each have drawbacks: in the scheme 1, a plurality of sets of processes are required to be maintained, and the maintenance cost is high. Once the flow template is modified, all corresponding flows need to be modified. In the scheme 2, the business logic is realized by depending on codes, and once a new flow is accessed, the codes corresponding to the flow are required to be modified, so that the method is an invasive realization mode, the codes are required to be released every time the codes are modified, the release risk is high, and the logic is not friendly to non-technical personnel in the codes. Scheme 3, once a new merchant accesses, the flow configuration needs to be modified, and a relatively steady flow cannot be maintained.
In the embodiment of the present application, in order to support a service scenario more flexibly, to quickly and at low cost access a new merchant, as shown in fig. 1, a standard operation program flow in a service platform such as "new retail" may be first abstracted out by taking a node as a unit to provide a standard service interface (which may be referred to as SPI in the embodiment of the present application), and a first system 101 may be provided to define and register a specific service interface; the definition information of such a service interface may then be provided to a specific service provider (e.g., the service platform itself, or other external merchants, etc., referred to as the third system 103 in this embodiment), which may then provide a specific service implementation (which may be referred to as bundle in this embodiment) according to a standard job interface specification corresponding to the specific service. That is, in the embodiment of the present application, the service logic node on a specific flow does not correspond to a certain fixed specific implementation, but exists in the form of an interface, and when defining a service interface, only the in-parameter, out-parameter, function, and the like of the service interface need to be defined, without providing specific implementation codes. In other words, a service interface need only define what functions are corresponding, which in-parameters are needed, and which out-parameters are needed, without providing specific implementation code. A specific service provider may provide a plurality of different service implementations for a specific service interface, for example, for a "pick" service interface, at the service interface level, it is not necessary to determine how to implement a pick function specifically, but, if a merchant a is able to provide a specific pick service, a specific service implementation code may be provided for the service interface, that is, by the merchant a, according to the specific pick implementation logic of the merchant a, a service implementation code related to the pick service is provided. In addition, if merchant B is also able to provide specific pick-up services, a corresponding pick-up service implementation code may also be provided according to specific pick-up implementation logic within the merchant B. By the method, the different nodes in the business process are decoupled from each other, and the service implementation on the different nodes can be independently developed, independently deployed and independently provided with the service. And, for the same service interface, a plurality of different service providers can provide a plurality of different service implementation codes, which are respectively registered in the flow engine subsystem, so that the same service interface can have a 'multi-state' implementation.
That is, in the embodiment of the present application, a specific service interface may be abstracted by a platform side, and then a specific service implementation code may be provided by service providers, where each service provider's service implementation code may be developed according to service implementation logic in an ERP (enterprise management planning) system within the service provider. In addition, the service implementation code provided by the specific service provider can be directly stored on the server of the service provider, and then when the service implementation code is called by the specific service caller, the service implementation code can also run on the server of the service provider, execute specific operation according to the implementation logic inside the service provider, and return the processing result to the service caller.
After the service interface is abstracted and defined in the above manner and at least one service implementation is provided for a specific service interface, a service caller (for example, a specific business party, etc. may be referred to as the second system 102 in the embodiment of the present application) may call one of the specific service implementations under the service interface through the specific service interface, so as to obtain a corresponding service. When a service calling party specifically calls a service, the service calling party can specify the id or name of the service to be called, can also specify the information of the specific required service implementation, and then a specific flow engine system routes a specific calling request to a service address corresponding to a specific service implementation. In particular, when the service implementation is specified, specific parameter information may be set in the call code. In order to facilitate the setting of call parameters by the service caller, the service provider may also set specific routing rules when providing the service implementation code. For example, in one form, identification information such as an id or name of a particular service implementation may be directly specified, such that the flow engine can locate the service implementation code of a particular desired call directly through the id or name of the service implementation. Alternatively, in another implementation manner, the specification may be performed by a regularization method, where the specific incoming parameter may be some indirect information, for example, information such as a warehouse type, a warehouse Id, etc., and then the specific service implementation code is located by the regularization method.
For example, in a service system in a "new retail" mode, in order to enable access to ERP systems of different partners for standard services of the system on a standard service link of the system, to implement diversification of a certain service node, the embodiment of the present application abstracts, for each service on a specific service link, a standard interface of the service is defined, which may be referred to as an SPI, for example, including a pick-up service interface, a package service interface, an on-shelf service interface, and so on. The specific implementation of the service is called as Bundle, and one SPI can be provided with a plurality of bundles to realize the polymorphism of the service implementation. For example, in the foregoing commodity loading process, the four nodes including picking, packing, boxing and loading may be abstracted into four service interfaces in the embodiment of the present application, which are a picking service interface, a packing service interface, a boxing service interface and a loading service interface. The goods picking service interface (SPI) can be realized by providing service by the service provider 1; the SPI, the package service interface, may have a Default implementation (Default Bundle) provided by the service provider a, an implementation (e.g., darun fa Bundle) provided by the service provider 2, and so on.
After the abstraction of the service interface is performed and the service implementation is developed on the service granularity, the service interface can be registered in the service system, so that the service call in a specific entity store can be conveniently performed by calling the service implementation to obtain a specific function. For example, a service caller in the physical store a may call the implementation of the package service provided by the service provider 1, implement the package function, call the implementation of the put-on-shelf service of the service provider 2, and implement the put-on-shelf function; the service caller in the physical store B may call the implementation of the pick service provided by the service provider 1, implement the pick function, call the implementation of the put-on-shelf service of the service provider 2, implement the put-on-shelf function, and so on. That is, in the process of implementing the standard operation flow, the same service caller client can jointly solve the specific problem in the actual service scene by arranging the implementation corresponding to a plurality of different services, including setting the call relationship among the different services, and the like, and using the service implementation provided by a plurality of different service providers.
The above description describes the solution provided by the embodiments of the present application for developing services based on service granularity and invoking services. The commodity service flow is split according to the nodes, specific service interfaces are abstracted, and after a specific service implementation code is provided by a service provider, the commodity service flow is equivalent to all the standard operation flow to be broken into one service interface, a plurality of service implementations are corresponding to each service interface, and the concept of the flow does not exist on a platform level any more. In the process of specifically calling the service interface, the service calling party can singly call a certain service interface, for example, a certain service calling party only needs the service on a certain node, and only calls the service interface corresponding to the node to obtain the service provided by one of the service implementations. Or, in an actual service scenario specific to the service caller, a certain function may still need to be implemented in a flow form, so that a plurality of service interfaces may also be arranged in advance to generate a flow instance, and the second system may call in units of the flow instance. For example, if a service caller needs to put a commodity on shelf, a process from picking, packing, boxing, and putting a specific commodity on shelf may still be required.
Therefore, in order to meet the arrangement requirement of the service interface of the service calling party, a flow configuration subsystem can be further provided for creating a service flow instance in the service platform and performing task configuration in a specific service flow instance, and when performing task configuration, a corresponding task can be completed by designating a specific service interface and service implementation. The flow configuration subsystem may also allocate an ID and other identifier to the flow instance, and may provide a tool package for the service caller, where the tool package may include a tool for operating the configured flow, so that the service caller may introduce the tool package into its own client, and call and terminate a specifically defined flow in the client code according to the actual service requirement.
In the process of carrying out specific flow creation and task configuration through the flow configuration subsystem, a flow chart can be generated based on a specific required flow, and then specific task configuration is carried out on the basis of the flow chart, so that visual configuration is realized. However, in the prior art, the process engine is either focused on a stateless or pure state machine of pure memory execution, and therefore, either task configuration is performed only on nodes in the process or on events in the process. Among these, a finite state machine, simply called a state machine (statemachine), is a mathematical model that represents a finite number of states and actions such as transitions and actions between these states. The main points of the state machine are as follows: having a set of states and being switchable between the set of states and being simultaneously only one state. The working principle of the finite state machine is as follows: after an event (event) occurs, the action (action) to be performed is decided based on the current state (current_state), and the next state (next_state) is set. Workflow (workflow) mode, emphasizing the execution of tasks. One node is considered as a task, and after the task execution is completed, the next task node is skipped. In the prior art, some of the flow engines only support the workflow mode, as shown in fig. 2-1, which illustrates the flow engines only supporting the workflow. In the process engine, tasks are configured on nodes, when the process is run to the nodes, corresponding task configuration is executed, and after the completion, the process jumps to the next node; some flow engines only support state machine modes, as shown in fig. 2-2, and show a flow engine only supporting state machines, in which tasks are configured on events, when a flow runs to the events, tasks corresponding to the events are executed, and after execution is completed, the next node is skipped.
In the embodiment of the present application, in order to use different expressions in different traffic scenarios, a flow engine compatible with a workflow mode and a state machine mode is provided, that is, in the embodiment of the present application, as shown in fig. 2-3, a configurable object in a flow chart may be a node or an event. In specific implementation, a service party can configure a specific task for a node in the flowchart by clicking the node, and can configure a specific event for a corresponding event by clicking a connecting line between adjacent nodes in the flowchart. Thus, the flow engine in the embodiment of the application can fuse the service arrangement mode in the workflow mode and the state machine mode.
Specific implementations are described below.
Example 1
The first embodiment provides a service call flow information processing method from the perspective of a flow configuration subsystem client, referring to fig. 3, the method specifically may include:
s301: creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node;
In particular implementations, the process configuration subsystem may provide an entry for creating a process, particularly a code editing entry, or, in another manner, a visual process creation interface for easier operation. Through this interface, a flow chart may be generated for the created flow instance, for example, as shown in FIG. 4-1, in which a plurality of nodes and wiring of the nodes may be included. The specific node may be a logical node in the corresponding flow, and the connection corresponds to a trigger event in the specific flow.
S302: providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
Specifically, after the flow instance is created, a configurable object may be provided for the flow instance, and in this embodiment of the present application, the specific configurable object may include the node and the trigger event, so that task configuration may be performed for the node and/or the trigger event in the flow instance. That is, in the embodiment of the present application, task configuration may be performed on nodes and events for the flow instance, so as to implement compatibility between the workflow mode and the state machine mode. In particular, when task configuration is performed, if the configuration is shown in 4-2, the identifier of the service interface specifically required to be invoked, the identifier of the service implementation, the parameter used for positioning the service implementation, and other information can be configured.
Specifically, when a configurable object is provided through a flowchart, nodes and links between the nodes in the flowchart may be set to an operable state, so that by operating a target node, the target node is determined to be a node to be configured for a task, and by operating the target link, a target event corresponding to the target link is determined to be a trigger event to be configured for the task. In specific implementation, a service party can configure a specific task for a node in the flowchart by clicking the node, and can configure a specific event for a corresponding event by clicking a connecting line between adjacent nodes in the flowchart.
After the configuration is completed, task configuration information configured for the flow can be submitted to a server, so that the server distributes identification information for the flow and provides a tool kit, and a service calling party client side operates the flow instance through the tool kit.
That is, in this embodiment of the present application, specifically, when the task configuration is performed by the same flow instance, the types of configuration objects corresponding to different tasks may be different, and the server may store such information, so that in the process of performing routing by using a subsequent specific flow engine, different working modes may be switched according to the types of configuration objects corresponding to the specific task. Specifically, the information stored in the server may be specifically shown in table 1:
TABLE 1
In this way, in the process of executing the task in the created process, the working mode of the process engine can be determined according to the type of the configuration object corresponding to the specific task, and on the other hand, the positioning and routing of the target service implementation can be performed according to the service interface identifier in the task, the service implementation corresponding parameter and other information. When the working mode of the flow engine is specifically determined, if the configuration object corresponding to a certain task is a node in the flow, the configuration object can be determined to be a workflow mode, otherwise, if the configuration object is a trigger event, the configuration object is determined to be a state machine mode. The flow engine can be switched between different working modes to realize the compatibility of the workflow mode and the state machine mode.
In summary, through the embodiment of the present application, the configurable object in the flow may be a node or an event, which can be compatible with a workflow mode and a state machine mode, so that multiple different expression modes can be used in different service scenarios to schedule the service interface.
Example two
The second embodiment corresponds to the first embodiment, and from the perspective of the server, a service call flow information processing method is provided, and referring to fig. 5, the method specifically may include:
s501: receiving a flow instance created by a client and task information configured for nodes and/or triggering events in the flow instance, wherein the configured task comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
s502: providing identification information for the call flow instance;
s503: and providing the tool package information so that a service calling party operates the flow instance corresponding to the identification information through the tool package, and initiating the call to the service implementation through the service interface in the process of executing the flow instance so as to obtain the service on the corresponding node.
Example III
From the perspective of the flow engine subsystem client, the third embodiment provides a service call flow information processing method, referring to fig. 6, which specifically may include:
s601: in the process of executing a specified flow by a service calling party, positioning to a target service to be called according to a specified service interface identifier and call parameter information in a task corresponding to the flow; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
s602: determining a working mode of a flow engine according to the configuration object category information in the flow instance corresponding to the task;
and if the configuration object class is a logic node, determining that the working mode is a workflow mode. If the configuration object class is a trigger event, the working mode can be determined to be a state machine mode. That is, the flow engine in the embodiment is compatible with both modes.
S603: and returning to the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
For the undescribed portions of the first to third embodiments, reference may be made to the descriptions of the foregoing embodiments, and the description is omitted here.
Corresponding to the first embodiment, the embodiment of the present application further provides a service call flow information processing apparatus, referring to fig. 7, where the apparatus specifically may include:
a flow instance creation unit 701, configured to create a flow instance according to a received creation request, where the flow instance includes a plurality of nodes and at least one trigger event, where the trigger event is used to trigger a switch from one node to the next node;
a configurable object providing unit 702, configured to provide a configurable object for the flow, where the configurable object includes the node and the trigger event, so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
In particular, the apparatus may further include:
a flow chart generating unit, configured to generate a flow chart for the created flow chart instance, where the flow chart includes a plurality of nodes and connection lines of the nodes;
the configurable object providing unit is specifically configured to: a configurable object is provided by the flowchart.
More specifically, the configurable object providing unit may specifically be configured to:
and setting the nodes and the links among the nodes in the flow chart to be in an operable state, so as to determine the target node as the node to be subjected to task configuration through the operation on the target node, and determining the target event corresponding to the target link as the trigger event to be subjected to task configuration through the operation on the target link.
In addition, the apparatus may further include:
and the information submitting unit is used for submitting the task configuration information configured for the flow to a server so that the server distributes identification information for the flow and provides a tool kit so that the service calling party client operates the flow instance through the tool kit.
Corresponding to the embodiment, the embodiment of the application also provides a service call flow information processing device, referring to fig. 8, the device specifically may include:
A flow instance receiving unit 801, configured to receive a flow instance created by a client, and task information configured for a node and/or a trigger event in the flow instance, where the configured task includes a service interface identifier to be called and parameter information for locating a service implementation under the service interface; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
an identifier providing unit 802, configured to provide identifier information for the call flow instance;
and the tool pack providing unit 803 is configured to provide tool pack information, so that a service caller operates a flow instance corresponding to the identification information through the tool pack, and in the process of executing the flow instance, a call to the service implementation is initiated through the service interface to obtain a service on a corresponding node.
Corresponding to the embodiment, the embodiment of the application also provides a service call flow information processing device, referring to fig. 9, the device specifically may include:
the service positioning unit 901 is configured to position, in a process of executing a specified flow by a service caller, a target service to be invoked according to a service interface identifier specified in a task corresponding to the flow and call parameter information; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
A working mode determining unit 902, configured to determine a working mode of a flow engine according to configuration object category information in a flow instance corresponding to the task;
and the service address returning unit 903 is configured to return a service address corresponding to the target service implementation, so that the service caller client initiates a call to the service address.
Wherein, the working mode determining unit may specifically be used for:
and if the configuration object class is a logic node, determining that the working mode is a workflow mode.
And if the configuration object type is a trigger event, determining that the working mode is a state machine mode.
In addition, the embodiment of the application also provides electronic equipment, which comprises:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node;
Providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
And another electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
in the process of executing a specified flow by a service calling party, positioning to a target service to be called according to a specified service interface identifier and call parameter information in a task corresponding to the flow; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
Determining a working mode of a flow engine according to the configuration object category information in the flow instance corresponding to the task;
and returning to the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
Fig. 10 illustrates an exemplary architecture of a computer system, which may include a processor 1010, a video display adapter 1011, a disk drive 1012, an input/output interface 1013, a network interface 1014, and a memory 1020. The processor 1010, the video display adapter 1011, the disk drive 1012, the input/output interface 1013, the network interface 1014, and the memory 1020 may be communicatively connected by a communication bus 1030.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit ), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc., for executing related programs to implement the technical solutions provided herein.
The Memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory ), static storage device, dynamic storage device, or the like. The memory 1020 may store an operating system 1021 for controlling the operation of the electronic device 1000, and a Basic Input Output System (BIOS) for controlling the low-level operation of the electronic device 1000. In addition, web browser 1023, data storage management system 1024, and service call processing system 1025, etc. may also be stored. The service call processing system 1025 may be an application program that specifically implements the operations of the foregoing steps in the embodiments of the present application. In general, when implemented in software or firmware, the relevant program code is stored in memory 1020 and executed by processor 1010.
The input/output interface 1013 is used to connect with an input/output module to realize information input and output. The input/output module may be configured as a component in a device (not shown) or may be external to the device to provide corresponding functionality. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various types of sensors, etc., and the output devices may include a display, speaker, vibrator, indicator lights, etc.
The network interface 1014 is used to connect communication modules (not shown) to enable communication interactions of the device with other devices. The communication module may implement communication through a wired manner (such as USB, network cable, etc.), or may implement communication through a wireless manner (such as mobile network, WIFI, bluetooth, etc.).
In addition, the electronic device 1000 may also obtain information of specific acquisition conditions from the virtual resource object acquisition condition information database 1041 for making condition judgment, and so on.
It is noted that although the above-described devices illustrate only the processor 1010, video display adapter 1011, disk drive 1012, input/output interface 1013, network interface 1014, memory 1020, bus 1030, etc., the device may include other components necessary to achieve proper operation in an implementation. Furthermore, it will be understood by those skilled in the art that the above-described apparatus may include only the components necessary to implement the present application, and not all the components shown in the drawings.
From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the embodiments or some parts of the embodiments of the present application.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a system or system embodiment, since it is substantially similar to a method embodiment, the description is relatively simple, with reference to the description of the method embodiment being made in part. The systems and system embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The service call flow information processing method, device and electronic equipment provided by the application are described in detail, and specific examples are applied to illustrate the principles and implementation modes of the application, and the description of the above examples is only used for helping to understand the method and core ideas of the application; also, as will occur to those of ordinary skill in the art, many modifications are possible in view of the teachings of the present application, both in the detailed description and the scope of its applications. In view of the foregoing, this description should not be construed as limiting the application.
Claims (13)
1. A service call flow information processing method, characterized by comprising:
creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node;
providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
2. The method as recited in claim 1, further comprising:
generating a flow chart for the created flow example, wherein the flow chart comprises a plurality of nodes and connecting lines of the nodes;
The providing the configurable object for the flow includes:
a configurable object is provided by the flowchart.
3. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the providing the configurable object through the flow chart comprises the following steps:
and setting the nodes and the links among the nodes in the flow chart to be in an operable state, so as to determine the target node as the node to be subjected to task configuration through the operation on the target node, and determining the target event corresponding to the target link as the trigger event to be subjected to task configuration through the operation on the target link.
4. The method as recited in claim 1, further comprising:
and submitting the task configuration information configured for the flow to a server so that the server distributes identification information for the flow and provides a tool kit so that a service calling party client operates the flow instance through the tool kit.
5. A service call flow information processing method, characterized by comprising:
receiving a flow instance created by a client and task information configured for nodes and/or triggering events in the flow instance, wherein the configured task comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
Providing identification information for the call flow instance;
and providing the tool package information so that a service calling party operates the flow instance corresponding to the identification information through the tool package, and initiating the call to the service implementation through the service interface in the process of executing the flow instance so as to obtain the service on the corresponding node.
6. A service call flow information processing method, characterized by comprising:
in the process of executing a specified flow by a service calling party, positioning to a target service to be called according to a specified service interface identifier and call parameter information in a task corresponding to the flow; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
determining a working mode of a flow engine according to the configuration object category information in the flow instance corresponding to the task;
and returning to the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
7. The method of claim 6, wherein the step of providing the first layer comprises,
The determining the working mode of the process engine according to the configuration object category information in the process instance corresponding to the task comprises the following steps:
and if the configuration object class is a logic node, determining that the working mode is a workflow mode.
8. The method of claim 6, wherein the step of providing the first layer comprises,
the determining the working mode of the process engine according to the configuration object category information in the process instance corresponding to the task comprises the following steps:
and if the configuration object type is a trigger event, determining that the working mode is a state machine mode.
9. A service call flow information processing apparatus, comprising:
a flow instance creation unit, configured to create a flow instance according to a received creation request, where the flow instance includes a plurality of nodes and at least one trigger event, where the trigger event is used to trigger switching from one node to the next node;
a configurable object providing unit, configured to provide a configurable object for the flow, where the configurable object includes the node and the trigger event, so as to perform task configuration for the node and/or the trigger event in the flow instance;
The task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
10. A service call flow information processing apparatus, comprising:
the system comprises a flow instance receiving unit, a processing unit and a processing unit, wherein the flow instance receiving unit is used for receiving a flow instance created by a client and task information configured for nodes and/or triggering events in the flow instance, wherein the configured task comprises a service interface identifier required to be called and parameter information used for positioning service implementation under the service interface; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
the identification providing unit is used for providing identification information for the call flow instance;
And the tool pack providing unit is used for providing tool pack information so that a service calling party can operate the flow instance corresponding to the identification information through the tool pack, and in the process of executing the flow instance, the service interface initiates the call to the service implementation to obtain the service on the corresponding node.
11. A service call flow information processing apparatus, comprising:
the service positioning unit is used for positioning the target service to be invoked according to the service interface identifier and the invoking parameter information appointed in the task corresponding to the flow in the process of executing the appointed flow by the service caller; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
the working mode determining unit is used for determining the working mode of the flow engine according to the configuration object category information in the flow instance corresponding to the task;
and the service address return unit is used for returning the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
12. An electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
creating a flow instance according to the received creation request, wherein the flow instance comprises a plurality of nodes and at least one trigger event, and the trigger event is used for triggering switching from one node to the next node;
providing a configurable object for the flow, wherein the configurable object comprises the node and the trigger event so as to perform task configuration for the node and/or the trigger event in the flow instance;
the task of the configuration comprises a service interface identifier required to be called and parameter information for positioning service implementation under the service interface; the service interface is defined according to the nodes in the commodity object service flow, the service implementation is provided by the service provider according to the definition information corresponding to the service interface, and the service calling party initiates the call of the service implementation through the service interface so as to obtain the service on the corresponding nodes.
13. An electronic device, comprising:
one or more processors; and
a memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:
in the process of executing a specified flow by a service calling party, positioning to a target service to be called according to a specified service interface identifier and call parameter information in a task corresponding to the flow; the service interface is defined according to nodes in the commodity object service flow, and the service implementation is provided by a service provider according to definition information corresponding to the service interface;
determining a working mode of a flow engine according to the configuration object category information in the flow instance corresponding to the task;
and returning to the service address corresponding to the target service implementation so that the service calling party client initiates calling to the service address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811461098.5A CN111258773B (en) | 2018-12-01 | 2018-12-01 | Service call flow information processing method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811461098.5A CN111258773B (en) | 2018-12-01 | 2018-12-01 | Service call flow information processing method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258773A CN111258773A (en) | 2020-06-09 |
| CN111258773B true CN111258773B (en) | 2023-05-26 |
Family
ID=70948361
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811461098.5A Active CN111258773B (en) | 2018-12-01 | 2018-12-01 | Service call flow information processing method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258773B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112068936A (en) * | 2020-07-16 | 2020-12-11 | 石化盈科信息技术有限责任公司 | Workflow management platform and workflow management system |
| CN112633538B (en) * | 2020-12-26 | 2022-04-26 | 北京云迹科技股份有限公司 | Robot-based hotel reservation service order distribution processing method and system |
| CN113296906B (en) * | 2021-03-31 | 2023-11-28 | 阿里巴巴新加坡控股有限公司 | Task configuration method and device |
| CN113298343B (en) * | 2021-03-31 | 2023-11-14 | 阿里巴巴新加坡控股有限公司 | Task generation method, task execution method and device |
| CN113094192A (en) * | 2021-04-23 | 2021-07-09 | 杭州网易云音乐科技有限公司 | Data processing method, device, medium and equipment |
| CN113377371A (en) * | 2021-06-02 | 2021-09-10 | 五八到家有限公司 | Multi-scene configuration method, system, device and medium |
| CN113313476A (en) * | 2021-07-28 | 2021-08-27 | 深圳市永达电子信息股份有限公司 | Service information processing method, system, electronic device and storage medium |
| CN113609831A (en) * | 2021-08-05 | 2021-11-05 | 北京金堤科技有限公司 | Method and device for generating product delivery flow template |
| CN113778492B (en) * | 2021-09-17 | 2023-11-10 | 中国移动通信集团陕西有限公司 | Method, device, equipment and storage medium for issuing capability API |
| CN114780265A (en) * | 2022-05-18 | 2022-07-22 | 壹沓科技(上海)有限公司 | Cross-system service calling method, device and related equipment based on DSL |
| CN117592311B (en) * | 2024-01-17 | 2024-04-16 | 上海朋熙半导体有限公司 | Multi-level simulation method, device and equipment for workflow and readable medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104618433A (en) * | 2014-12-26 | 2015-05-13 | 国家电网公司 | ECA (Event-Condition-Action) rule based service combination method |
| CN106485439A (en) * | 2015-09-02 | 2017-03-08 | 阿里巴巴集团控股有限公司 | logistics service information processing method and device |
| CN106803143A (en) * | 2016-11-29 | 2017-06-06 | 中电科华云信息技术有限公司 | The method that flow engine cloud service is provided based on workflow engine for cloud platform |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020174050A1 (en) * | 2000-12-27 | 2002-11-21 | James Eynard | Business capacity transaction management system |
-
2018
- 2018-12-01 CN CN201811461098.5A patent/CN111258773B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104618433A (en) * | 2014-12-26 | 2015-05-13 | 国家电网公司 | ECA (Event-Condition-Action) rule based service combination method |
| CN106485439A (en) * | 2015-09-02 | 2017-03-08 | 阿里巴巴集团控股有限公司 | logistics service information processing method and device |
| CN106803143A (en) * | 2016-11-29 | 2017-06-06 | 中电科华云信息技术有限公司 | The method that flow engine cloud service is provided based on workflow engine for cloud platform |
Non-Patent Citations (3)
| Title |
|---|
| Gamal Sallam等.Shortest Path and Maximum Flow Problems Under Service Function Chaining Constraints.《IEEE INFOCOM 2018 - IEEE Conference on Computer Communications》.2018,全文. * |
| 吴敏灵.面向SOA架构的证券行情服务的设计与实现.《中国优秀硕士学位论文全文数据库 信息科技辑》.2015,(第undefined期),全文. * |
| 张艳.基于Web Service实现电子政务异构系统的数据交换和共享.《信息化建设》.2003,(第undefined期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258773A (en) | 2020-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258773B (en) | Service call flow information processing method and device and electronic equipment | |
| CN111262897B (en) | Service call routing processing method, device and system | |
| CN111258772B (en) | Service calling information processing method, device and system | |
| JP6879940B2 (en) | Service mounting method and equipment | |
| JP5489391B2 (en) | Method, system and program for comparing topologies (topology comparison) | |
| US20100250608A1 (en) | Creation and management of multi-tenant application services | |
| US8127269B2 (en) | Transforming a flow graph model to a structured flow language model | |
| CN111258567B (en) | Service code development processing method and device | |
| CN111262898B (en) | Service degradation processing method and device and electronic equipment | |
| CN112650475A (en) | Software low-code development system and development method combined with middle platform architecture theory | |
| WO2024002222A1 (en) | Application management method and related device | |
| CN112463211A (en) | System architecture transformation method compatible with multiple development architectures and system architecture | |
| CN108733457A (en) | The implementation method and device of distributed transaction | |
| US8234649B2 (en) | Composite system to integrate process systems using secondarily created process objects for local database operations and inter process system communications | |
| CN109840074A (en) | A kind of business generating method, device and the network equipment | |
| CN110531967B (en) | Code generation method and code generation device | |
| US20020112231A1 (en) | Software distribution at a multi-processor telecommunications platform | |
| CN113850558A (en) | Workflow arrangement method and device | |
| US9323509B2 (en) | Method and system for automated process distribution | |
| WO2023050956A1 (en) | Automatic selection of nodes on which to perform tasks | |
| EP2249294A2 (en) | Using abstraction layers to facilitate communication between systems | |
| US8468159B2 (en) | Data element categorization in a service-oriented architecture | |
| CN111506340B (en) | Business rule information processing method, device and system | |
| CN111510393B (en) | Traffic scheduling method, device and system | |
| JP2004185166A (en) | Service part selection support method |
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 |