CN112235411A - AI-based RPA process control end server communication method, device, equipment and medium - Google Patents

AI-based RPA process control end server communication method, device, equipment and medium Download PDF

Info

Publication number
CN112235411A
CN112235411A CN202011133600.7A CN202011133600A CN112235411A CN 112235411 A CN112235411 A CN 112235411A CN 202011133600 A CN202011133600 A CN 202011133600A CN 112235411 A CN112235411 A CN 112235411A
Authority
CN
China
Prior art keywords
server
service
communication
message
communication 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.)
Granted
Application number
CN202011133600.7A
Other languages
Chinese (zh)
Other versions
CN112235411B (en
Inventor
胡一川
汪冠春
褚瑞
李玮
谢亦东
罗亮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Laiye Network Technology Co Ltd
Laiye Technology Beijing Co Ltd
Original Assignee
Beijing Benying Network Technology Co Ltd
Beijing Laiye Network Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Benying Network Technology Co Ltd, Beijing Laiye Network Technology Co Ltd filed Critical Beijing Benying Network Technology Co Ltd
Publication of CN112235411A publication Critical patent/CN112235411A/en
Application granted granted Critical
Publication of CN112235411B publication Critical patent/CN112235411B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • 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/14—Session management
    • H04L67/141—Setup of application sessions
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

An embodiment of the present disclosure provides an AI-based RPA process control end server communication method, device, and medium. Relates to the technical field of AI and RPA, the method comprises the following steps: a first server receives a service calling request of an RPA flow execution end; if the first server and the second server are in communication connection, the first server sends a communication message requesting for calling the service to the second server; and the first server responds to the communication message of the service calling response returned by the second server, and returns the calling structure in the communication message to the RPA flow execution end. The data type of the communication message between the first server and the second server is byte type. The method of the embodiment of the disclosure improves the efficiency and performance of server communication of the RPA process control end.

Description

AI-based RPA process control end server communication method, device, equipment and medium
Technical Field
The embodiment of the disclosure relates to the field of robot Process Automation, in particular to the fields of Artificial Intelligence (AI) and Robot Process Automation (RPA), and in particular to a server communication method, device, equipment and medium of an RPA Process control end based on AI.
Background
Robot Process Automation (RPA), which simulates human operation on a computer through specific robot software and automatically executes process tasks according to rules. Compared with manual task execution, the RPA not only provides task execution efficiency, but also improves the stability of task execution effect.
Artificial Intelligence (AI) is a new technology science for researching and developing theories, methods, techniques and application systems for simulating, extending and expanding human Intelligence. Research in the field of artificial intelligence includes robotics, language recognition, image recognition, natural language processing, and expert systems, among others. The artificial intelligence technology includes Natural Language Processing (NLP) technology.
The RPA system architecture comprises an RPA process development end, an RPA process execution end and an RPA process control end. The method comprises the following steps that a developer develops a flow task on an RPA flow development end, an RPA flow execution end executes the flow task, and an RPA flow control end manages the flow task and provides corresponding business service for the RPA flow execution end to execute a task flow.
With the increase of the number of the RPA process execution terminals, the number of communication messages between the servers in the RPA process control terminal becomes larger and larger, and it is urgently needed to improve the server communication efficiency of the RPA process control terminal.
Disclosure of Invention
Embodiments of the present disclosure provide a server communication method, apparatus, device, and medium for an RPA process control end based on an AI, so as to solve a problem that a server communication efficiency of the RPA process control end is not high.
In a first aspect, an embodiment of the present disclosure provides a server communication method for an AI-based RPA process control end, where the RPA process control end includes a first server and a second server, the first server is configured to communicate with an RPA process execution end and the second server, the second server is configured to store a service, and a data type of a communication message between the first server and the second server is a byte type; the method comprises the following steps:
the first server receives a service calling request of the RPA flow execution end;
if a communication connection exists between the first server and the second server, the first server sends a communication message requesting to call a service to the second server;
and the first server responds to the received communication message of the service call response returned by the second server, and returns the call result in the communication message of the service call response to the RPA flow execution end.
In one possible implementation, a message header of a communication message between the first server and the second server is fixed in length.
In one possible implementation manner, the message header includes a plurality of preset fields, and a position of each of the fields in the message header is fixed.
In one possible implementation, the field includes a packet type, a communication protocol version number, a message identifier, a service identifier, a message body length, a message time, a message type, a reserved bit, and a check bit.
In a possible implementation manner, before the first server sends the communication message requesting to invoke the service to the second server if the communication connection exists between the first server and the second server, the method further includes:
if no communication connection exists between the first server and the second server, the first server sends a communication message requesting to establish the communication connection to the second server;
the sending, by the first server, a communication message requesting for invoking a service to the second server if a communication connection exists between the first server and the second server includes:
and if the first server receives the communication message of the connection response returned by the second server, the first server sends the communication message of the request for calling the service to the second server.
In one possible implementation, the method further includes:
and acquiring the continuous time length of the first server and the second server which do not perform data transmission, and if the continuous time length is greater than a preset time length threshold value, disconnecting the communication connection between the first server and the second server.
In one possible implementation manner, the sending, by the first server, a communication message requesting to invoke a service to the second server if a communication connection exists between the first server and the second server includes:
if the first server is in communication connection with the second server, the first server acquires a service identifier and a service input parameter from a service calling request according to Natural Language Processing (NLP);
the first server generates a message header of a communication message of the request calling service according to the service identification;
the first server serializes the service input parameters to generate a message body of the communication message requesting to call the service;
and the first server sends the communication message of requesting to call the service to the second server.
In a second aspect, an embodiment of the present disclosure provides a server communication method for an AI-based RPA process control end, where the RPA process control end includes a first server and a second server, the first server is configured to communicate with an RPA process execution end and the second server, the first server is configured to communicate with the RPA process execution end and the second server based on a natural language processing NLP technique, the second server is configured to store a business service, and a data type of a communication message between the first server and the second server is a byte type; the method comprises the following steps:
the second server receives a communication message which is sent by the first server and requests to call the service;
the second server calls the corresponding service according to the communication message of the request calling service to obtain a calling result;
and the second server returns the calling result to the first server by sending a communication message of a service calling response to the first server.
In one possible implementation, the message header length of the communication message between the first server and the second server is fixed.
In one possible implementation manner, the message header includes a plurality of preset fields, and a position of each of the fields in the message header is fixed.
In one possible implementation, the field includes a packet type, a communication protocol version number, a message identifier, a service identifier, a message body length, time information, a message type, a reserved bit, and a check bit.
In one possible implementation manner, before the second server receives the communication message requesting to invoke the service, which is sent by the first server, the method further includes:
the second server receives a communication message which is sent by the first server and requests to establish communication connection;
the second server checks the communication message requesting to establish the communication connection;
and if the verification is passed, the second server establishes communication connection with the first server and sends a communication message of a connection response to the first server.
In one possible implementation, the method further includes:
and acquiring the continuous time length of the first server and the second server which do not transmit data, and if the continuous time length is greater than a preset time length threshold value, disconnecting the communication connection between the first server and the second server.
In a possible implementation manner, the invoking, by the second server, the corresponding service according to the communication message requesting to invoke the service to obtain an invoking result includes:
the second server obtains the service identifier of the service in the message header of the communication message requesting for calling the service;
the second server carries out deserialization on the message body of the communication message requesting for calling the service to obtain a service input parameter;
and the second server calls the business service according to the service identification of the business service and the service input parameter to obtain a calling result of the business service.
In one possible implementation manner, the returning, by the second server, the call result to the first server by sending a communication message of a service call response to the first server includes:
the second server generates a message header of a communication message of the service calling response;
the second server serializes the calling result to generate a message body of the communication message of the service calling response;
and the second server sends the communication message of the service calling response to the first server.
In a third aspect, an embodiment of the present disclosure provides a server communication apparatus of an AI-based RPA flow control end, where the RPA flow control end includes a first server and a second server, the first server is configured to communicate with an RPA flow execution end and the second server, the first server is configured to communicate with the RPA flow execution end and the second server based on a natural language processing NLP technique, the second server is configured to store a business service, and a data type of a communication message between the first server and the second server is a byte type; the device comprises:
a receiving module, configured to receive, by the first server, a service invocation request of the RPA process execution end;
a sending module, configured to send, by the first server to the second server, a communication message requesting for invoking a service if a communication connection exists between the first server and the second server; and the first server responds to the received communication message of the service call response returned by the second server, and returns the call result in the communication message of the service call response to the RPA flow execution end.
In a fourth aspect, an embodiment of the present disclosure provides a server communication apparatus of an AI-based RPA process control end, where the RPA process control end includes a first server and a second server, the first server is configured to communicate with an RPA process execution end and the second server, the first server is configured to communicate with the RPA process execution end and the second server based on a natural language processing NLP technique, the second server is configured to store a business service, and a data type of a communication message between the first server and the second server is a byte type; the device comprises:
the receiving module is used for receiving a communication message which is sent by the first server and requests for calling the service by the second server;
the calling module is used for calling the corresponding service by the second server according to the communication message of the request calling service to obtain a calling result;
and the sending module is used for returning the calling result to the first server by the second server through sending the communication message of the service calling response to the first server.
In a fifth aspect, an embodiment of the present disclosure provides a server, including: a transceiver, a memory, and a processor;
the transceiver is used for data transceiving;
the memory is to store program instructions;
the processor is configured to invoke program instructions in the memory to perform the method according to the first aspect, the possible implementations of the first aspect, the second aspect, or the possible implementations of the second aspect.
In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium on which a computer program is stored, which, when executed, implements the method according to the first aspect, the possible implementations of the first aspect, the second aspect, or the possible implementations of the second aspect.
In a seventh aspect, an embodiment of the present disclosure provides a program product including instructions, where the program product includes a computer program that, when executed by a processor, implements the method according to the first aspect, the possible implementations of the first aspect, the second aspect, or the possible implementations of the second aspect.
In the server communication method, device, equipment and medium of the AI-based RPA process control end provided by the embodiments of the present disclosure, the RPA process control end includes a first server and a second server, the first server is used for communicating with the RPA process executor and the second server, the second server is used for storing a service, and a message type of a communication message between the first server and the second server is a byte type. And in response to receiving the communication message of the service calling response returned by the second server, the first server returns the calling result in the communication message of the service calling response to the RPA flow execution end. Therefore, by distinguishing the server in the RPA flow execution end into the first server and the second server, the orderliness of server communication in the RPA flow execution end is provided; the communication is carried out based on the communication messages of the byte type, the data redundancy of the communication messages is reduced, and the communication connection between the first server and the second server can be multiplexed under the condition that the first server and the second server are kept connected, so that the communication efficiency of the server at the RPA process control end and the communication performance under high concurrence are improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic diagram of an RPA system architecture according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a server communication method of an AI-based RPA process control end according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of a server communication method of an AI-based RPA process control end according to another embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a server communication method of an AI-based RPA process control end according to another embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a server communication device at an AI-based RPA process control end according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a server communication device at an AI-based RPA process control end according to another embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a server according to an embodiment of the present disclosure;
fig. 8 is a block diagram of a server communication device 800 at an AI-based RPA process control end according to an embodiment of the disclosure.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
First, terms related to embodiments of the present disclosure are explained:
service: also called a functional service, service or functional module, refers to a function that can perform certain business operations. For example, a business service for querying bills, a staff service for face recognition. Business services are typically developed by developers and call interfaces are designed for the business services. Different business services can be mutually invoked.
The server communication method of the AI-based RPA process control end according to an embodiment of the present disclosure may be applied to the RPA system architecture diagram shown in fig. 1. As shown in fig. 1, the RPA system architecture includes: an RPA process development end 101, an RPA process execution end 102, and an RPA process control end 103. The RPA process development end 101 is configured to provide a development platform for developers, and provide developed and completed process tasks to the RPA process execution end 102 and the RPA process control end 103. The RPA process execution terminal 102 is used for executing process tasks. The RPA flow control terminal 103 manages the flow tasks and the execution of the flow tasks. In the process of executing the flow task by the RPA flow execution terminal 102, the RPA flow control terminal 103 may also provide a service to the RPA flow execution terminal. For example, the RPA process executing end 102 may invoke a business service for generating a table on the RPA process control end when executing a process task for generating a table.
The RPA process development end 101 and the RPA process execution end 102 may be terminal devices such as a computer and a tablet computer, and the RPA process control end 103 may be a server group.
The RPA process control end 103 includes a first server 104 and a second server 105, where the first server 104 is configured to communicate with the RPA process execution end 102 and one or more second servers 105, and the second servers 105 are configured to store business services.
Therefore, by dividing the servers in the RPA flow control end 103 into the first server 104 for communicating with the RPA flow execution end 102 and the second server 105 for storing the business service, the order of server communication in the RPA flow execution end 103 can be effectively improved, and the communication efficiency between the servers in the RPA flow execution end 103 can be further improved.
In the server communication method of the AI-based RPA flow control end provided by the embodiment of the present disclosure, the first server sends a communication message requesting for invoking a service to the second server maintaining a communication connection with itself in response to receiving a service invocation request from the RPA flow execution end, and the first server returns an invocation result in the communication message of the service invocation response to the RPA flow execution end in response to receiving a communication message of the service invocation response returned by the second server. The message type of the communication message between the first server and the second server is byte type. Therefore, data redundancy in the communication message is effectively reduced through the byte type, the communication efficiency between the first server and the second server is improved, and under the condition that the first server and the second server are kept connected, the communication connection between the first server and the second server can be multiplexed, so that the communication performance of the RPA flow control end under high concurrency is improved.
The following describes technical solutions of the embodiments of the present disclosure and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present disclosure will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart illustrating a server communication method of an AI-based RPA process control end according to an embodiment of the disclosure. As shown in fig. 2, the method includes:
s201, the first server receives a service calling request of an RPA process execution end.
The service calling request comprises a service identifier and a service input parameter of the service called by the RPA flow execution end. For example, the RPA process execution end requests to invoke a business service for querying positions of employees of a company, and the service invocation request includes a service identifier of the business service and a job number of the employees of the company, and the job number of the employees of the company is a service input parameter.
S202, if the first server and the second server are in communication connection, the first server sends a communication message requesting for calling the service to the second server.
The data type of the communication message between the first server and the second server is a byte type, and compared with the text type communication message, the byte type communication message basically has no redundant data, such as no line feed character and no blank space, so that the communication message is more concise, and the communication efficiency between the first server and the second server is improved.
The byte type can be binary, octal or hexadecimal.
Specifically, the first server may extract, according to a service identifier in the received service invocation request, the service identifier in the service invocation request through a Natural Language Processing (NLP) technique in an actual execution process, and further determine a second server where a service corresponding to the service identifier is located. If a communication connection exists between the first server and the second server, the first server may convert the data type of the service identification and the service input parameter to a byte type. And taking the converted service identification and the converted service input parameter as the message content of the communication message requesting to call the service. A communication message requesting invocation of the service is sent to the second server. As can be seen, in the case that a communication connection exists between the first server and the second server, the first server may send a plurality of communication messages requesting to invoke a service to the second server according to the communication connection, so as to implement multiplexing of the communication connection.
S203, the first server responds to the received communication message of the service calling response returned by the second server, and returns the calling result in the communication message of the service calling response to the RPA flow execution end.
Specifically, after receiving the communication message of the first server requesting for invoking the service, the second server may invoke the corresponding service according to the service identifier in the communication message requesting for invoking the service, and input the service input parameter in the communication message requesting for invoking the service to obtain an invocation result, where the service server in this embodiment may also recognize the service input parameter according to the NLP technique, and determine the invocation result according to the input parameter, for example, a deep learning model is obtained based on the NLP technique training, and an input of the deep learning model is the service input parameter and an output of the deep learning model is a corresponding invocation result, so that a corresponding invocation result may be obtained according to the deep learning model. And the second server converts the data type of the calling result into a byte type and takes the converted service calling as the message content of the communication message of the service calling response. The second server returns a communication message of the service invocation response to the first server.
Specifically, the first server obtains the call result from the message body of the communication message of the service call response in response to receiving the communication message of the service call response returned by the second server, and returns the call result to the RPA flow execution end.
In the embodiment of the disclosure, data redundancy in the communication message is effectively reduced through the byte type, the communication efficiency between the first server and the second server is improved, and the communication connection between the first server and the second server can be multiplexed under the condition that the first server and the second server are kept connected, so that the communication performance of the RPA process control end under high concurrency is improved.
Fig. 3 is a flowchart illustrating a server communication method of an AI-based RPA process control end according to another embodiment of the disclosure. As shown in fig. 3, the method includes:
s301, the second server receives a communication message which is sent by the first server and requests to call the service.
S302, the second server calls the corresponding service according to the communication message of the request calling service to obtain a calling result.
Specifically, after receiving the communication message of the first server requesting for invoking the service, the second server may invoke the corresponding service according to the service identifier in the communication message requesting for invoking the service, and input the service input parameter in the communication message requesting for invoking the service to obtain an invoking result.
As an example, the second server may invoke the service identifier in the communication message requesting to invoke the service, where the second server may invoke the service for generating the table according to the NLP technology, and may input the table parameter (e.g., the table size) in the communication message requesting to invoke the service into the service for generating the table.
S303, the second server sends the communication message of the service calling response to the first server so as to return the calling result to the first server.
Specifically, the second server converts the data type of the call result into a byte type, and uses the converted service call as the message content of the communication message of the service call response. The second server returns a communication message of the service invocation response to the first server.
In the embodiment of the disclosure, data redundancy in the communication message is effectively reduced through the byte type, the communication efficiency between the first server and the second server is improved, and the communication connection between the first server and the second server can be multiplexed under the condition that the first server and the second server are kept connected, so that the communication performance of the RPA process control end under high concurrency is improved.
Fig. 4 is a flowchart illustrating a server communication method of an AI-based RPA process control end according to another embodiment of the disclosure. As shown in fig. 4, the method includes:
s401, the first server receives a service calling request of an RPA process execution end.
Specifically, step S301 may refer to the detailed description of step S201, and is not repeated herein.
S402, if the communication connection does not exist between the first server and the second server, the first server sends a communication message requesting to establish the communication connection to the second server.
Specifically, the first server may obtain, from the service invocation request of the RPA flow execution end, a service identifier of the service requested to be invoked by the RPA flow execution end, and determine the second server where the service corresponding to the service identifier is located. If a communication connection does not exist between the first server and the determined second server, the first server may send a communication message to the second server requesting establishment of the communication connection.
And S403, the second server checks the communication message requesting to establish the communication connection.
Specifically, the communication message requesting to establish the communication connection includes a check bit. When the second server receives the communication message which is sent by the first server and requests to establish the communication connection, the check bit can be checked through a preset check algorithm, so that the check on the communication message which requests to establish the communication connection is further realized, whether the communication message which requests to establish the communication connection is correct is determined, and the accuracy of the communication between the first server and the second server is improved.
In one possible embodiment, the Check algorithm may use a Cyclic Redundancy Check (CRC) Check algorithm to improve the accuracy of checking the communication message.
S404, if the verification is passed, the second server establishes communication connection with the first server.
Specifically, if the verification passes, the second server establishes a communication connection with the first server, otherwise, the second server may send a communication message indicating that the communication connection establishment fails to the first server.
S405, the second server sends the communication message of the connection response to the first server.
Specifically, after establishing the communication connection with the first server, the second server may send a communication message of the connection response to the first server, so that the first server knows that the communication connection is established successfully in time.
S406, the first server sends a communication message requesting to call the service to the second server.
Specifically, after the communication connection is established between the first server and the second server, the first server may convert the data type of the service representation and the service input parameter in the service invocation request into a byte type, and use the converted service identifier and the converted service input parameter as the message content of the communication message requesting to invoke the service. A communication message requesting invocation of the service is sent to the second server.
S407, the second server calls the corresponding service according to the communication message of the request call service to obtain a call result.
Specifically, after receiving the communication message of the first server requesting for invoking the service, the second server may invoke the corresponding service according to the service identifier in the communication message requesting for invoking the service, and input the service input parameter in the communication message requesting for invoking the service to obtain an invoking result.
S408, the second server sends the communication message of the service calling response to the first server so as to return the calling result to the first server.
Specifically, the second server converts the data type of the call result into a byte type, and uses the converted service call as the message content of the communication message of the service call response. The second server returns a communication message of the service invocation response to the first server.
S409, the first server returns the calling result in the communication message of the service calling response to the RPA flow executing end.
Specifically, the first server obtains the call result from the message body of the communication message of the service call response in response to receiving the communication message of the service call response returned by the second server, and returns the call result to the RPA flow execution end.
The data type of the communication message between the first server and the second server is a byte type, and compared with the text type communication message, the byte type communication message basically has no redundant data, such as no line feed character and no blank space, so that the communication message is more concise, and the communication efficiency between the first server and the second server is improved.
Wherein the byte type may be binary, octal, or hexadecimal.
In a possible implementation manner, the length of the message header of the communication message between the first server and the second server is fixed, so that by fixing the length of the message header, the first server and the second server can conveniently perform read-write operation on the message header (for example, read a service identifier from the message header and write the service identifier into the message header), thereby improving the server communication efficiency of the RPA process control end.
In a feasible implementation manner, the message header comprises a plurality of preset fields, and the positions of the fields in the message header are fixed, so that the content of the message header is standardized by fixing the positions of the top ends in the message header, and the first server and the second server can accurately read the content of the fields, thereby effectively improving the server communication efficiency of the RPA process control end.
Further, the fields comprise message types, communication protocol version numbers, message identifications, service identifications, message body lengths, message time, message types, reserved bits and check bits, so that the integrity of the content of the message header is guaranteed and the compactness of the content of the message header is improved by fixing the positions of the fields in the message header, the first server and the second server can accurately read the content of each field, and the server communication performance of the RPA process control end is effectively improved.
The message types comprise a request message and a response message; the communication protocol version number is a version number of a communication protocol based on the current communication of the first server and the second server; the message identification is the only identification of the communication message; the service identifier is used for recording the service identifier of the service requested by the communication message or the service identifier of the service to which the returned calling result belongs; the message body length is used for recording the length of a message body in the communication message; the message time is the sending time or the generating time of the communication message; the message type comprises a connection request, a connection response, a service call and a service call response; reserving bits for expanding a message header in a subsequent development process; the check bits are used to check the communication message.
For example, the structure of the message header of the communication message between the first server and the second server may be as shown in table 1, where the left side of table 1 is the position of each field in the message header, and the right side is the meaning of each field. In a communication message whose message type is a connection message, a connection response, or a service invocation response, the service identification is 0.
TABLE 1
Figure BDA0002735954430000111
Figure BDA0002735954430000121
Specifically, in a communication message which is sent by a first server to a second server and requests for communication connection, a message type in a message header is a request message, a service identifier is 0, a message body length is 0, and the message type is a connection request. In the communication message of the connection response returned to the first server by the second server, the message type in the message header is a response message, the service identifier is 0, the message body length is 0, and the message type is the connection response. In a communication message which is sent by a first server to a second server and requests for calling service, the message type in the message header is a request message, the service identifier is obtained by converting the byte type of the service identifier in the service calling request sent by an RPA flow execution end, the message type is service calling, and the message body is obtained by converting the byte type of the service input parameter in the service calling request sent by the RPA flow execution end. In the communication message of the service call response sent to the first server by the second server, the message type in the message header is a response message, the service identifier is 0, the message type is the service call response, and the message body is obtained by performing byte type conversion on the call result.
In a possible implementation manner, a preset fixed header and a message header are added, and a result obtained by the addition is processed through a preset verification algorithm to obtain data of a verification bit in the message header, so that a verification effect is improved. For example, the fixed header "49 f785a939c5475594c7ffb2a54f173 f" is added to the 2 nd to 59 th bytes of the message header shown in table 1 to obtain an addition result, and the addition result is processed by the CRC check algorithm to obtain the 60 th to 63 th bytes of the check bits of the message header shown in table 1.
In a possible implementation manner, in the process of generating a communication message requesting for invoking a service, the first server may convert a data type of a service identifier in a service invocation request sent by an RPA flow execution end into a byte type, and determine the converted service identifier as a service identifier in a message header; the data type of the service input parameter in the service calling request sent by the RPA flow execution end can be converted into the byte type, the converted service input parameter is determined as the message body, and the message body length in the message header is determined according to the length of the message body. The message header and the message body are combined to obtain the communication message requesting for calling the service, so that redundant data in the communication message are reduced, the analysis efficiency of the communication message is improved, and the communication efficiency of the first server and the second server is improved.
In a possible implementation manner, in the process of generating the communication message of the service invocation response, the second server may generate a message header (where the service identifier is 0) according to a result of the message header, convert a data type of a invocation result of the service into a byte type, determine the converted invocation result as a message body, and determine a message body length in the message header according to the length of the message body. The message header and the message body are combined to obtain the communication message of the service calling response, so that redundant data in the communication message are reduced, the analysis efficiency of the communication message is improved, and the communication efficiency of the first server and the second server is improved. The calling result includes whether the business service is normally called or not, and output data (for example, the work number of the inquired company employee) after the business service is called.
In a possible implementation manner, in the process of converting the data type of the service input parameter into the byte type or converting the data type of the call result into the byte type, the service input parameter may be serialized to obtain the service input parameter of the byte type, or the call result may be serialized to obtain the call result of the byte type, so as to improve the byte type conversion efficiency.
Therefore, after receiving the communication message of the first server requesting to invoke the service, the second server may obtain the service input parameter in the communication message by deserializing the message body of the communication message. After receiving the communication message of the service call response of the second server, the first server can obtain the call result in the communication message by deserializing the message body of the communication message.
In one possible embodiment, Protocol Buffers (abbreviated as Protocol Buffers) may be used to serialize the service input parameters or the call results, so as to improve the serialization effect. The ProtoBuf is a method which is not limited by languages and platforms and can expand serialized structured data.
In one embodiment, the continuous time length of data transmission failure between the first server and the second server is obtained, and if the continuous time length is greater than a preset time length threshold value, the communication connection between the first server and the second server is disconnected. Therefore, when data transmission exists between the first server and the second server, the communication connection between the first server and the second server is maintained, so that the communication connection between the first server and the second server can carry out multiple data transmission, the multiplexing of the communication connection is realized, and the capability of the RPA flow control end for coping with high concurrency situations is improved. When data transmission does not exist between the first server and the second server for a long time, the communication connection is disconnected, and the power consumption of the RPA process control end is reduced.
In the embodiment of the disclosure, by means of byte types and message header results of communication messages, data redundancy in the communication messages is effectively reduced, communication efficiency between the first server and the second server is improved, and under the condition that the first server and the second server are kept connected, communication connection between the first server and the second server can be multiplexed, so that communication performance of the RPA process control end under high concurrency is improved.
Fig. 5 is a schematic structural diagram of a server communication device of an AI-based RPA process control end according to an embodiment of the present disclosure, where the RPA process control end includes a first server and a second server, the first server is used for communicating with an RPA process execution end and the second server, the second server is used for storing a business service, and a data type of a communication message between the first server and the second server is a byte type. As shown in fig. 5, the apparatus includes:
a receiving module 501, configured to receive, by a first server, a service invocation request of an RPA process execution end;
a sending module 502, configured to send, by a first server, a communication message requesting to invoke a service to a second server if a communication connection exists between the first server and the second server; and the first server responds to the received communication message of the service calling response returned by the second server, and returns the calling result in the communication message of the service calling response to the RPA flow execution end.
In one possible embodiment, the message header length of the communication message between the first server and the second server is fixed.
In one possible embodiment, the message header includes a plurality of preset fields, and each field is fixed in position in the message header.
In one possible embodiment, the fields include a message type, a communication protocol version number, a message identification, a service identification, a message body length, a message time, a message type, reserved bits, and check bits.
In a possible implementation, the sending module 502 is further configured to: if the communication connection does not exist between the first server and the second server, the first server sends a communication message requesting to establish the communication connection to the second server; and if the first server receives the communication message of the connection response returned by the second server, the first server sends the communication message of the request for calling the service to the second server.
In one possible embodiment, the apparatus further comprises a connection module for: and acquiring the continuous time length of the first server and the second server which do not transmit data, and disconnecting the communication connection between the first server and the second server if the continuous time length is greater than a preset time length threshold value.
In a possible implementation, the sending module 502 is specifically configured to: if the first server is in communication connection with the second server, the first server acquires a service identifier and a service input parameter from a service calling request according to the natural language processing NLP; the first server generates a message header of a communication message requesting for calling the service according to the service identifier; the first server serializes the service input parameters to generate a message body of a communication message requesting to call the service; the first server sends a communication message to the second server requesting invocation of the service.
Fig. 6 is a schematic structural diagram of a server communication device of an AI-based RPA process control end according to another embodiment of the present disclosure, where the RPA process control end includes a first server and a second server, the first server is used for communicating with an RPA process execution end and the second server, the second server is used for storing a business service, and a data type of a communication message between the first server and the second server is a byte type. As shown in fig. 6, the apparatus includes:
a receiving module 601, configured to receive, by a second server, a communication message requesting for invoking a service, where the communication message is sent by a first server;
the calling module 602 is configured to call, by the second server, the corresponding service according to the communication message requesting for calling the service, and obtain a calling result;
the sending module 603 is configured to send, by the second server, a communication message of the service invocation response to the first server, so as to return the invocation result to the first server.
In one possible embodiment, the message header length of the communication message between the first server and the second server is fixed.
In one possible embodiment, the message header includes a plurality of preset fields, and each field is fixed in position in the message header.
In one possible embodiment, the fields include a message type, a communication protocol version number, a message identification, a service identification, a message body length, time information, a message type, reserved bits, and check bits.
In one possible embodiment, the apparatus further comprises a connection module for: receiving a communication message which is sent by a first server and requests to establish communication connection; the second server checks the communication message requesting to establish the communication connection; and if the verification is passed, the second server establishes communication connection with the first server and sends a communication message of a connection response to the first server.
In one possible embodiment, the connection module is further configured to: and acquiring the continuous time length of the first server and the second server which do not transmit data, and disconnecting the communication connection between the first server and the second server if the continuous time length is greater than a preset time length threshold value.
The server communication device of the AI-based RPA process control end provided in fig. 5 and 6 may implement the corresponding method embodiments, and the implementation principle and technical effect are similar, which are not described herein again.
Fig. 7 is a schematic structural diagram of a server according to an embodiment of the present disclosure. As shown in fig. 7, the server may include: a transceiver 701, a processor 702, and a memory 703. The transceiver 701 is used for data transceiving, the memory 703 is used for storing computer execution instructions, and the processor 702 executes the computer program to implement the method according to any of the embodiments described above.
The transceivers described above may be wired or wireless network interfaces. The processor 702 may be a general-purpose processor, including a central processing unit CPU, a Network Processor (NP), and the like; but also a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The memory 703 may include a Random Access Memory (RAM) and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
An embodiment of the present disclosure also provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of any of the embodiments described above.
An embodiment of the present disclosure also provides a program product comprising a computer program, the computer program being stored in a storage medium, the computer program being readable from the storage medium by at least one processor, the at least one processor being capable of implementing the method of any of the above embodiments when executing the computer program.
Fig. 8 is a block diagram of a server communication device 800 at an AI-based RPA process control end according to an embodiment of the disclosure. For example, the apparatus 800 may be provided as a server or a computer. Referring to fig. 8, apparatus 800 includes a processing component 801 that further includes one or more processors and memory resources, represented by memory 802, for storing instructions, such as application programs, that are executable by the processing component 801. The application programs stored in memory 802 may include one or more modules that each correspond to a set of instructions. Further, the processing component 801 is configured to execute instructions to perform the method of any of the embodiments described above.
The device 800 may also include a power component 803 configured to perform power management of the device 800, a wired or wireless network interface 804 configured to connect the device 800 to a network, and an input/output (I/O) interface 805. The apparatus 800 may operate based on an operating system stored in the memory 802, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
In the embodiments of the present disclosure, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein, A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula, the character "/" indicates that the preceding and following related objects are in a relationship of "division". "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
It is to be understood that references to "first" and "second" in the embodiments of the present disclosure are merely for convenience of description and do not limit the scope of the embodiments of the present disclosure.
It is to be understood that the various numerical designations referred to in the embodiments of the disclosure are merely for convenience of description and are not intended to limit the scope of the embodiments of the disclosure.
It should be understood that, in the embodiment of the present disclosure, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiment of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. The embodiments of the disclosure are intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (19)

1. The server communication method of the RPA flow control end based on AI is characterized in that the RPA flow control end comprises a first server and a second server, the first server is used for communicating with an RPA flow execution end and the second server, the second server is used for storing business services, and the data type of communication messages between the first server and the second server is byte type; the method comprises the following steps:
the first server receives a service calling request of the RPA flow execution end;
if a communication connection exists between the first server and the second server, the first server sends a communication message requesting to call a service to the second server;
and the first server responds to the received communication message of the service call response returned by the second server, and returns the call result in the communication message of the service call response to the RPA flow execution end.
2. The method of claim 1, wherein a header length of a communication message between the first server and the second server is fixed.
3. The method of claim 2, wherein the message header includes a plurality of predetermined fields therein, each of the fields being fixed in position in the message header.
4. The method of claim 3, wherein the fields comprise a packet type, a communication protocol version number, a message identifier, a service identifier, a message body length, a message time, a message type, reserved bits, and check bits.
5. The method of any of claims 1-4, wherein before the first server sends a communication message to the second server requesting invocation of a service if a communication connection exists between the first server and the second server, the method further comprises:
if no communication connection exists between the first server and the second server, the first server sends a communication message requesting to establish the communication connection to the second server;
the sending, by the first server, a communication message requesting for invoking a service to the second server if a communication connection exists between the first server and the second server includes:
and if the first server receives the communication message of the connection response returned by the second server, the first server sends the communication message of the request for calling the service to the second server.
6. The method according to any one of claims 1-4, further comprising:
and acquiring the continuous time length of the first server and the second server which do not perform data transmission, and if the continuous time length is greater than a preset time length threshold value, disconnecting the communication connection between the first server and the second server.
7. The method according to any one of claims 1-4, wherein the sending, by the first server, the communication message requesting the invocation of the service to the second server if the communication connection exists between the first server and the second server comprises:
if the first server is in communication connection with the second server, the first server acquires a service identifier and a service input parameter from a service calling request according to Natural Language Processing (NLP);
the first server generates a message header of a communication message of the request calling service according to the service identification;
the first server serializes the service input parameters to generate a message body of the communication message requesting to call the service;
and the first server sends the communication message of requesting to call the service to the second server.
8. The server communication method for the RPA process executing end is characterized in that the RPA process control end comprises a first server and a second server, the first server is used for communicating with the RPA process executing end and the second server, the second server is used for storing business services, and the data type of communication messages between the first server and the second server is byte type; the method comprises the following steps:
the second server receives a communication message which is sent by the first server and requests to call the service;
the second server calls the corresponding service according to the communication message of the request calling service to obtain a calling result;
and the second server sends a communication message of a service calling response to the first server so as to return the calling result to the first server.
9. The method of claim 8, wherein a header length of a communication message between the first server and the second server is fixed.
10. The method of claim 9, wherein the message header includes a plurality of predetermined fields therein, each of the fields being fixed in position in the message header.
11. The method of claim 10, wherein the fields comprise a packet type, a communication protocol version number, a message identifier, a service identifier, a message body length, time information, a message type, reserved bits, and check bits.
12. The method of any of claims 8-11, wherein prior to the second server receiving the communication message sent by the first server requesting invocation of the service, the method further comprises:
the second server receives a communication message which is sent by the first server and requests to establish communication connection;
the second server checks the communication message requesting to establish the communication connection;
and if the verification is passed, the second server establishes communication connection with the first server and sends a communication message of a connection response to the first server.
13. The method according to any one of claims 8-11, further comprising:
and acquiring the continuous time length of the first server and the second server which do not perform data transmission, and if the continuous time length is greater than a preset time length threshold value, disconnecting the communication connection between the first server and the second server.
14. The method according to any one of claims 8 to 11, wherein the second server invokes the corresponding service according to the communication message requesting to invoke the service, and obtains an invocation result, including:
the second server obtains the service identifier of the service in the message header of the communication message requesting for calling the service;
the second server carries out deserialization on the message body of the communication message requesting for calling the service to obtain a service input parameter;
and the second server calls the business service according to the service identification of the business service and the service input parameter to obtain a calling result of the business service.
15. The method according to any one of claims 8 to 11, wherein the second server sends a communication message of a service invocation response to the first server to return the invocation result to the first server, including:
the second server generates a message header of a communication message of the service calling response;
the second server serializes the calling result to generate a message body of the communication message of the service calling response;
and the second server sends the communication message of the service calling response to the first server.
16. The server communication device of the RPA flow control end based on AI is characterized in that the RPA flow control end comprises a first server and a second server, the first server is used for communicating with an RPA flow execution end and the second server, the second server is used for storing business services, and the data type of communication messages between the first server and the second server is byte type; the device comprises:
a receiving module, configured to receive, by the first server, a service invocation request of the RPA process execution end;
a sending module, configured to send, by the first server to the second server, a communication message requesting for invoking a service if a communication connection exists between the first server and the second server; and the first server responds to the received communication message of the service call response returned by the second server, and returns the call result in the communication message of the service call response to the RPA flow execution end.
17. The server communication device of the RPA flow control end based on AI is characterized in that the RPA flow control end comprises a first server and a second server, the first server is used for communicating with an RPA flow execution end and the second server, the first server is used for communicating with the RPA flow execution end and the second server based on Natural Language Processing (NLP) technology, and the second server is used for storing business services; the data type of the communication message between the first server and the second server is byte type; the device comprises:
the receiving module is used for receiving a communication message which is sent by the first server and requests for calling the service by the second server;
the calling module is used for calling the corresponding service by the second server according to the communication message of the request calling service to obtain a calling result;
and the sending module is used for sending the communication message of the service calling response to the first server by the second server so as to return the calling result to the first server.
18. A server, comprising: a transceiver, a memory, and a processor;
the transceiver is used for data transceiving;
the memory is to store program instructions;
the processor is configured to invoke program instructions in the memory to perform the method of any of claims 1-7 or any of claims 8-15.
19. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program; the computer program, when executed, implements the method of any of claims 1-7 or any of claims 8-15.
CN202011133600.7A 2020-06-30 2020-10-21 Server communication method, device, equipment and medium of RPA flow control terminal based on AI Active CN112235411B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010610274.8A CN111756851A (en) 2020-06-30 2020-06-30 Server communication method, device, equipment and medium for RPA process control end
CN2020106102748 2020-06-30

Publications (2)

Publication Number Publication Date
CN112235411A true CN112235411A (en) 2021-01-15
CN112235411B CN112235411B (en) 2023-10-10

Family

ID=72678187

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202010610274.8A Pending CN111756851A (en) 2020-06-30 2020-06-30 Server communication method, device, equipment and medium for RPA process control end
CN202011133600.7A Active CN112235411B (en) 2020-06-30 2020-10-21 Server communication method, device, equipment and medium of RPA flow control terminal based on AI

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202010610274.8A Pending CN111756851A (en) 2020-06-30 2020-06-30 Server communication method, device, equipment and medium for RPA process control end

Country Status (1)

Country Link
CN (2) CN111756851A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023115738A1 (en) * 2021-12-23 2023-06-29 北京来也网络科技有限公司 Service interface configuration method and device combining rpa and ai

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180329399A1 (en) * 2017-05-11 2018-11-15 Global Eprocure Robotic process automation for supply chain management operations
US20190057203A1 (en) * 2017-08-16 2019-02-21 Bank Of America Corporation Robotic process automation using controller execution model
CN110099031A (en) * 2018-01-30 2019-08-06 普天信息技术有限公司 A kind of service calling method, device and micro services platform
US20190373653A1 (en) * 2017-01-23 2019-12-05 Lg Electronics Inc. Bluetooth communication method and apparatus
US20200065334A1 (en) * 2018-08-21 2020-02-27 Kylie.ai, Inc. Artificial intelligence communications agent
US20200074329A1 (en) * 2018-08-29 2020-03-05 Accenture Global Solutions Limited Intelligent adaptor service in unified automation platforms for robotic process automation
JP2020091512A (en) * 2018-12-03 2020-06-11 ＢｉｚｔｅＸ株式会社 Apparatus, method and program for automating business process with operation to intra-company server on intra-company network

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190373653A1 (en) * 2017-01-23 2019-12-05 Lg Electronics Inc. Bluetooth communication method and apparatus
US20180329399A1 (en) * 2017-05-11 2018-11-15 Global Eprocure Robotic process automation for supply chain management operations
US20190057203A1 (en) * 2017-08-16 2019-02-21 Bank Of America Corporation Robotic process automation using controller execution model
CN110099031A (en) * 2018-01-30 2019-08-06 普天信息技术有限公司 A kind of service calling method, device and micro services platform
US20200065334A1 (en) * 2018-08-21 2020-02-27 Kylie.ai, Inc. Artificial intelligence communications agent
US20200074329A1 (en) * 2018-08-29 2020-03-05 Accenture Global Solutions Limited Intelligent adaptor service in unified automation platforms for robotic process automation
JP2020091512A (en) * 2018-12-03 2020-06-11 ＢｉｚｔｅＸ株式会社 Apparatus, method and program for automating business process with operation to intra-company server on intra-company network

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023115738A1 (en) * 2021-12-23 2023-06-29 北京来也网络科技有限公司 Service interface configuration method and device combining rpa and ai

Also Published As

Publication number Publication date
CN112235411B (en) 2023-10-10
CN111756851A (en) 2020-10-09

Similar Documents

Publication Publication Date Title
CN107645562B (en) Data transmission processing method, device, equipment and system
US10467321B2 (en) Systems and methods for dynamic C# serialization
CN109308224B (en) Cross-platform data communication and cross-platform data processing method, device and system
US11948021B2 (en) Method for inter-core communication, processor, inter-core communication system and computer readable storage medium
CN111369237B (en) Data processing method and device and computer storage medium
CN111736867A (en) FPGA updating device, method and storage medium
CN112035344A (en) Multi-scenario test method, device, equipment and computer readable storage medium
CN114331416A (en) Data processing method and device, electronic equipment and storage medium
CN112235411B (en) Server communication method, device, equipment and medium of RPA flow control terminal based on AI
CN113010381A (en) Method and equipment for managing components
CN113760562A (en) Link tracking method, device, system, server and storage medium
CN111314805B (en) Debugging method and device for intercommunication OMCI (OMCI) messages of GPON (gigabit passive optical network) system
CN115460265A (en) Interface calling method, device, equipment and medium
CN113676521A (en) Service request response method and device and electronic equipment
US20220365762A1 (en) Neural network model conversion method server, and storage medium
CN115022403B (en) Information processing system for multi-channel service agent
CN116800807A (en) GPU resource remote calling method, device, equipment and storage medium
CN117472553B (en) Workflow processing method, device, processing equipment and readable storage medium
CN115509146B (en) Distributed communication resource integration method for flight maintenance simulator
CN116743589B (en) Cloud host migration method and device and electronic equipment
US20230315533A1 (en) Ai computing platform, ai computing method, and ai cloud computing system
CN115623070A (en) IDL message processing method and device, electronic equipment and storage medium
CN116132385A (en) Data forwarding method, device, computer equipment and storage medium
CN114117010A (en) NLP task processing method and device, terminal equipment and storage medium
CN116483479A (en) Method, device, equipment and medium for multi-dimension calling interface

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CP03 Change of name, title or address

Address after: 1902, 19 / F, China Electronics Building, 3 Danling Road, Haidian District, Beijing 100080

Patentee after: BEIJING LAIYE NETWORK TECHNOLOGY Co.,Ltd.

Country or region after: China

Patentee after: Laiye Technology (Beijing) Co.,Ltd.

Address before: 1902, 19 / F, China Electronics Building, 3 Danling Road, Haidian District, Beijing 100080

Patentee before: BEIJING LAIYE NETWORK TECHNOLOGY Co.,Ltd.

Country or region before: China

Patentee before: BEIJING BENYING NETWORK TECHNOLOGY Co.,Ltd.

CP03 Change of name, title or address