CN111726420A - Communication method, device, equipment and storage medium based on RPA - Google Patents
Communication method, device, equipment and storage medium based on RPA Download PDFInfo
- Publication number
- CN111726420A CN111726420A CN202010617245.4A CN202010617245A CN111726420A CN 111726420 A CN111726420 A CN 111726420A CN 202010617245 A CN202010617245 A CN 202010617245A CN 111726420 A CN111726420 A CN 111726420A
- Authority
- CN
- China
- Prior art keywords
- message
- task
- request message
- robot
- response message
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Abstract
The embodiment of the invention provides a communication method, a device, equipment and a storage medium based on RPA, relating to the field of RPA, and the specific implementation scheme is as follows: the method is applied to an RPA robot execution end, and comprises the following steps: s1, receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information; s2, processing the task corresponding to the task identification information according to the task processing request message, and generating a corresponding task response message; and S3, sending the task response message to the robot automation process management terminal. Because the management end of the RPA robot can actively send the task processing request message to the execution end of the RPA robot, the pressure of the management end of the RPA robot is effectively reduced, and the efficiency of the execution end of the RPA robot executing tasks is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a communication method, a communication device, communication equipment and a storage medium based on RPA.
Background
Robot Process Automation (RPA), which simulates human operation on a computer through specific robot software and automatically executes process tasks according to rules. The RPA robot can intelligently understand the existing application of an enterprise through a user interface, automate the regular operation based on rules, and complete the work with high repeatability but fixed business logic. Such as automatic repeated reading of mail, mass production of documents and reports, and completion of tedious document inspection.
The RPA robot comprises: the development end of the RPA robot is abbreviated as follows: creator) and an execution end of an RPA robot (abbreviation: worker) and a management end of the RPA robot (abbreviation: commander). The development end of the RPA robot is responsible for developing the RPA robot aiming at specific tasks. And the execution end of the RPA robot is responsible for automatically executing the configured tasks of the RPA robot. And the management end of the RPA robot is used for centralized management and control of data and monitoring the running condition of the RPA robot.
At present, when data interaction is carried out between a management end of an RPA robot and an execution end of the RPA robot, generally, the management end of the RPA robot responds after the execution end of the RPA robot sends a request, and if the frequency of the request sent by the execution end of the RPA robot is too high, the processing pressure of the management end of the RPA robot is higher, the response is not timely, and the real-time performance of the execution end of the RPA robot executing a task is poor.
Disclosure of Invention
Embodiments of the present invention provide a communication method, apparatus, device and storage medium based on an RPA, which solve the technical problem in the prior art that the execution end of an RPA robot sends a request too frequently, so that the processing pressure of the management end of the RPA robot is relatively high, so that the response is not timely, and further, the real-time performance of the execution end of the RPA robot executing a task is poor.
In a first aspect, an embodiment of the present invention provides an RPA-based communication method, where the method is applied to an RPA robot execution end, and the method includes:
s1, receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information;
s2, processing the task corresponding to the task identification information according to the task processing request message, and generating a corresponding task response message;
and S3, sending the task response message to the robot automation process management terminal.
In a second aspect, an embodiment of the present invention provides an RPA-based communication apparatus, the apparatus being located in an RPA robot execution end, the apparatus including:
the message receiving module is used for receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information;
the message generating module is used for processing the task corresponding to the task identification information according to the task processing request message and generating a corresponding task response message;
and the message sending module is used for sending the task response message to the robot automation process management terminal.
In a third aspect, an embodiment of the present invention provides an RPA robot execution end, including: a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the method according to the first aspect.
The embodiment of the invention provides a communication method, a device, equipment and a storage medium based on RPA, which are used for receiving a task processing request message sent by an automatic process management end of a robot, wherein the task processing request message comprises task identification information, processing a task corresponding to the task identification information according to the task processing request message, generating a corresponding task response message and sending the task response message to the automatic process management end of the robot. Because the management end of the RPA robot can actively send the task processing request message to the execution end of the RPA robot, the pressure of the management end of the RPA robot is effectively reduced, and the efficiency of the execution end of the RPA robot executing tasks is improved.
It should be understood that what is described in the summary above is not intended to limit key or critical features of embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of an RPA-based communication method according to an embodiment of the present invention;
fig. 2 is a flowchart of an RPA-based communication method according to a second embodiment of the present invention;
fig. 3 is a flowchart of an RPA-based communication method according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of an RPA-based communication device according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of an RPA-based communication device according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of an RPA robot executing end according to the fifth embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present invention. It should be understood that the drawings and the embodiments of the present invention are illustrative only and are not intended to limit the scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, and in the above-described drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example one
Fig. 1 is a flowchart of an RPA-based communication method according to an embodiment of the present invention, and as shown in fig. 1, an execution main body of this embodiment is an RPA-based communication device, which may be integrated in an RPA robot execution end, which may be coupled in an electronic device, and then the RPA-based communication method according to this embodiment includes the following steps.
And 1-S1, receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information.
In this embodiment, the robot automation process management end is simply referred to as: the management end of the RPA robot is to simply refer to the execution end of the robot automation process as: and an execution end of the RPA robot.
Specifically, in the process of processing services, the user uses the RPA robot to process, and each service is equivalent to one task for the RPA robot. Such as mailing tasks, financial reimbursement tasks, and the like. The RPA robot includes an execution terminal of the RPA robot and a management terminal of the RPA robot. And the execution end of the RPA robot is responsible for automatically executing the configured tasks of the RPA robot. Because the tasks processed by the RPA robot can be various, in order to better manage the RPA robot, the management end of the RPA robot is used for performing centralized management and control on data required by the tasks, monitoring the running conditions of the RPA robot and the execution end of the RPA robot, and issuing a task processing request to the robot automation process management end so that the execution end of the RPA robot processes the tasks.
Specifically, in this embodiment, the execution end of the RPA robot establishes a communication connection with the management end of the RPA robot, the management end of the RPA robot monitors whether a condition for sending a task processing request message to the execution end of the RPA robot is satisfied, and if the condition for sending a task processing request message to the execution end of the RPA robot is satisfied, the execution end of the RPA robot receives the task processing request message sent by the robot automation process management end. The task processing request message includes task identification information.
The task identification information may be a task name, or a number of a plurality of tasks in a management end of the RPA robot, and the like, which is not limited in this embodiment.
In this embodiment, the format of the task processing request message may be a format of a message header and a format of a message body, and the message header and the message body may be partitioned by a separator, such as character string partitioning. The task identification information is placed in the message header.
It is to be understood that the format of the task processing request message may also be other formats, which is not limited in this embodiment.
And 1-S2, processing the task corresponding to the task identification information according to the task processing request message, and generating a corresponding task response message.
In this embodiment, after receiving the task processing request message, the RPA robot execution end acquires the task corresponding to the task identification information, including acquiring flow information of the task, processing data required by the task, and the like, and automatically processes the task corresponding to the task identification information.
And after receiving the task processing request message, generating a task response message, wherein the task response message can be generated when the RPA robot execution end executes the task corresponding to the task identification information. So that the task response message indicates that the RPA robot execution end has successfully started the task.
Similarly, the format of the task response message may be the format of a message header and a message body, and the message header and the message body may be divided by a separator, such as a character string. And the task response message can also carry a response code, and the value of the response code indicates whether the RPA robot execution end successfully responds to the task processing request message. If the response code is 0, the RPA robot execution end successfully responds to the task processing request message, and if the response code is non-zero, the RPA robot execution end unsuccessfully responds to the task processing request message.
And 1-S3, sending the task response message to the robot automation process management terminal.
In this embodiment, the RPA robot execution end sends the task response message to the robot automation flow management end, so that the robot automation flow management end determines whether the RPA robot execution end successfully responds to the task processing request message according to the task response message. For example, the value of the response code in the task response message may be checked to determine whether the RPA robot executive successfully responded to the task processing request message.
It can be understood that, if the RPA robot execution end fails to respond to the task processing request message, the task processing request message may be retransmitted so that the RPA robot execution end successfully responds to the task processing request message, and if the number of times that the RPA robot execution end fails to respond to the task processing request message exceeds a preset threshold, it indicates that the RPA robot execution end is likely to have a fault, and the RPA robot execution end may be troubleshot.
In the communication method based on the RPA provided by this embodiment, a task processing request message sent by a robot automation process management end is received, where the task processing request message includes task identification information, a task corresponding to the task identification information is processed according to the task processing request message, a corresponding task response message is generated, and the task response message is sent to the robot automation process management end. Because the management end of the RPA robot can actively send the task processing request message to the execution end of the RPA robot, the pressure of the management end of the RPA robot is effectively reduced, and the efficiency of the execution end of the RPA robot executing tasks is improved.
Example two
Fig. 2 is a flowchart of an RPA-based communication method according to a second embodiment of the present invention, and as shown in fig. 2, the RPA-based communication method according to the present embodiment is further detailed in steps 1-S1 to 1-S3 on the basis of the RPA-based communication method according to the first embodiment of the present invention, and further includes a step of establishing a communication connection with a robot automation process management terminal, and a step of stopping task processing interaction, and then the RPA-based communication method according to the present embodiment includes the following steps.
And 2-S0, establishing a communication connection with the robot automation process management terminal, wherein the communication connection adopts a WebSocket communication protocol.
Optionally, in this embodiment, because the RPA robot management end and the execution end of the RPA robot communicate frequently, and in order to accelerate the acquisition of data of processing tasks and accelerate the issuance and other interactions of tasks, sometimes it is necessary for the RPA robot management end to be able to actively send a message to the execution end of the RPA robot, and sometimes it is also necessary for the execution end of the RPA robot to actively send a message to the RPA robot management end, in this embodiment, when the execution end of the RPA robot establishes a communication connection with the RPA robot management end, a WebSocket communication protocol is used, and the WebSocket communication protocol supports full-duplex communication between the execution end of the RPA robot and the RPA robot management end.
As an alternative implementation, in this embodiment, steps 2 to S0 include the following steps:
and 2-S01, sending a connection establishment request message to the robot automation process management end, wherein the connection establishment request message comprises login token information of the RPA robot execution end.
The connection establishment request message comprises a message header and a message body, the message header and the message body are divided by adopting a preset character string, and if the preset character string is '\\ r \ n', the connection establishment request message can be represented as follows: -a connection establishment request message header-r/n-j-a connection establishment request message body-j.
In this embodiment, the message header of the connection establishment request message includes the message type and the message identification information. The request message body of the connection establishment request message comprises: the request data identification information, such as identification information that may be verification result data.
Wherein the message type is a connection establishment type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the method further includes, in a header of the connection establishment request message: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, that is, data obtained by encrypting the connection establishment request message. The header of the connection establishment request can be represented as shown in table 1:
table 1: message header example table of connection establishment request message
In this embodiment, the connection establishment request message is carried in an HTTP header, and the HTTP header includes login token information of the RPA robot execution end.
And 2-S02, receiving a connection establishment response message sent by the robot automation process management terminal.
Optionally, in this embodiment, after the robot automation process management end receives the connection establishment request message, the connection establishment request message is encrypted by using a random character string and digitally signed. The robot automation process management terminal checks the signature of the message according to the digital signature, decrypts the message according to the random character string, acquires the login token information of the RPA robot execution terminal after the signature is successfully checked and the decryption is successful, verifies the login token information of the RPA robot execution terminal and generates a verification result. The verification result may be verification success or verification failure. And sending a connection establishment response message to the execution end of the RPA robot.
Wherein the connection establishment response message includes: the message head and the message body are divided by adopting a preset character string, if the preset character string is '\ r \ n', the connection establishment request message can be expressed as follows: -a connection establishment response message header-r/n-j-a connection establishment response message body-j.
Optionally, the connection establishment response message includes, in a header thereof: message type, message identification information.
Wherein the message type is a connection establishment type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the method further includes, in a header of the connection establishment response message: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, that is, data obtained by encrypting the connection establishment response message. The header of the connection setup response message may be represented as shown in table 2:
table 2: message header example table of connection establishment response message
Wherein, the response message body of the connection establishment response message comprises: a response code and a response message, the response code and the response message for determining whether the request message was successfully received. If the response code is zero and the response message is empty, it indicates that the connection establishment request message is successfully received. If the response code is non-zero, the response message may indicate the reason for not receiving the connection establishment request message.
And response data, which may be verification result data, is also included in the connection establishment response message. Such as verification successful data or verification failed data. The response message body of the connection setup response message may be represented as shown in table 3:
table 3: response message body example table of connection establishment response message
And 2-S03, analyzing the connection establishment response message.
Optionally, in this embodiment, before parsing the connection establishment response message, the method further includes:
and carrying out signature verification processing on the message according to the digital signature. And decrypting the message according to the random character string.
In this embodiment, in order to ensure that the communication connection between the execution end of the RPA robot and the management end of the RPA robot is safe and reliable, both the connection establishment request message and the connection establishment response message are digitally signed and encrypted, and after the signature verification is successful and the decryption is successful, the subsequent operations are performed, so that the established communication connection can be ensured to be safe and reliable.
In this embodiment, after the signature verification is successful and the decryption is successful, the connection establishment response message is analyzed, and verification result data is obtained. The verification result data may be verification success data or verification failure data.
And 2-S04, if the connection establishment response message comprises successful verification data corresponding to the login token information, establishing communication connection with the robot automation process management terminal by adopting a WebSocket communication protocol.
Optionally, in this embodiment, if the connection establishment response message includes verification success data corresponding to the login token information, it indicates that the management end of the RPA robot successfully verifies the login token information, and allows the execution end of the RPA robot to establish a connection therewith, and then establishes a communication connection with the robot automation process management end by using a WebSocket communication protocol.
In the RPA-based communication method provided in this embodiment, when establishing a communication connection with an automation process management end of a robot, a WebSocket communication protocol is used, and the WebSocket communication protocol supports full-duplex communication between an execution end of an RPA robot and an RPA robot management end, so that the communication efficiency between the two ends is improved when the communication between the RPA robot management end and the execution end of the RPA robot is frequent. And when the communication connection with the robot automation process management end is established, the connection establishment request message and the connection establishment response message are digitally signed and encrypted, and after the signature verification is successful and the decryption is successful, the subsequent operation is carried out, so that the established communication connection can be ensured to be safe and reliable.
Optionally, in this embodiment, after steps 2 to S0, the method further includes the following steps:
judging whether the condition for sending the heartbeat request message is met; if the condition for sending the heartbeat request message is determined to be met, sending the heartbeat request message to an automatic process management end of the robot; and receiving a heartbeat response message sent by the robot automation process management terminal.
Specifically, in the present embodiment, since communication is frequently performed between the RPA robot execution terminal and the RPA robot management terminal, it is necessary to ensure a long connection between both terminals. Therefore, in this embodiment, a long connection between the two ends is maintained by sending heartbeat messages.
Firstly, the execution end of the RPA robot judges whether the condition for sending the heartbeat request message is met, and the condition for sending the heartbeat request message can be configured in advance. For example, the interval time between two heartbeat request messages may be a preset interval time. The execution end of the RPA robot judges whether the previous heartbeat request message and the current time reach the preset interval time, and if the previous heartbeat request message and the current time reach the preset interval time, the condition of sending the heartbeat request message is determined to be met. And secondly, after the condition that the heartbeat request message sending condition is met is determined, sending the heartbeat request message to the robot automation process management terminal.
Similarly, the heartbeat request message includes: the heartbeat request message comprises a message head and a message body, wherein the message head and the message body are divided by adopting a preset character string, and if the preset character string is '\\ \ r \ n', the heartbeat request message can be expressed as follows: -a heartbeat request message header-r/n | { - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -heartbeat request message body.
Optionally, the heartbeat request message includes, in a header thereof: message type, message identification information.
Wherein the message type is a heartbeat type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the method further includes, in a header of the heartbeat request message: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, namely data obtained by encrypting the heartbeat request message. The format of the header of the heartbeat request message is similar to that of the connection establishment request message in table 1, and is not described herein again.
In this embodiment, after the execution end of the RPA robot sends the heartbeat request message to the robot automation process management end, the management end of the RPA robot determines that the message is the heartbeat request message, generates a heartbeat response message, and sends the heartbeat response message to the execution end of the RPA robot, and the execution end of the RPA robot receives the heartbeat response message sent by the robot automation process management end.
Similarly, the heartbeat response message includes: a message header and a message body. The message header of the heartbeat response message comprises: message type, message identification information. The message type is a heartbeat type. And optionally, further comprising in the header of the heartbeat response message: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, namely data obtained by encrypting the heartbeat response message.
Wherein, the response message body of the heartbeat response message comprises: a response code and a response message. The response code and the response message are used to determine whether the request message was successfully received.
It should be noted that the format of the heartbeat response message is similar to the format of the connection establishment response message, and is not described in detail herein.
It can be understood that, after receiving the heartbeat response message sent by the robot automation process management end, the execution end of the RPA robot performs signature verification and decryption on the heartbeat response message, and after the signature verification and decryption are successful, if it is determined that the heartbeat request message is successfully received through the response code and the response message, it is determined that one-time heartbeat communication between the two ends is completed.
It will be appreciated that the heartbeat communication of the above-described process at both ends is periodic and is maintained after the communication connection is established at both ends to ensure a long connection between the two ends.
And 2-S1, receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information.
Optionally, in this embodiment, the task processing request message includes a message header and a message body, and the message header and the message body are partitioned by using a preset character string. The message type and the message identification information are included in a message header of the task processing request message. The request message body of the task processing request message comprises: data identification information is requested.
Wherein the message type is a task issuing type.
Likewise, optionally, the message header of the task processing request message further includes: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, namely data obtained by encrypting the task processing request message. The format of the message header of the task processing request message is similar to the format of the message header of the connection establishment request message, and is not described in detail herein.
It can be understood that after receiving the task processing request message sent by the robot automation process management terminal, the task processing request message is subjected to signature verification processing according to the digital signature. And decrypting the task processing request message according to the random character string, and obtaining task identification information after the signature verification is successful and the decryption is successful.
And 2-S2, processing the task corresponding to the task identification information according to the task processing request message, and generating a corresponding task response message.
Wherein the task response message includes: the message comprises a message head and a message body, wherein the message head and the message body are divided by adopting preset character strings.
Optionally, the task response message includes, in a header thereof: message type, message identification information. Wherein the message type is a task issuing type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the method further includes, in a header of the task response message: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, namely data obtained by encrypting the task response message. The response message body of the task response message comprises: a response code and a response message, the response code and the response message for determining whether the request message was successfully received.
It can be understood that the formats of the message header and the message body of the task response message are similar to the formats of the message header and the message body of the connection establishment response message, respectively, and are not described in detail herein.
And 2-S3, sending the task response message to the robot automation process management terminal.
Step 2-S4, receiving a task stop processing request message sent by the robot automation process management terminal; the task stop processing request message includes stop task identification information.
In this embodiment, the robot automation process management end monitors whether a task stop condition is satisfied, and if the task stop condition is satisfied, sends a task stop processing request message to the execution end of the RPA robot. The execution end of the RPA robot receives the task stop processing request message.
The condition that the robot automation process management end monitors whether the task stop is met may be monitoring whether a task stop message triggered by a user is received or monitoring whether a preset task stop condition is met, and the like, which is not limited in this embodiment.
Similarly, the task stop processing request message includes a message header and a message body, the message header and the message body are divided by using a preset character string, and optionally, the message header of the task stop processing request message includes: message type, message identification information.
Wherein the message type is a heartbeat type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the method further includes, in a header of the task stop processing request message: random strings and digital signatures. The random character string is data obtained by encrypting a corresponding message, namely data obtained by encrypting a task stop processing request message. The format of the message header of the task stop processing request message is similar to the format of the connection establishment request message in table 1, and is not described herein again.
In this embodiment, the task stop processing request message may be carried in an HTTP header, and the HTTP header includes stop task identification information.
And 2-S5, if the identification information of the current task is determined to be inconsistent with the identification information of the stop task, continuing to execute the current task and generating a corresponding response message of the stop task.
Optionally, in this embodiment, the message is first subjected to signature verification processing according to the digital signature. And decrypting the message according to the random character string. Wherein, the message is a task stop processing request message. And acquiring the stop task identification information after the signature verification is successful and the decryption is successful. And acquiring the identification information of the current task, and judging whether the identification information of the current task is consistent with the identification information of the stop task. If the identification information of the current task is determined to be inconsistent with the identification information of the stop task, the instruction for stopping the current task is not given, and the current task is continuously executed. And generates a corresponding stop task response message.
Wherein the stopping of the task response message includes: the message comprises a message head and a message body, wherein the message head and the message body are divided by adopting preset character strings.
Optionally, the stop task response message includes, in a header thereof: message type, message identification information. Wherein the message type is a stop task type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the method further includes, in a header of the stop task response message: random strings and digital signatures. The random character string is data obtained by encrypting a corresponding message, namely data obtained by encrypting a task stop response message. The response message body of the task stopping response message comprises: a response code and a response message, the response code and the response message for determining whether the request message was successfully received.
It should be noted that the response message body of the stop task response message further includes response data, and the response data may be data in which the identification information of the current task is inconsistent with the stop task identification information.
It can be understood that the formats of the message header and the message body of the task stop response message are similar to the formats of the message header and the message body of the connection establishment response message, and are not described in detail herein.
In this embodiment, if it is determined that the identification information of the current task is consistent with the stop task identification information, the current task is immediately stopped, and a corresponding stop task response message is generated.
The response data of the stop task response message may be data in which the identification information of the current task is consistent with the stop task identification information.
And 2-S6, sending a task stopping response message to the robot automation process management terminal.
In this embodiment, after the task stop response message is sent to the robot automation process management end, the management end of the RPA robot performs signature verification and decryption on the task stop response message, and obtains response data to determine a task identifier currently processed by the execution end of the RPA robot, and the execution end of the RPA robot is better managed according to the task identifier currently processed by the execution end of the RPA robot.
EXAMPLE III
Fig. 3 is a flowchart of an RPA-based communication method according to a third embodiment of the present invention, and as shown in fig. 3, the RPA-based communication method according to the third embodiment of the present invention is based on the RPA-based communication method according to the first embodiment or the second embodiment of the present invention, and after a communication connection with a robot automation process management terminal is established, the RPA robot execution terminal further includes a step of communicating with the RPA robot management terminal in a corresponding automation process, and then the RPA-based communication method according to the present embodiment includes the following steps.
And 3-S0, establishing a communication connection with the robot automation process management terminal, wherein the communication connection adopts a WebSocket communication protocol.
In this embodiment, the implementation manners of steps 3 to S0 are similar to the implementation manners of steps 2 to S0 in the second embodiment of the present invention, and are not described in detail herein.
And 3-S1, sending a data acquisition request message to the robot automation process management terminal.
In this embodiment, when a user has a service that needs to be processed by the RPA robot, the execution end of the RPA robot needs to construct a corresponding automation flow, and the target data of the service is needed when constructing the corresponding automation flow. The target data of the service is stored in advance in the management side of the RPA robot.
First, the execution end of the RPA robot transmits a data acquisition request message to the management end of the RPA robot. The data acquisition request message carries identification information of the target data.
The data acquisition request message comprises a message head and a message body, the message head and the message body are divided by adopting a preset character string, and the message head of the data acquisition request message comprises a message type and message identification information. The request message body of the data acquisition request message comprises: data identification information is requested, such as identification information that may be target data.
Wherein the message type is a data acquisition type. The message identification information is represented by a Unix timestamp and a UTC time.
Optionally, the data obtaining request message further includes, in a header thereof: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, that is, data obtained by encrypting the data acquisition request message.
It can be understood that, after receiving the data acquisition request message at the management end of the RPA robot, the management end performs signature verification and decryption on the data acquisition request message, and after the signature verification is successful and the decryption is successful, analyzes the data acquisition request message to acquire the identification information of the target data, and then acquires the target data corresponding to the identification information, and carries the target data in the response body of the data acquisition response message.
Wherein the data acquisition response message includes: a message header and a message body. The data acquisition response message comprises the following message headers: message type, message identification information. The message type is a data acquisition type. And optionally, the data acquisition response message further includes, in the header: random strings and digital signatures. The random character string is data obtained by encrypting the corresponding message, that is, data obtained by encrypting the data acquisition response message.
Wherein, the response message body of the data acquisition response message comprises: a response code and a response message. The response code and the response message are used to determine whether the request message was successfully received. Further comprising: and response data, wherein the response data is target data.
It should be noted that the format of the data acquisition response message is similar to the format of the connection establishment response message, and is not described in detail herein.
And 3-S2, receiving a data acquisition response message sent by the robot automation process management terminal.
And 3-S3, analyzing the response code and the response message of the data acquisition response message, and determining whether the request message is successfully received, if so, executing the steps 3-S4, otherwise, executing the steps 3-S6.
In this embodiment, after receiving the data acquisition response message, the execution end of the RPA robot performs signature verification processing on the message according to the digital signature. And decrypting the message according to the random character string. The message is a data acquisition response message. And after the signature verification is successful and the decryption is successful, analyzing the response code and the response message of the data acquisition response message.
When the response code of the data acquisition response message and the response message are analyzed, the specific numerical value of the response code and the specific data in the response message are acquired.
And 3-S4, acquiring the target data from the response message body of the data acquisition response message.
In this embodiment, when the response code and the response message of the data acquisition response message are analyzed, if the response code is zero and the response message is empty, it indicates that the data acquisition request message is successfully received. If the response code is non-zero, the response message may indicate the reason for not receiving the data acquisition request message.
In this embodiment, if it is determined that the request message is successfully received after the parsing, which indicates that the response data includes the target data, the target data is obtained from the response data corresponding to the response message body of the data obtaining response message.
And 3-S5, constructing a corresponding automatic flow according to the target data.
In this embodiment, the target data is data required for constructing an automation process of the service, and after the target data is obtained, a corresponding automation process is constructed.
And 3-S6, judging whether the message resending condition is met, if so, executing the steps 3-S7, and if not, ending the step.
In this embodiment, if the response code is non-zero, the response message may indicate a reason for not receiving the data acquisition request message, and it is determined that the request message is not successfully received, and the response data corresponding to the response message body of the data acquisition response message does not include the target data. In order to successfully acquire the target data, it is determined whether a condition for retransmitting the data acquisition request message is satisfied, where the condition for retransmitting the data acquisition request message may be configured in advance, and this is not limited in this embodiment.
And 3-S7, resending the data acquisition request message to the robot automation process management terminal.
In this embodiment, if it is determined that the resending message condition is satisfied, the data acquisition request message is resent to the robot automation process management terminal, so that the target data can be successfully acquired.
In the communication method based on the RPA provided by this embodiment, after establishing a communication connection with a robot automation process management terminal, where the communication connection adopts a WebSocket communication protocol, a data acquisition request message is sent to the robot automation process management terminal; receiving a data acquisition response message sent by an automatic process management end of the robot; analyzing a response code and a response message of the data acquisition response message; if the request message is successfully received after the analysis, acquiring target data from a response message body of the data acquisition response message; constructing a corresponding automatic flow according to the target data, and judging whether a message resending condition is met or not if the request message is determined to be unsuccessfully received after analysis; and if the condition of resending the message is determined to be met, resending the data acquisition request message to the robot automation process management terminal. When new service requirements exist, the execution end of the RPA robot actively acquires target data corresponding to the service from the management end of the RPA robot, and the communication efficiency between the two ends is further improved. And when the target data is not successfully acquired, the target data is successfully acquired from the management end of the RPA robot by means of resending the request, so that the success rate of acquiring the target data is improved.
Example four
Fig. 4 is a schematic structural diagram of an RPA-based communication device according to a fourth embodiment of the present invention, and as shown in fig. 4, an RPA-based communication device 40 according to this embodiment is located in an RPA robot executing end, and the RPA-based communication device includes: a task processing message receiving module 41, a message generating module 42 and a message sending module 43.
The message receiving module 41 is configured to receive a task processing request message sent by the robot automation process management end, where the task processing request message includes task identification information. And the message generating module 42 is configured to process the task corresponding to the task identification information according to the task processing request message, and generate a corresponding task response message. And the message sending module 43 is configured to send the task response message to the robot automation process management end.
The communication device based on RPA provided in this embodiment may execute the technical solution of the method embodiment shown in fig. 1, and the implementation principle and the technical effect are similar, which are not described herein again.
EXAMPLE five
Fig. 4 is a schematic structural diagram of an RPA-based communication device according to a fifth embodiment of the present invention, and as shown in fig. 5, an RPA-based communication device 50 according to this embodiment further includes, on the basis of an RPA-based communication device 40 according to a fourth embodiment of the present invention: a connection establishing module 51, a condition judging module 52, a decryption processing module 53, a signature checking processing module 54 and a flow constructing module 55.
Optionally, the connection establishing module 51 is configured to establish a communication connection with a robot automation process management end, where the communication connection uses a WebSocket communication protocol.
Optionally, the message receiving module 41 is further configured to receive a task stop processing request message sent by the robot automation process management end; the task stop processing request message comprises stop task identification information; the message generating module 42 is further configured to continue executing the current task and generate a corresponding task stop response message if it is determined that the identification information of the current task is inconsistent with the stop task identification information; and the message sending module 43 is further configured to send a task stopping response message to the robot automation process management end.
Optionally, the condition determining module 52 is configured to determine whether a heartbeat request message sending condition is satisfied; a message sending module 41, configured to send a heartbeat request message to the robot automation process management end if it is determined that the heartbeat request message sending condition is met; and the message receiving module 43 is configured to receive a heartbeat response message sent by the robot automation process management end.
Optionally, the connection establishing module 51 is specifically configured to send a connection establishing request message to the robot automation process management end, where the connection establishing request message includes login token information of the RPA robot execution end; receiving a connection establishment response message sent by the robot automation process management terminal; analyzing the connection establishment response message; and if the connection establishment response message comprises verification success data corresponding to the login token information, establishing communication connection with the robot automation process management terminal by adopting a WebSocket communication protocol.
Optionally, any one of the request messages and any one of the response messages includes: the message body and the message head are divided by adopting a preset character string; the message header comprises: message type, message identification information; the request message body of the request message comprises: requesting data identification information; the response message body of the response message comprises: a response code and a response message, the response code and the response message for determining whether the request message was successfully received.
Optionally, the message header further includes: the random character string is data obtained by encrypting the corresponding message;
correspondingly, the decryption processing module 53 is configured to perform decryption processing on the message according to the random character string.
Optionally, the message header further includes: a digital signature;
accordingly, the signature verification processing module 54 is configured to perform signature verification processing on the message according to the digital signature.
Optionally, the message sending module 41 is further configured to send a data acquisition request message to the robot automation process management end; the message receiving module 43 is further configured to receive a data acquisition response message sent by the robot automation process management end; a flow construction module 55, configured to analyze a response code and a response message of the data acquisition response message; if the request message is successfully received after the analysis, acquiring target data from a response message body of the data acquisition response message; and constructing a corresponding automatic process according to the target data.
Optionally, the condition determining module 52 is further configured to determine whether a condition for resending the message is satisfied if it is determined that the request message is not successfully received after the parsing; the message sending module 41 is further configured to resend the data acquisition request message to the robot automation process management terminal if it is determined that the resending message condition is met.
The communication device based on RPA provided in this embodiment may execute the technical solutions of the method embodiments shown in fig. 2 and fig. 3, and the implementation principle and the technical effect are similar, and are not described herein again.
EXAMPLE six
Fig. 6 is a schematic structural diagram of an RPA robot execution end according to a fifth embodiment of the present invention, and as shown in fig. 6, an RPA robot execution end 600 according to a sixth embodiment of the present invention includes: memory 601, processor 602, and computer programs.
Wherein the computer program is stored in the memory 601 and configured to be executed by the processor 602 to implement the RPA-based communication method provided by the fifth embodiment.
The relevant description may be understood by referring to the relevant description and effect corresponding to the steps in fig. 1 to fig. 3, and redundant description is not repeated here.
The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the RPA-based communication method provided in any one of the first to third embodiments of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware form, and can also be realized in a form of hardware and a software functional module.
Program code for implementing the methods of the present invention may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, 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. A 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.
Further, while operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Under 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 limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations 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 disclosed as example forms of implementing the claims.
Claims (13)
1. An RPA-based communication method, which is applied to an RPA robot execution end, and comprises the following steps:
s1, receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information;
s2, processing the task corresponding to the task identification information according to the task processing request message, and generating a corresponding task response message;
and S3, sending the task response message to the robot automation process management terminal.
2. The method according to claim 1, wherein before the S1, further comprising:
and S0, establishing a communication connection with the robot automation process management terminal, wherein the communication connection adopts a WebSocket communication protocol.
3. The method of claim 1, further comprising:
s4, receiving a task stop processing request message sent by the robot automation process management terminal; the task stop processing request message comprises stop task identification information;
s5, if the identification information of the current task is determined to be inconsistent with the identification information of the stop task, continuing to execute the current task and generating a corresponding response message of the stop task;
and S6, sending the task stopping response message to the robot automation process management terminal.
4. The method according to claim 2, wherein after S0, further comprising:
judging whether the condition for sending the heartbeat request message is met;
if the condition of sending the heartbeat request message is determined to be met, sending the heartbeat request message to the robot automation process management terminal;
and receiving a heartbeat response message sent by the robot automation process management terminal.
5. The method according to claim 1, wherein the S0 specifically includes:
s01, sending a connection establishment request message to the robot automation process management end, wherein the connection establishment request message comprises login token information of the RPA robot execution end;
s02, receiving a connection establishment response message sent by the robot automation process management terminal;
s03, analyzing the connection establishment response message;
and S04, if the connection establishment response message includes successful verification data corresponding to the login token information, establishing a communication connection with the robot automation process management terminal by adopting a WebSocket communication protocol.
6. The method according to any of claims 1-5, wherein any one of the request messages and any one of the response messages comprises: the message body and the message head are divided by adopting a preset character string;
the message header comprises: message type, message identification information;
the request message body of the request message comprises: requesting data identification information;
the response message body of the response message comprises: a response code and a response message, the response code and the response message for determining whether the request message was successfully received.
7. The method of claim 6, wherein the message header further comprises: the random character string is data obtained by encrypting the corresponding message;
after receiving any kind of message sent by the robot automation process management terminal, the method further comprises the following steps:
and decrypting the message according to the random character string.
8. The method of claim 6, wherein the message header further comprises: a digital signature;
after receiving any message sent by the robot automation process management terminal, the method further includes:
and checking the signature of the message according to the digital signature.
9. The method of claim 6, further comprising:
a data acquisition request message is sent to the robot automation process management terminal;
receiving a data acquisition response message sent by the robot automation process management terminal;
analyzing the response code and the response message of the data acquisition response message;
if the request message is successfully received after the analysis, acquiring target data from a response message body of the data acquisition response message;
and constructing a corresponding automatic process according to the target data.
10. The method of claim 9, further comprising:
if the request message is determined to be unsuccessfully received after the analysis, judging whether the condition of resending the message is met;
and if the condition of resending the message is determined to be met, resending the data acquisition request message to the robot automation process management terminal.
11. An RPA-based communication device, the device being located in an RPA robot execution end, the device comprising:
the message receiving module is used for receiving a task processing request message sent by the robot automation process management terminal, wherein the task processing request message comprises task identification information;
the message generating module is used for processing the task corresponding to the task identification information according to the task processing request message and generating a corresponding task response message;
and the message sending module is used for sending the task response message to the robot automation process management terminal.
12. An RPA robot effector, comprising:
a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any one of claims 1-10.
13. A computer-readable storage medium, on which a computer program is stored, which computer program is executable by a processor to implement the method according to any one of claims 1-10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010617245.4A CN111726420A (en) | 2020-06-30 | 2020-06-30 | Communication method, device, equipment and storage medium based on RPA |
| CN202011182023.0A CN112217906A (en) | 2020-06-30 | 2020-10-29 | Communication method, device, equipment and storage medium combining AI and RPA |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010617245.4A CN111726420A (en) | 2020-06-30 | 2020-06-30 | Communication method, device, equipment and storage medium based on RPA |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111726420A true CN111726420A (en) | 2020-09-29 |
Family
ID=72570926
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010617245.4A Pending CN111726420A (en) | 2020-06-30 | 2020-06-30 | Communication method, device, equipment and storage medium based on RPA |
| CN202011182023.0A Pending CN112217906A (en) | 2020-06-30 | 2020-10-29 | Communication method, device, equipment and storage medium combining AI and RPA |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011182023.0A Pending CN112217906A (en) | 2020-06-30 | 2020-10-29 | Communication method, device, equipment and storage medium combining AI and RPA |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN111726420A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112434275A (en) * | 2020-11-20 | 2021-03-02 | 中国建设银行股份有限公司 | RPA user authentication method, device, electronic equipment and medium |
| CN112926954A (en) * | 2021-04-26 | 2021-06-08 | 南京微雀信息技术有限公司 | Cross-network government affair information exchange system and method based on artificial intelligent robot |
| CN113220378A (en) * | 2021-05-11 | 2021-08-06 | 中电金信软件有限公司 | Flow processing method and device, electronic equipment, storage medium and system |
| CN113315839A (en) * | 2021-05-28 | 2021-08-27 | 武汉悦学帮网络技术有限公司 | Message processing method, system, device, computer equipment and storage medium |
| CN113761367A (en) * | 2021-09-06 | 2021-12-07 | 海通证券股份有限公司 | System, method and device for pushing robot process automation program and computing equipment |
| CN114666407A (en) * | 2022-03-21 | 2022-06-24 | 上海弘玑信息技术有限公司 | RPA cross-terminal communication method and equipment |
| CN115794345A (en) * | 2022-11-25 | 2023-03-14 | 上海数睿管理咨询有限公司 | Software robot control method, device, electronic equipment and storage medium |
| CN116545977A (en) * | 2023-06-06 | 2023-08-04 | 北京联客触点智能科技有限公司 | RPA operation interaction method based on enterprise micro customization |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113835864A (en) * | 2021-09-29 | 2021-12-24 | 北京来也网络科技有限公司 | Task processing method, device, equipment, medium and system based on RPA and AI |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8156333B2 (en) * | 2008-05-29 | 2012-04-10 | Red Hat, Inc. | Username based authentication security |
| CN105306288A (en) * | 2014-06-27 | 2016-02-03 | 中兴通讯股份有限公司 | WebSocket server monitoring method and device |
| US9774451B2 (en) * | 2015-02-10 | 2017-09-26 | Qualcomm Incorporated | Using secure elements to authenticate devices in point-to-point communication |
| CN106332176A (en) * | 2015-06-17 | 2017-01-11 | 中兴通讯股份有限公司 | Data transmission method, apparatus and system |
| CN106686026A (en) * | 2015-11-06 | 2017-05-17 | 中兴通讯股份有限公司 | Communication method and device |
| WO2017164618A2 (en) * | 2016-03-21 | 2017-09-28 | 엘지전자(주) | Method and apparatus for controlling device by using bluetooth technology |
| US10333868B2 (en) * | 2017-04-14 | 2019-06-25 | Facebook, Inc. | Techniques to automate bot creation for web pages |
| CN111221632A (en) * | 2019-10-15 | 2020-06-02 | 中国平安财产保险股份有限公司 | Distributed parallel task scheduling method and device, computer equipment and storage medium |
-
2020
- 2020-06-30 CN CN202010617245.4A patent/CN111726420A/en active Pending
- 2020-10-29 CN CN202011182023.0A patent/CN112217906A/en active Pending
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112434275A (en) * | 2020-11-20 | 2021-03-02 | 中国建设银行股份有限公司 | RPA user authentication method, device, electronic equipment and medium |
| CN112926954A (en) * | 2021-04-26 | 2021-06-08 | 南京微雀信息技术有限公司 | Cross-network government affair information exchange system and method based on artificial intelligent robot |
| CN113220378A (en) * | 2021-05-11 | 2021-08-06 | 中电金信软件有限公司 | Flow processing method and device, electronic equipment, storage medium and system |
| CN113315839A (en) * | 2021-05-28 | 2021-08-27 | 武汉悦学帮网络技术有限公司 | Message processing method, system, device, computer equipment and storage medium |
| CN113315839B (en) * | 2021-05-28 | 2023-05-02 | 武汉悦学帮网络技术有限公司 | Message processing method, system, device, computer equipment and storage medium |
| CN113761367A (en) * | 2021-09-06 | 2021-12-07 | 海通证券股份有限公司 | System, method and device for pushing robot process automation program and computing equipment |
| CN113761367B (en) * | 2021-09-06 | 2024-02-02 | 海通证券股份有限公司 | Push system, push method, push device and push computing device for robot flow automation program |
| CN114666407A (en) * | 2022-03-21 | 2022-06-24 | 上海弘玑信息技术有限公司 | RPA cross-terminal communication method and equipment |
| CN115794345A (en) * | 2022-11-25 | 2023-03-14 | 上海数睿管理咨询有限公司 | Software robot control method, device, electronic equipment and storage medium |
| CN116545977A (en) * | 2023-06-06 | 2023-08-04 | 北京联客触点智能科技有限公司 | RPA operation interaction method based on enterprise micro customization |
| CN116545977B (en) * | 2023-06-06 | 2024-03-12 | 北京联客触点智能科技有限公司 | RPA operation interaction method based on enterprise micro customization |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112217906A (en) | 2021-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111726420A (en) | Communication method, device, equipment and storage medium based on RPA | |
| CN108600029B (en) | Configuration file updating method and device, terminal equipment and storage medium | |
| CN110601952A (en) | Multi-channel message notification sending method and device | |
| CN109257254B (en) | Network connectivity checking method, device, computer equipment and storage medium | |
| US8060919B2 (en) | Automated password tool and method of use | |
| CN109508295B (en) | Block chain consensus algorithm testing method and device, calculating device and storage medium | |
| CN111538516A (en) | Server power firmware upgrading method, device, equipment and readable storage medium | |
| CN112202635B (en) | Link monitoring method and device, storage medium and electronic device | |
| CN110932918A (en) | Log data acquisition method and device and storage medium | |
| CN112953983A (en) | SFTP transmission method and device | |
| CN108228417B (en) | Internet of vehicles log processing method and device | |
| KR20120102967A (en) | System and method for verifying application | |
| CN111367795A (en) | Performance test method based on benchmark service and related equipment | |
| JP2014183334A (en) | Monitoring system, monitoring server, and monitoring method | |
| CN111221764B (en) | Cross-link data transmission method and system | |
| CN112948195B (en) | Interface testing method, device, electronic equipment and storage medium | |
| CN111182047B (en) | Method and system for transferring files between large data platforms across a network | |
| CN114257632A (en) | Disconnection reconnection method and device, electronic equipment and readable storage medium | |
| CN112333262A (en) | Data updating prompting method and device, computer equipment and readable storage medium | |
| CN110661681B (en) | Buried point design method and device | |
| CN113986661A (en) | Log output method and device, electronic equipment and storage medium | |
| CN113992491B (en) | Application server group operation and maintenance management system, method and device | |
| CN113760635A (en) | Method and device for determining connection abnormity, electronic equipment and storage medium | |
| CN116401425A (en) | Syslog log data acquisition method, device, equipment and medium | |
| CN106851703B (en) | Method and device for processing alarm information by cloud access controller |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200929 |
|
| WD01 | Invention patent application deemed withdrawn after publication |