CN114416305A

CN114416305A - Robot engine implementation method and system and electronic equipment

Info

Publication number: CN114416305A
Application number: CN202111421010.9A
Authority: CN
Inventors: 陈威桦
Original assignee: Beijing Chinasoft International Information Technology Co ltd
Current assignee: Beijing Chinasoft International Information Technology Co ltd
Priority date: 2021-11-26
Filing date: 2021-11-26
Publication date: 2022-04-29

Abstract

The invention discloses a robot engine implementation method, a system and electronic equipment, wherein the method comprises the following steps: acquiring identification information and scheduling drive of each robot; creating corresponding node information for the robot according to the identification information; calling an execution command to execute the robot and the node information and generating an execution result; scheduling the robot according to the execution result and the scheduling drive, and determining a scheduling result; and packaging the node information, the execution result and the scheduling result to generate a robot engine. The invention defines RPA through metadata, standardizes the definition of RPA, and adopts nodes to realize independent functions, thereby increasing the reusability of function development. After the RPA definition is completed, the functions defined by the RPA are executed through dynamic compiling and driving. After one RPA definition is completed, the RPA can be scheduled by other RPAs, thereby realizing complex functions and being applicable to complex scenes. And developing a visual interface for developing and changing the robot and scheduling the RPA robot.

Description

Robot engine implementation method and system and electronic equipment

Technical Field

The invention relates to the technical field of robot process automation, in particular to a robot engine implementation method, a robot engine implementation system and electronic equipment.

Background

Robot process automation is a solution that can simulate humans to perform repetitive tasks. Aiming at the RPA requirements of a certain industry specific scene, such as finance, HR, logistics and the like, manual operation is replaced by an RPA robot. At present, two development methods generally exist for the development of an RPA robot, one is realized by adopting a traditional coding mode and carrying out module-by-module design, coding and testing in a hard coding mode by programmers such as JAVA and Python. One is realized by adopting a third-party RPA product and dragging and pulling through a graphical interface. The scheme realized by the traditional coding mode has the defects of low reusability, long development period and high project risk. The scheme realized by dragging and pulling based on the graphical interface has the defects of simple function, limited use scene and abnormal and difficult understanding of the graphical interface after the flow is complicated.

Disclosure of Invention

In view of this, embodiments of the present invention provide a robot engine implementation method, a robot engine implementation system, and an electronic device, which solve the problems of low reusability and limited use scenarios in the existing robot implementation method.

According to a first aspect, an embodiment of the present invention provides a robot engine implementation method, including:

acquiring identification information and scheduling drive of each robot;

creating corresponding node information for the robot according to the identification information;

calling an execution command to execute the robot and the node information to generate an execution result;

scheduling the robot according to the execution result and the scheduling driver, and determining a scheduling result;

and packaging the node information, the execution result and the scheduling result to generate a robot engine.

The robot engine implementation method provided by the embodiment of the invention defines the RPA through metadata, standardizes the definition of the RPA, and adopts nodes to realize independent functions, thereby increasing the reusability of function development. After the RPA definition is completed, the functions defined by the RPA are executed through dynamic compiling and driving. After one RPA definition is completed, the RPA can be scheduled by other RPAs, thereby realizing complex functions and being applicable to complex scenes. And developing a visual interface for developing and changing the robot and scheduling the RPA robot.

With reference to the first aspect, in a first implementation manner of the first aspect, before the acquiring the identification information of each robot, the method further includes:

acquiring metadata of each robot;

and defining the corresponding robot according to the metadata so as to determine the identification information of the robot.

With reference to the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the node information includes: a start node, an end node and at least one service logic node.

With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the creating, according to the identification information, corresponding node information for the robot includes:

acquiring functional logic of the robot;

and creating corresponding node information for the robot by using the functional logic, wherein the node information starts with the starting node and ends with the ending node, and the functional logic of the robot is realized by using the service logic node.

With reference to the first aspect, in a fourth implementation manner of the first aspect, the invoking the execution command to execute the robot and the node information and generate an execution result includes:

calling an execution command, and dynamically analyzing the robot and the node information to generate a dynamic code;

and dynamically compiling the dynamic code to generate a machine code, wherein the machine code is used for driving the robot to generate an execution result.

With reference to the first aspect, in a fifth implementation manner of the first aspect, the scheduling the robot according to the execution result and the scheduling driver, and determining a scheduling result includes:

acquiring a node arrangement sequence in the execution result;

when the scheduling driving is parallel, the robots are scheduled in parallel, and a scheduling result is determined;

and when the scheduling driver is serial, scheduling the robot according to the node scheduling sequence to determine a scheduling result.

According to a second aspect, an embodiment of the present invention provides a robot engine implementation system, including:

the first processing module is used for acquiring identification information and scheduling drive of each robot;

the second processing module is used for establishing corresponding node information for the robot according to the identification information;

the third processing module is used for calling an execution command to execute the robot and the node information and generating an execution result;

the fourth processing module is used for scheduling the robot according to the execution result and the scheduling drive and determining a scheduling result;

and the fifth processing module is used for packaging the node information, the execution result and the scheduling result to generate a robot engine.

The robot engine implementation system provided by the embodiment of the invention defines the RPA through metadata, standardizes the definition of the RPA, and adopts nodes to realize independent functions, thereby increasing the reusability of function development. After the RPA definition is completed, the functions defined by the RPA are executed through dynamic compiling and driving. After one RPA definition is completed, the RPA can be scheduled by other RPAs, thereby realizing complex functions and being applicable to complex scenes. And developing a visual interface for developing and changing the robot and scheduling the RPA robot.

According to a third aspect, an embodiment of the present invention provides an electronic device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing therein computer instructions, and the processor executing the computer instructions to perform the robot engine implementation method of the first aspect or any one of the embodiments of the first aspect.

According to a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the robot engine implementation method described in the first aspect or any one of the implementation manners of the first aspect.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a flow diagram of a robot engine implementation method according to an embodiment of the present invention;

FIG. 2 is a flow diagram of a robot engine implementing method in accordance with a preferred embodiment of the present invention;

FIG. 3 is a flow chart of a robot engine implementing method according to another preferred embodiment of the present invention;

FIG. 4 is a flow diagram of another robot engine implemented method in accordance with a preferred embodiment of the present invention;

FIG. 5 is a schematic diagram of a robotic engine implementing system according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Rpa (robotic Process automation) robot Process automation is a solution that can simulate humans to perform repetitive tasks. The RPA can realize overall arrangement and automatic service processing and improve the processing efficiency of the service workflow. As three technologies playing important roles in enterprise service, RPA, low code and middle platform respectively play their roles and supplement each other, and jointly promote the development of enterprise supply terminals. The middle platform is used as a middle layer connected with a foreground and background system and forms a strong support for the agility of foreground services. The low-code development platform reduces development cost and flexibly updates iteration by dragging and pulling the quick building application. The RPA completes the last 'one kilometer' of enterprise automation while not invading the original system, reduces the repeated and fussy work tasks and realizes the labor release of the service personnel. Simultaneously, RPA can get through the bottom data as the interface, carries out cross-system data integration, and own possesses well platform and low code attribute, and well platform needs to call a large amount of data in the executive process, can accomplish the buildding of engine again through the low code, and three functions complement each other and assist the enterprise's digital transformation jointly.

The RPA precursor appeared as early as 2000 or so in the form of "key sprites", and was more used in the desktop-level stages of player games, intellectual office, and the like. About 2011, manufacturers who originally introduced RPA products begin to appear in China, and in the same year, the "code stack" of the precursor of the Aliyun RPA was born in Taobao and mainly helps the Alibara group to automate operation, service sale and the like. In 2015, as RPA is applied to China areas where four major accounting offices are located, RPA tools are gradually accepted by domestic financial institutions, in 2 years later, a large number of RPA manufacturers are established, financial science manufacturers and AI manufacturers start to transform into army RPA at this stage, and with the education and product expansion of early manufacturers on market cognition, more enterprises start to learn and accept the value brought by RPA in 2018, and a surge of capital is brought up in 2019. In the future, the development of technology maturity and the mining of application scenarios in different industries still accompany the RPA market for a long time.

Aiming at the RPA requirements of a certain industry specific scene, such as finance, HR, logistics and the like, manual operation is replaced by an RPA robot. At present, two development methods generally exist for the development of an RPA robot, one is realized by adopting a traditional coding mode and carrying out module-by-module design, coding and testing in a hard coding mode by programmers such as JAVA and Python. One is realized by adopting a third-party RPA product and dragging and pulling through a graphical interface. The scheme realized by the traditional coding mode has the defects of low reusability, long development period and high project risk. The scheme realized by dragging and pulling based on the graphical interface has the defects of simple function, limited use scene and abnormal and difficult understanding of the graphical interface after the flow is complicated.

Specifically, the RPA robot implemented by a hard coding method has no reusability, can only encapsulate a public method and an object on a code layer, cannot meet the requirement of rapidly developing the RPA robot, is easy to generate BUG, needs a high technical threshold, and can only implement the development of the RPA technology by professional developers; different robots can be quickly created by the RPA robot realized in a graphical dragging mode, but the functions of the robot are limited, and when the processing logic is complex, the interface is extremely complex, the RPA robot with higher difficulty cannot be developed, and the use scene is limited.

Therefore, in order to reduce the difficulty of RPA robot development, improve the applicable scene of the RPA robot, standardize the RPA robot development, be easily integrated into different systems, be capable of operating independently and be capable of configuring a visual interface to develop the RPA robot. The embodiment provides a robot engine implementation method, which can be used for electronic devices such as computers, mobile phones, tablet computers, and the like. Fig. 1 is a flowchart of a robot engine implementation method according to an embodiment of the present invention, and as shown in fig. 1, the flowchart includes the following steps:

and S11, acquiring the identification information and the scheduling drive of each robot.

In this embodiment, acquiring identification information of all robots, where the identification information is a name, a unique identifier, and a related description of a currently corresponding robot, that is, a Robot (RPA) definition, is a first step of completing robot development. The relevant description may include functions, implementation situations, related notices, and the like of the robot, and the relevant description is only illustrated in this embodiment, and the included parts may be set according to actual needs, which is not limited to this embodiment.

And S12, creating corresponding node information for the robot according to the identification information.

In this embodiment, a robot node needs to be created after the robot definition is completed, where the node information of the robot is information such as an RPA node, an RPA unique identifier, a node name, a node description, a node code execution sequence number, an callout URL, a callout URL execution sequence number, a custom field, and a custom field type, which are defined according to metadata. Specifically, the functions realized by the nodes are composed of the functions of node codes, node code execution sequence numbers, callout URLs and callout URL execution sequence numbers, and the node codes and the callout URLs can exist at the same time. When only one node code and one URL calling code exist, the function of the node is the function of the node code or the URL calling function, and the node code execution needs not to work with the calling URL execution sequence number. When the node code and the callout URL exist at the same time, the node function is the common function of the node code and the callout URL, at the moment, the execution sequence number of the node code and the execution of the callout URL need to be acted, the execution is carried out firstly when the numerical value is smaller, the execution is carried out after the data is larger, and the parallel execution with the same numerical value is carried out. The return information of the node code or the callout URL executed first can be called by the code or the node executed later.

And S13, calling the execution command to execute the robot and the node information, and generating an execution result.

After the node definition is completed, the execution command execution robot can be called to debug and run, and execution information is output. And dynamically analyzing the defined RPA and the node, driving the RPA to run according to the definition, generating an execution record, outputting an execution result, storing an execution log, and storing a scheduling record corresponding to the generation of the RPA scheduling.

And S14, scheduling the robot according to the execution result and the scheduling driver, and determining the scheduling result.

And S15, packaging the node information, the execution result and the scheduling result to generate a robot engine.

The robot engine can be generated after the node information, the execution result and the scheduling result are packaged, that is, the robot definition, the node definition, the RPA execution and the RPA scheduling are packaged into the RPA robot engine, and the RPA robot engine can operate independently or be integrated into a third-party system, and is easy to understand and integrate. The development of the RPA robot is ensured to be easy to develop, integrate and maintain like a common process engine.

The robot engine implementation method provided by this embodiment defines the RPA through metadata, standardizes the definition of the RPA, and implements an independent function by using nodes, thereby increasing the reusability of function development. After the RPA definition is completed, the functions defined by the RPA are executed through dynamic compiling and driving. After one RPA definition is completed, the RPA can be scheduled by other RPAs, thereby realizing complex functions and being applicable to complex scenes. And developing a visual interface for developing and changing the robot and scheduling the RPA robot.

In another embodiment, a robot engine implementation method is further provided, and fig. 2 is another flowchart of the robot engine implementation method according to the embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:

s02, metadata of each robot is acquired. Wherein, the RPA metadata defines the RPA robot, the RPA node and the RPA robot in JSON format.

And S12, defining the corresponding robot according to the metadata to determine the identification information of the robot.

Wherein the RPA robot metadata is used to define the RPA robot. After the metadata is determined in this embodiment, the corresponding robot may be defined according to the metadata to determine the identification information of the robot.

And S21, acquiring the identification information and the scheduling drive of each robot.

Referring to step S11 in detail, this embodiment is not described in detail.

And S22, creating corresponding node information for the robot according to the identification information. Wherein the node information includes: a start node, an end node and at least one service logic node.

Referring to step S12 in detail, this embodiment is not described in detail.

Specifically, the step S22 further includes the following steps:

and S221, acquiring the functional logic of the robot.

S222, corresponding node information is created for the robot by using the functional logic, the node information starts with a start node and ends with an end node, and the functional logic of the robot is realized by using the service logic node.

In this embodiment, the node is a node that splits the RPA into different nodes and modules, each node implements an independent function, including but not limited to a start node, an end node, a JSON node, a file node, a DB node, a JS script node, a Python program node, a JAVA program node, a Linux node, an child robot node, a loop node, and the like, and the RPA robot is composed of a combination of a series of nodes.

And S23, calling the execution command to execute the robot and the node information, and generating an execution result.

Referring to step S13 in detail, this embodiment is not described in detail.

And S24, scheduling the robot according to the execution result and the scheduling driver, and determining the scheduling result.

Referring to step S14 in detail, this embodiment is not described in detail.

And S25, packaging the node information, the execution result and the scheduling result to generate a robot engine.

Referring to step S15 in detail, this embodiment is not described in detail.

In the robot engine implementation method provided in this embodiment, the RPA is defined by metadata, the definition of the RPA is standardized, and an independent function is implemented by using a node, so that the reusability of function development is increased. After the RPA definition is completed, the functions defined by the RPA are executed through dynamic compiling and driving. After one RPA definition is completed, the RPA can be scheduled by other RPAs, thereby realizing complex functions and being applicable to complex scenes. And developing a visual interface for developing and changing the robot and scheduling the RPA robot.

In another embodiment, a robot engine implementation method is further provided, and fig. 3 is another flowchart of the robot engine implementation method according to the embodiment of the present invention, as shown in fig. 3, the flowchart includes the following steps:

and S31, acquiring the identification information and the scheduling drive of each robot.

Referring to step S11 in detail, this embodiment is not described in detail.

And S32, creating corresponding node information for the robot according to the identification information.

Referring to step S12 in detail, this embodiment is not described in detail.

And S33, calling the execution command to execute the robot and the node information, and generating an execution result.

In this embodiment, the step S33 further includes the following steps:

and S331, calling the execution command, dynamically analyzing the robot and the node information, and generating a dynamic code.

And S332, dynamically compiling the dynamic code to generate a machine code, wherein the machine code is used for driving the robot to generate an execution result.

In this embodiment, the execution is to dynamically analyze the defined RPA and the included nodes to generate a dynamic code, and dynamically compile the code to generate a machine code to drive the RPA robot to execute. Dynamically analyzing the RPA and the node, driving the RPA to run according to the definition, generating an execution record, outputting an execution result, storing an execution log, and storing a scheduling record corresponding to the generation of the RPA scheduling

And S34, scheduling the robot according to the execution result and the scheduling driver, and determining the scheduling result.

Referring to step S14 in detail, this embodiment is not described in detail.

And S35, packaging the node information, the execution result and the scheduling result to generate a robot engine.

Referring to step S15 in detail, this embodiment is not described in detail.

In another embodiment, a robot engine implementation method is further provided, and fig. 4 is another flowchart of the robot engine implementation method according to the embodiment of the present invention, as shown in fig. 4, the flowchart includes the following steps:

and S41, acquiring the identification information and the scheduling drive of each robot.

Referring to step S11 in detail, this embodiment is not described in detail.

And S42, creating corresponding node information for the robot according to the identification information.

Referring to step S12 in detail, this embodiment is not described in detail.

And S43, calling the execution command to execute the robot and the node information, and generating an execution result.

Referring to step S13 in detail, this embodiment is not described in detail.

And S44, scheduling the robot according to the execution result and the scheduling driver, and determining the scheduling result.

In this embodiment, the step S44 further includes the following steps:

s441, the node arrangement sequence in the execution result is obtained. And determines whether the type of scheduling driver is parallel or serial.

And S442, when the scheduling driving is parallel, the robots are scheduled in parallel, and the scheduling result is determined.

And S443, when the scheduling driver is serial, scheduling the robot according to the node scheduling order, and determining a scheduling result.

The dispatching is to drive different RPA robots to run in series and in parallel through a dispatching program, the dispatching sequence is the arranging sequence of the nodes, if the nodes are in series, the dispatched robots are started to execute after the execution of the previous node is finished, and if the nodes are in parallel, the dispatched robots are executed in parallel without the sequence. The method comprises the steps of defining RPA robot scheduling according to metadata, scheduling codes, scheduling RPA unique identification, scheduled RPA unique identification, scheduling parameters, execution logs, execution results and scheduling time.

And S45, packaging the node information, the execution result and the scheduling result to generate a robot engine.

Referring to step S15 in detail, this embodiment is not described in detail.

Also provided in this embodiment is a robotic engine implementation system, as used below, the term "module" may implement a combination of software and/or hardware for a predetermined function. While the system described in the embodiments below is preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

The invention discloses a robot engine implementation system, as shown in fig. 5, comprising:

the first processing module 1 is used for acquiring identification information and scheduling drive of each robot;

the second processing module 2 is used for creating corresponding node information for the robot according to the identification information;

the third processing module 3 is used for calling the execution command to execute the robot and the node information and generating an execution result;

the fourth processing module 4 is used for scheduling the robot according to the execution result and the scheduling drive and determining a scheduling result;

and the fifth processing module 5 is configured to encapsulate the node information, the execution result, and the scheduling result, and generate a robot engine.

An embodiment of the present invention further provides an electronic device, please refer to fig. 6, where fig. 6 is a schematic structural diagram of an electronic device according to an alternative embodiment of the present invention, and as shown in fig. 6, the electronic device may include: at least one processor 601, such as a CPU (Central Processing Unit), at least one communication interface 603, memory 604, and at least one communication bus 602. Wherein a communication bus 602 is used to enable the connection communication between these components. The communication interface 603 may include a Display (Display) and a Keyboard (Keyboard), and the optional communication interface 603 may also include a standard wired interface and a standard wireless interface. The Memory 604 may be a high-speed RAM (Random Access Memory) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The memory 604 may optionally be at least one storage device located remotely from the processor 601. Wherein the processor 601 may be in connection with the system described in fig. 5, an application program is stored in the memory 604 and the processor 601 calls the program code stored in the memory 604 for performing any of the above-mentioned method steps.

The communication bus 602 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 602 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.

The memory 604 may include a volatile memory (RAM), such as a random-access memory (RAM); the memory may also include a non-volatile memory (english: non-volatile memory), such as a flash memory (english: flash memory), a hard disk (english: hard disk drive, abbreviated: HDD) or a solid-state drive (english: SSD); the memory 604 may also comprise a combination of the above types of memory.

The processor 601 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP.

The processor 601 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Optionally, the memory 604 is also used for storing program instructions. The processor 601 may call program instructions to implement a robot engine implementation method as shown in the embodiments of the figures of the present application.

The embodiment of the invention also provides a non-transitory computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the robot engine implementation method in any method embodiment. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD) or a Solid State Drive (SSD), etc.; the storage medium may also comprise a combination of memories of the kind described above.

Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A robot engine implementation method is characterized by comprising the following steps:

acquiring identification information and scheduling drive of each robot;

2. The method of claim 1, wherein prior to said obtaining identification information for each robot, the method further comprises:

acquiring metadata of each robot;

3. The method of claim 2, wherein the node information comprises: a start node, an end node and at least one service logic node.

4. The method of claim 3, wherein the creating corresponding node information for the robot according to the identification information comprises:

acquiring functional logic of the robot;

5. The method of claim 1, wherein the invoking the execution command executes the robot and the node information to generate an execution result, comprising:

6. The method of claim 1, wherein scheduling the robot according to the execution results and the scheduling driver, and determining a scheduling result comprises:

acquiring a node arrangement sequence in the execution result;

7. A robotic engine implementing system, comprising:

8. An electronic device, comprising:

a memory and a processor, the memory and the processor being communicatively coupled to each other, the memory having stored therein computer instructions, the processor executing the computer instructions to perform the robot engine-implemented method of any of claims 1-6.

9. A computer-readable storage medium having stored thereon computer instructions for causing a computer to perform the robotic engine implemented method of any of claims 1-6.