CN116886531A

CN116886531A - Service processing method, device, medium and electronic equipment

Info

Publication number: CN116886531A
Application number: CN202310863048.4A
Authority: CN
Inventors: 包宏权; 王昱林; 何鸣明; 涂兆峰
Original assignee: Beijing Youzhuju Network Technology Co Ltd
Current assignee: Beijing Youzhuju Network Technology Co Ltd
Priority date: 2023-07-13
Filing date: 2023-07-13
Publication date: 2023-10-13

Abstract

The disclosure relates to a service processing method, a device, a medium and an electronic device, wherein the method comprises the following steps: acquiring a service request, wherein the service request carries a configuration file, the configuration file comprises first attribute parameters of a plurality of nodes, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes; based on the first attribute parameters of the nodes, executing the application examples corresponding to the nodes to obtain service processing results corresponding to the service requests, and configuring the flow of the service of the complex logic by configuring the nodes of various types, so that the complex service requirements can be realized.

Description

Service processing method, device, medium and electronic equipment

Technical Field

The disclosure relates to the technical field of electronic information, and in particular relates to a business processing method, a business processing device, a business processing medium and electronic equipment.

Background

With the development of computer technology, it is important how users can handle complex business needs initiated by users based on electronic devices that can perform various businesses, such as logging in to a certain application business and accessing a certain website.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

In a first aspect, the present disclosure provides a service processing method, including:

acquiring a service request, wherein the service request carries a configuration file, the configuration file comprises first attribute parameters of a plurality of nodes, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes;

and executing the application instance corresponding to each node based on the first attribute parameter of each node to obtain a service processing result corresponding to the service request.

In a second aspect, the present disclosure provides a service processing apparatus, including:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a service request, the service request carries a configuration file, the configuration file comprises first attribute parameters of a plurality of nodes, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes;

And the processing module is used for executing the application instance corresponding to each node based on the first attribute parameter of each node to obtain the service processing result corresponding to the service request.

In a third aspect, the present disclosure provides a computer readable medium having stored thereon a computer program which when executed by a processing device implements the steps of the method described in the first aspect.

In a fourth aspect, the present disclosure provides an electronic device comprising:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to carry out the steps of the method described in the first aspect.

By the technical scheme, the service request is acquired, the service request carries a configuration file, the configuration file comprises first attribute parameters of a plurality of nodes, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes; based on the first attribute parameters of each node, executing the application instance corresponding to each node to obtain a service processing result corresponding to the service request, and configuring the flow of the service of the complex logic by configuring multiple types of nodes, so that the complex service requirement can be realized.

Additional features and advantages of the present disclosure will be set forth in the detailed description which follows.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale. In the drawings:

fig. 1 is a flowchart illustrating a service processing method according to an exemplary embodiment of the present disclosure.

Fig. 2 is a flow chart illustrating a node execution sequence of a plurality of nodes according to an exemplary embodiment of the present disclosure.

Fig. 3 is a schematic diagram of a routing area in a first interface, according to an exemplary embodiment of the present disclosure.

Fig. 4 is another schematic diagram of a routing area in a first interface, according to an exemplary embodiment of the present disclosure.

Fig. 5 is another schematic diagram of a routing area in a first interface, according to an exemplary embodiment of the present disclosure.

Fig. 6 is a schematic diagram of a second interface shown according to an exemplary embodiment of the present disclosure.

Fig. 7 is a schematic diagram illustrating data flow of an application instance of an executing node according to an exemplary embodiment of the present disclosure.

Fig. 8 is a block diagram of a service processing apparatus according to an exemplary embodiment of the present disclosure.

Fig. 9 is a schematic structural view of an electronic device according to an exemplary embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

It will be appreciated that prior to using the technical solutions disclosed in the embodiments of the present disclosure, the user should be informed and authorized of the type, usage range, usage scenario, etc. of the personal information related to the present disclosure in an appropriate manner according to the relevant legal regulations.

For example, in response to receiving an active request from a user, a prompt is sent to the user to explicitly prompt the user that the operation it is requesting to perform will require personal information to be obtained and used with the user. Thus, the user can autonomously select whether to provide personal information to software or hardware such as an electronic device, an application program, a server or a storage medium for executing the operation of the technical scheme of the present disclosure according to the prompt information.

As an alternative but non-limiting implementation, in response to receiving an active request from a user, the manner in which the prompt information is sent to the user may be, for example, a popup, in which the prompt information may be presented in a text manner. In addition, a selection control for the user to select to provide personal information to the electronic device in a 'consent' or 'disagreement' manner can be carried in the popup window.

It will be appreciated that the above-described notification and user authorization process is merely illustrative and not limiting of the implementations of the present disclosure, and that other ways of satisfying relevant legal regulations may be applied to the implementations of the present disclosure.

Meanwhile, it can be understood that the data (including but not limited to the data itself, the acquisition or the use of the data) related to the technical scheme should conform to the requirements of the corresponding laws and regulations and related regulations.

Fig. 1 is a flowchart illustrating a service processing method according to an exemplary embodiment of the present disclosure. As shown in fig. 1, an embodiment of the present disclosure provides a service processing method, which may be performed by an electronic device. As shown in fig. 1, the service processing method may include the steps of:

step 101, a service request is obtained, the service request carries a configuration file, the configuration file comprises a plurality of nodes and first attribute parameters of each node, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes.

The service request may be parsed, thereby obtaining a configuration file. The service request may be a query request, a login request, and the like. It is understood that the node execution order means an execution order of application instances corresponding to the nodes. Fig. 2 is a flowchart of a node execution sequence of a plurality of nodes, and referring to fig. 2, an arrow shown in fig. 2 represents a node execution sequence, that is, an application instance of a node 1 is executed before an application instance of a node 2, an execution result of the application instance of the node 2 affects an application instance of an executing node 3 or an application instance of a node 4, if an execution result of the application instance of the node 2 meets a condition of executing the application instance of the node 3, the application instance of the node 3 is executed after the application instance of the node 2 is executed, and further, after the application instance of the node 3 is executed, the application instance of the node 5 and the application instance of the node 6 are sequentially executed; if the execution result of the application instance of the node 2 meets the condition of executing the application instance of the node 4, executing the application instance of the node 4 after the application instance of the node 2 is executed. Wherein the first attribute parameters of the plurality of nodes include parameters for reflecting the order of execution of the nodes, and explanation about the parameters can be made with reference to the following related embodiments.

When executing an application instance corresponding to a node of a selected type, the implementation function may be to perform logic judgment on the input of the node based on a configured rule, and correspondingly enter a next node of the node based on different results of the logic judgment, where the configured rule is a first attribute parameter of the node, and the node of the selected type is, for example, node 2 shown in fig. 2.

See table 1 for a description of the types of nodes and the functions of the types of nodes:

TABLE 1

The Task represents a plug-in type or a service type, the Choice represents a selection type, and the Fail represents a failure type. Specifically, when executing an application instance corresponding to a plug-in type node, it may be implemented to extend other functions on the basis of the original service. When executing the application instance corresponding to the node of the service type, the application instance is used for realizing the function corresponding to the corresponding micro-service. When executing the application instance corresponding to the node of the failure type, the function implemented may be to return a message of failure in service processing to the user layer.

Step 102, executing the application instance corresponding to each node based on the first attribute parameter of each node to obtain the service processing result corresponding to the service request.

It is worth to say that, based on the parameter characterizing the node execution sequence in the first attribute parameter, executing the application instance corresponding to each node according to the node execution sequence characterized by the parameter.

By the technical scheme, the service request is acquired, the service request carries a configuration file, the configuration file comprises a plurality of first attribute parameters, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes; based on the first attribute parameters of each node, executing the application instance corresponding to each node to obtain a service processing result corresponding to the service request, and configuring the flow of the service of the complex logic by configuring multiple types of nodes, so that the complex service requirement can be realized.

In general, for a service request with complex logic, where multiple downstream services may be involved, the execution result between services also affects the execution of the next service, and the platform difference according to which each service depends, support of plug-ins is required, so that the logic processing procedure of multiple services needs to be scheduled in advance.

Thus, before acquiring the service request, the service processing method may further comprise the steps of: displaying a first interface, wherein the first interface comprises a path arrangement area; responding to node adding operation aiming at the path arranging area, and displaying the added nodes in the path arranging area; responding to a first configuration operation aiming at the first attribute parameters of the added nodes, and configuring the first attribute parameters; responding to a second configuration operation aiming at a second attribute parameter of the configuration file, and configuring the second attribute parameter; and responding to the generating operation, and generating a configuration file corresponding to the service request according to the added node, the configuration result of the first attribute parameter and the configuration result of the second attribute parameter.

Referring to fig. 3, fig. 3 is a schematic diagram of a routing area in a first interface, where a "plus" control is displayed for adding nodes downward. As an example, the user may hold the mouse at the "plus" control displayed in the path arrangement area in the first interface, and the path arrangement area is converted from fig. 3 to fig. 4, where Thrift, plugin, choice and Fail are both a control, thread is used to characterize the service type, plugin is used to characterize the add-in type, choice is used to characterize the selection type, fail is used to characterize the failure type, delete is used to Delete the established node. The user may click on either of the Thrift, plugin, choice and Fail controls, triggering an add operation, thereby enabling the addition of the corresponding node, e.g., if the thread control is clicked, the routing area may be as shown in fig. 5. Clicking on the Delete control may trigger a Delete operation, thereby deleting the corresponding node.

As an example, the first configuration operation may be a single click operation or a double click operation for the added node, and the second interface may be presented by responding to the first configuration operation, and the configuration of the first attribute parameter is implemented through the second interface. Referring to fig. 6, fig. 6 is a schematic diagram of a second interface, where the second interface shown in fig. 6 is an interface for configuring the first attribute parameters of the Choice node. In this second interface, node name, node description, and condition rules can all be understood as the first attribute parameters of the Choice node. The node name is used to uniquely identify the node, the node description may be used to describe the function of the node, etc., the condition rule is used to identify the condition for entering the application instance corresponding to the executing next node, and in combination with fig. 2, the step of executing the application instance corresponding to the node 3 is entered when the condition rule corresponding to the node 2 is satisfied, and the step of executing the application instance corresponding to the node 4 is entered when the condition rule corresponding to the node 2 is not satisfied.

In addition, the second attribute parameters may be configured in response to a second configuration operation of the second attribute parameters of the configuration file. The second attribute parameter is used to identify the attribute of the configuration file. As an example, the second configuration operation may also be a single click operation or a double click operation.

It should be noted that the configuration of the first attribute parameter and the configuration of the second attribute parameter are understood as the configuration of the values of the corresponding parameters. For example, taking a first attribute parameter, next, as a Next node parameter configuring a node, next: node 2, is then the value configured by the Next node parameter Next.

And under the condition that the configuration is completed, generating a configuration file corresponding to the service request according to the added node, the configuration result of the first attribute parameter and the configuration result of the second attribute parameter.

As an example, the configuration file may be a JSON format file.

By the method, the nodes in the configuration file, the first attribute parameters of the nodes and the second attribute parameters of the configuration file are configured in a visual mode, the readability is high, the configuration file is convenient to update, and the online period of the updated configuration file is reduced.

In some embodiments, the parameters reflecting the order of execution of the nodes include one of a next node parameter of the node and a parameter for identifying the node as a termination node, and the first attribute parameter of the node further includes at least one of a name parameter of the node, a type parameter of the node, a description parameter of the node, an input parameter of the node, an output parameter of the node, and an input parameter of the node. As an example, the first attribute parameters of a node may be determined with reference to table 2:

TABLE 2

Table 2 is a first attribute parameter of each type, and "necessary" in table 2 indicates a first attribute parameter that must be configured by a node of a corresponding type, and "optional" in table 2 indicates a first attribute parameter that may be configured or not configured by a node of a corresponding type. The Type represents a Type parameter, and a value corresponding to the Type is used for representing the Type of the node; comment represents description parameters, and a value corresponding to the Comment is used for representing description information of the node; the input path characterizes input parameters, the value corresponding to the input path is used for characterizing input parameters of the node, the value corresponding to the output path is used for characterizing output parameters of the node, next is used for characterizing Next node of the node, end is used for characterizing parameters of the termination node, and the value corresponding to End is true, so that the node is the termination node. Parameters are used for representing parameter entering Parameters of the node, and a value corresponding to the Parameters is used for representing Parameters which need to be transferred by an application instance corresponding to the execution node; the resultants characterize the filtering parameters, the values corresponding to the resultants are used for characterizing which variables are extracted from the Task execution results to be used as output, the resultapath refers to putting the Task execution results on the Task input to generate final output, namely, the output path, the Task execution results can be parameter-out, and the parameter-out refers to the value returned by the function or the method from the operation results. The Retry and the Catch represent re-execution parameters, and the value corresponding to the re-execution parameters may represent the maximum number of application instances corresponding to the re-execution node.

Referring to fig. 7, there is shown a schematic diagram of a data flow of an application instance of an executing node, where the node is, for example, a service type node and a plug-in type node shown in fig. 7, the service type node is, for example, RPC (Remote Procedure Call ) shown in fig. 7, and the service type node is, for example, plug in shown in fig. 7. State input in fig. 7 represents input variables of a node, that is, input Path, parameters represent input Parameters of the node, that is, input Parameters required for executing an application instance of the node are fetched from the input Path, and according to the fetched application instance of the input Parameters, a resultase may select variables in an execution Result of the application instance of the node, where the selected variables and the input variables of the node are regarded as Result Path, that is, output Path and State output. In addition, the explanation about part of the features in fig. 7 may refer to the explanation about the same features in the above-described related embodiments.

In some embodiments, the second attribute parameters may include a name parameter of the configuration file and a header node parameter in the configuration file.

Wherein, the name of the configuration file can be uniquely corresponding to the service request; the application instance corresponding to the header node parameter is executed for the first time.

In some embodiments, the method may further comprise: after the first interface is displayed, responding to the import operation, displaying data corresponding to the import operation in a path arrangement area, wherein the data comprises a node flow chart which is obtained by rendering based on the data in the target configuration file, and the node flow chart is used for reflecting the node execution sequence.

As an example, a node flow diagram may be as shown in fig. 2.

It is worth noting that the generated configuration file may be stored in a target location of the electronic device. The target profile is one of the stored profiles, the target profile being determined by the import operation. As an example, the first interface may further include a shortcut area in which a name of a profile already stored on the electronic device may be displayed, and the import operation is triggered based on a selection operation of the name of the profile in the shortcut area, so that corresponding data is displayed in the path orchestration area, which may be a single click operation or a double click operation, as an example.

Thus, the arranged data can be conveniently multiplexed by directly importing the arranged data, namely, multiplexing of the data in the configuration file is realized.

In some embodiments, the step of executing the application instance corresponding to each node based on the first attribute parameter of each node to obtain the service processing result corresponding to the service request may be implemented by the following manner: determining a head node from the nodes based on the first attribute parameters of the nodes, wherein an application instance corresponding to the head node is executed for the first time; determining an application instance corresponding to the head node as a target application instance to be processed, and executing the target application instance; and determining target operation according to target data, and executing the target operation, wherein the target data comprises an execution result of the target application instance or a first attribute parameter of a node corresponding to the target application instance.

The target data may include an execution result of the target application instance or a first attribute parameter of a node corresponding to the target application instance.

The target operation may be an operation of selecting a target node from the nodes, taking an application instance corresponding to the target node as a new target application instance to be processed, executing the target application instance, returning to execute a step of determining the target operation according to the target data, and executing the target operation.

The target operation may be an operation of generating a business processing result corresponding to the execution result.

It should be noted that the first attribute parameter of each node includes one of a next node parameter of the node and a parameter for identifying the node as a termination node, so that the header node can be determined according to the parameters. In yet another example, since the second attribute parameter may include a header node in the configuration file, the header node may also be determined from the nodes based on the second attribute parameter.

Taking a node of Choice type as an example, under the condition that the next node exists in the node corresponding to the target application instance and the execution result of the target application instance is not in error, determining the target operation to select the target node from the nodes, taking the application instance corresponding to the target node as a new target application instance to be processed, executing the target application instance, returning to execute the operation of determining the target operation according to the target data, and executing the steps of the target operation. In this embodiment, the target data may be an execution result of the target application instance, that is, the corresponding next node may be determined according to an execution result of the target application instance of the Choice type node, that is, a matching result of the condition rule of the node. Taking the flowchart of the node execution sequence of the plurality of nodes shown in fig. 2 as an example, after the application instance corresponding to the node 1 is executed, the output result of the node 1 is matched with the condition rule corresponding to the node 2, so as to obtain a matching result (i.e. an execution result). If the matching result represents that the output result of the node 1 is matched with the condition rule, determining that the next node of the node 2 is the node 3, and the application instance corresponding to the node 3 is the target application instance; if the matching result indicates that the output result of the node 1 is not matched with the condition rule, determining that the next node of the node 2 is the node 4, and the application instance corresponding to the node 4 is the target application instance.

If the execution result of the target application instance has an error or there is no next node, the target operation may be determined to be an operation for generating a service processing result corresponding to the execution result. In this embodiment, the target data may be a first attribute parameter of a node corresponding to the target application instance. Continuing taking the flowchart of the node execution sequence of the plurality of nodes shown in fig. 2 as an example, when the target application instance corresponding to the node 4 is executed, the node 4 does not have the next node, that is, the node 4 is the termination node, and then a service processing result corresponding to the execution result of the node 4 can be generated and fed back to the user layer.

And under the condition that the next node exists in the nodes corresponding to the target application examples and the error is not reported in the execution results of the target application examples, determining the target operation as selecting the target node from the nodes, taking the application example corresponding to the target node as a new target application example to be processed, executing the target application example, returning to execute the operation of determining the target operation according to the target data, and executing the steps of the target operation. In this embodiment, continuing with node 3 as an example, node 3 may be a node of the service type. Correspondingly, the target data may be a first attribute parameter of a node corresponding to the target application instance, that is, the node 5 may be determined to be the target node according to the first attribute parameter of the node 3, further, the application instance corresponding to the node 5 is taken as a new target application instance to be processed, and the application instance corresponding to the node 5 is executed.

In this embodiment, the first attribute parameter of the node may include one of a next node parameter of the node and a parameter for identifying the node as a termination node, so that whether the node corresponding to the target application instance exists and which node the next node is can be determined according to one of the next node parameter of the node and the parameter for identifying the node as the termination node.

In some embodiments, the target application instance is executed by: initializing a target application instance according to a second attribute parameter of a node corresponding to the target application instance; and executing the initialized target application instance.

It should be noted that each node may be configured with a function or a method for implementing the corresponding function, where the function or the method may be understood as an application instance. The function or method may be set with an input parameter and an output parameter, and as known from the above, the second attribute parameter of each node corresponds to an input parameter, and the function or method (i.e. the application instance) corresponding to the node may be initialized by using the input parameter of the function corresponding to the node extracted from the second attribute parameter of the node, and then the initialized function or method (i.e. the target application instance) is executed to obtain the output parameter. Through the scheme, the execution of the target application instance is realized.

Based on the same inventive concept, the embodiments of the present disclosure further provide a service processing apparatus, fig. 8 is a block diagram of a service processing apparatus according to an exemplary embodiment of the present disclosure, and referring to fig. 8, the service processing apparatus 800 may include:

an obtaining module 801, configured to obtain a service request, where the service request carries a configuration file, where the configuration file includes a plurality of nodes and first attribute parameters of each node, types of the plurality of nodes include a selection type, a plug-in type, a service type, and a failure type, and the first attribute parameters of the plurality of nodes include parameters for reflecting an execution sequence of the nodes;

and a processing module 802, configured to execute an application instance corresponding to each node based on the first attribute parameter of each node, so as to obtain a service processing result corresponding to the service request.

Optionally, the apparatus 800 further comprises:

the display module is used for displaying a first interface, and the first interface comprises a path arrangement area;

a first response module for responding to node adding operation for the path arranging area and displaying the added nodes in the path arranging area;

the second response module is used for responding to a first configuration operation aiming at the first attribute parameters of the added node and configuring the first attribute parameters;

The third response module is used for responding to a second configuration operation aiming at a second attribute parameter of the configuration file and configuring the second attribute parameter;

and the fourth response module is used for responding to the generating operation and generating a configuration file corresponding to the service request according to the added node, the configuration result of the first attribute parameter and the configuration result of the second attribute parameter.

Optionally, the parameters reflecting the execution sequence of the nodes include one of a next node parameter of the nodes and a parameter for identifying the nodes as termination nodes, and the first attribute parameter of the nodes further includes at least one of a name parameter of the nodes, a type parameter of the nodes, a description parameter of the nodes, an input parameter of the nodes, an output parameter of the nodes, and an input parameter of the nodes.

Optionally, the second attribute parameter includes a name parameter of the configuration file and a header node parameter in the configuration file, and an application instance corresponding to a header node corresponding to the header node parameter is executed for the first time.

Optionally, the apparatus 800 further comprises:

and the fifth response module is used for responding to the importing operation after the first interface is displayed, displaying data corresponding to the importing operation in the path arrangement area, wherein the data comprises a node flow chart which is obtained by rendering based on the data in the target configuration file, and the node flow chart is used for reflecting the node execution sequence.

Optionally, the processing module 802 includes:

a first determining submodule, configured to determine a head node from the nodes based on a first attribute parameter of each node, where an application instance corresponding to the head node is executed first;

the second determining submodule is used for determining the application instance corresponding to the head node as a target application instance to be processed and executing the target application instance;

the third determining submodule is used for determining target operation according to target data and executing the target operation, wherein the target data comprises an execution result of the target application instance or a first attribute parameter of a node corresponding to the target application instance;

the target operation comprises the steps of selecting a target node from the nodes, taking an application instance corresponding to the target node as a new target application instance to be processed, executing the target application instance, returning to execute the steps of determining the target operation according to target data and executing the target operation, or generating a business processing result corresponding to the execution result.

Optionally, the target application instance is executed by:

Initializing the target application instance according to a second attribute parameter of the node corresponding to the target application instance;

and executing the initialized target application instance.

For the implementation of each module in the apparatus 800, reference may be made to related embodiments, which are not described herein.

Based on the same inventive concept, the embodiments of the present disclosure also provide a computer-readable medium having stored thereon a computer program which, when executed by a processing device, implements the steps of the above-described service processing method.

Based on the same inventive concept, the embodiments of the present disclosure further provide an electronic device, including:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to implement the steps of the above-mentioned business processing method.

Referring now to fig. 9, a schematic diagram of an electronic device 900 suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 9 is merely an example, and should not impose any limitations on the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 9, the electronic device 900 may include a processing means (e.g., a central processor, a graphics processor, etc.) 901, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 902 or a program loaded from a storage means 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are also stored. The processing device 901, the ROM 902, and the RAM 903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

In general, the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 907 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 908 including, for example, magnetic tape, hard disk, etc.; and a communication device 909. The communication means 909 may allow the electronic device 900 to communicate wirelessly or by wire with other devices to exchange data. While fig. 9 shows an electronic device 900 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 909, or installed from the storage device 908, or installed from the ROM 902. When executed by the processing device 901, performs the above-described functions defined in the methods of the embodiments of the present disclosure.

It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

In some implementations, the electronic device may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring a service request, wherein the service request carries a configuration file, the configuration file comprises first attribute parameters of a plurality of nodes, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes; and executing the application instance corresponding to each node based on the first attribute parameter of each node to obtain a service processing result corresponding to the service request.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present disclosure may be implemented in software or hardware. The name of a module does not in some cases define the module itself.

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims. The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Claims

1. A method for processing a service, comprising:

2. The method of claim 1, wherein prior to obtaining the service request, the method further comprises:

Displaying a first interface, wherein the first interface comprises a path arrangement area;

responding to node adding operation aiming at the path arranging area, and displaying the added nodes in the path arranging area;

responding to a first configuration operation aiming at a first attribute parameter of the added node, and configuring the first attribute parameter;

responding to a second configuration operation aiming at a second attribute parameter of a configuration file, and configuring the second attribute parameter;

and responding to the generating operation, and generating a configuration file corresponding to the service request according to the added node, the configuration result of the first attribute parameter and the configuration result of the second attribute parameter.

3. The method of claim 2, wherein the parameters reflecting the order of execution of the nodes include one of a next node parameter of the nodes and a parameter identifying the nodes as termination nodes, and wherein the first attribute parameter of the nodes further includes at least one of a name parameter of the nodes, a type parameter of the nodes, a description parameter of the nodes, an input parameter of the nodes, an output parameter of the nodes, and an input parameter of the nodes.

4. The method of claim 2, wherein the second attribute parameter includes a name parameter of the configuration file and a header node parameter in the configuration file, and an application instance corresponding to a header node corresponding to the header node parameter is executed first.

5. The method according to claim 2, wherein the method further comprises:

after the first interface is displayed, responding to an import operation, displaying data corresponding to the import operation in the path arrangement area, wherein the data comprises a node flow chart obtained by rendering based on the data in the target configuration file, and the node flow chart is used for reflecting the node execution sequence.

6. The method of claim 3, wherein executing the application instance corresponding to each node based on the first attribute parameter of each node to obtain the service processing result corresponding to the service request includes:

determining a head node from the nodes based on first attribute parameters of the nodes, wherein an application instance corresponding to the head node is executed for the first time;

determining an application instance corresponding to the head node as a target application instance to be processed, and executing the target application instance;

Determining target operation according to target data, and executing the target operation, wherein the target data comprises an execution result of the target application instance or a first attribute parameter of a node corresponding to the target application instance;

7. The method of claim 6, wherein the target application instance is executed by:

and executing the initialized target application instance.

8. A service processing apparatus, comprising:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a service request, the service request carries a configuration file, the configuration file comprises a plurality of nodes and first attribute parameters of each node, the types of the plurality of nodes comprise a selection type, a plug-in type, a service type and a failure type, and the first attribute parameters of the plurality of nodes comprise parameters for reflecting the execution sequence of the nodes;

9. A computer readable medium on which a computer program is stored, characterized in that the program, when being executed by a processing device, carries out the steps of the method according to any one of claims 1-7.

10. An electronic device, comprising:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to carry out the steps of the method according to any one of claims 1-7.