CN112235411B - Server communication method, device, equipment and medium of RPA flow control terminal based on AI - Google Patents

Server communication method, device, equipment and medium of RPA flow control terminal based on AI Download PDF

Info

Publication number
CN112235411B
CN112235411B CN202011133600.7A CN202011133600A CN112235411B CN 112235411 B CN112235411 B CN 112235411B CN 202011133600 A CN202011133600 A CN 202011133600A CN 112235411 B CN112235411 B CN 112235411B
Authority
CN
China
Prior art keywords
server
service
message
communication
call
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202011133600.7A
Other languages
Chinese (zh)
Other versions
CN112235411A (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

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]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The embodiment of the disclosure provides server communication method equipment and medium of an RPA flow control terminal based on AI. Relates to the technical field of AI and RPA, and the method comprises the following steps: the method comprises the steps that a first server receives a service call request of an RPA flow execution end; if communication connection exists between the first server and the second server, the first server sends a communication message requesting to call the service to the second server; and the first server responds to the communication message of the service call response returned by the second server, and returns a call structure in the communication message to the RPA flow execution end. Wherein the data type of the communication message between the first server and the second server is a byte type. The method of the embodiment of the disclosure improves the efficiency and performance of server communication of the RPA flow control end.

Description

Server communication method, device, equipment and medium of RPA flow control terminal based on AI
Technical Field
The embodiment of the disclosure relates to the field of robot process automation, in particular to the fields of artificial intelligence (Artificial Intelligence, abbreviated as AI) and robot process automation (Robotic Process Automation, abbreviated as RPA), and especially relates to a server communication method, device, equipment and medium of an AI-based RPA process control end.
Background
Robot process automation (Robotic process automation), RPA for short, simulates the operation of a human on a computer by 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 (Artificial Intelligence, AI for short) is a new technical science to research, develop 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, expert systems, and the like. Among them, artificial intelligence techniques include natural language processing (Natural Language Processing, abbreviated as NLP) techniques.
The RPA system architecture comprises an RPA flow development end, an RPA flow execution end and an RPA flow control end. The developer develops the flow task on the RPA flow development end, the RPA flow execution end executes the flow task, and the RPA flow control end manages the flow task and provides corresponding business service for the RPA flow execution end executing the task flow.
With the increase of the number of RPA flow execution ends, the number of communication messages between servers in the RPA flow control end is becoming larger, and there is a need to improve the server communication efficiency of the RPA flow control end.
Disclosure of Invention
The embodiment of the disclosure provides a server communication method, device, equipment and medium of an RPA flow control end based on AI, which are used for solving the problem of low server communication efficiency of the RPA flow control end.
In a first aspect, an embodiment of the present disclosure provides a server communication method of an RPA flow control end based on AI, 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 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 first server receives a service call request of the RPA flow execution end;
if 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 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 length of a communication message between the first server and the second server is fixed.
In one possible implementation, the message header includes a plurality of preset fields, and the position of each field in the message header is fixed.
In one possible implementation, 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, a reserved bit, and a check bit.
In one possible implementation manner, if a communication connection exists between the first server and the second server, before the first server sends a communication message requesting to invoke a service to 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 communication connection to the second server;
and if the first server and the second server have communication connection, the first server sends a communication message for requesting to call a service to the second server, wherein the communication message comprises:
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 call service request to the second server.
In one possible implementation, the method further includes:
and acquiring continuous time length of the first server and the second server which do not perform data transmission, and disconnecting communication connection between the first server and the second server if the continuous time length is larger than a preset time length threshold value.
In one possible implementation manner, if a communication connection exists between the first server and the second server, the first server sends a communication message requesting to invoke a service to the second server, including:
if communication connection exists between the first server and the second server, the first server acquires a service identifier and a service input parameter from a service call request according to natural language processing NLP;
the first server generates a message header of the communication message requesting to call the service according to the service identifier;
the first server sequences the service input parameters to generate a message body of the communication message requesting to call the service;
The first server sends the communication message requesting to call a service to the second server.
In a second aspect, an embodiment of the present disclosure provides a server communication method of an RPA flow control end based on AI, 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 technology, 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:
a second server receives a communication message which is sent by the first server and requests to call a service;
the second server calls corresponding business service according to the communication message of the service call request to obtain a call 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, a message header length of a communication message between the first server and the second server is fixed.
In one possible implementation, the message header includes a plurality of preset fields, and the position of each field in the message header is fixed.
In one possible implementation, 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, a reserved bit, and a check bit.
In one possible implementation manner, before the second server receives the communication message sent by the first server and requesting to call a service, 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 verifies the communication message requesting to establish 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 continuous time length of the first server and the second server which do not perform data transmission, and disconnecting communication connection between the first server and the second server if the continuous time length is larger than a preset time length threshold value.
In one possible implementation manner, the calling, by the second server, the corresponding business service according to the communication message of the service calling request, to obtain a calling result includes:
the second server obtains the service identifier of the business service in the message header of the communication message requesting to call the service;
the second server deserializes the message body of the communication message requesting to call the service to obtain service input parameters;
and the second server calls the business service according to the service identifier of the business service and the service input parameter to obtain a call result of the business service.
In one possible implementation manner, 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, including:
the second server generates a message header of the communication message of the service call response;
the second server sequences the calling result to generate a message body of the communication message of the service calling response;
the second server sends a communication message of the service invocation response to the first server.
In a third aspect, an embodiment of the present disclosure provides a server communication device of an RPA flow control end based on AI, 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 technology, 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 device comprises:
the receiving module is used for receiving the service call request of the RPA flow execution end by the first server;
a sending module, configured to send a communication message requesting to invoke a service to the second server if there is a communication connection between the first server and the second server; and the first server responds to the 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 device of an RPA flow control end based on AI, 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 technology, 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 device comprises:
the receiving module is used for receiving the communication message which is sent by the first server and is used for requesting to call the service by the second server;
the calling module is used for calling the corresponding business service according to the communication message of the service calling request by the second server to obtain a calling result;
and the sending module is used for returning the calling result to the first server by sending a communication message of a service calling response to the first server by the second server.
In a fifth aspect, embodiments of the present disclosure provide a server, comprising: a transceiver, a memory, and a processor;
The transceiver is used for receiving and transmitting data;
the memory is used for storing program instructions;
the processor is configured to invoke program instructions in the memory to perform a method as described in the first aspect, each possible implementation of the first aspect, the second aspect, or each possible implementation of the second aspect.
In a sixth aspect, embodiments of the present disclosure provide a computer readable storage medium having stored thereon a computer program which, when executed, implements a method as described in 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, embodiments of the present disclosure provide a program product comprising instructions, the program product comprising a computer program which, when executed by a processor, implements the method of the first aspect, each possible implementation of the first aspect, the second aspect, or each possible implementation of the second aspect.
In the server communication method, device, equipment and medium of the RPA flow control end based on AI provided in the embodiments of the present disclosure, the RPA flow control end includes a first server and a second server, the first server is used for communicating with the RPA flow executor and the second server, the second server is used for storing business services, and a message type of a communication message between the first server and the second server is a byte type. In response to receiving a service call request of the RPA flow executor, the first server sends a communication message requesting to call a service to the second server, and in response to receiving a communication message of a service call response returned by the second server, the first server returns a call result in the communication message of the service call response to the RPA flow executor. Therefore, by dividing the servers in the RPA procedure execution end into a first server and a second server, the order of server communication in the RPA procedure execution end is provided; communication is carried out based on the byte type communication information, so that the data redundancy of the communication information is reduced, 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, and further the server communication efficiency and the high-concurrency communication performance of the RPA flow control end are improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the 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 disclosure;
fig. 2 is a flowchart of a server communication method of an AI-based RPA flow control end according to an embodiment of the disclosure;
fig. 3 is a flowchart of a server communication method of an AI-based RPA flow control end according to another embodiment of the disclosure;
fig. 4 is a flowchart of a server communication method of an AI-based RPA flow control end according to another embodiment of the disclosure;
fig. 5 is a schematic structural diagram of a server communication device of an AI-based RPA flow control end according to an embodiment of the disclosure;
fig. 6 is a schematic structural diagram of a server communication device at an AI-based RPA flow control end according to another embodiment of the disclosure;
FIG. 7 is a schematic diagram of a server according to an embodiment of the disclosure;
fig. 8 is a block diagram of a server communication device 800 of an AI-based RPA flow control end according to an embodiment of the disclosure.
Specific embodiments of the present disclosure have been shown by way of the above drawings and will be described in more detail below. These drawings and the written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
First, terms involved in embodiments of the present disclosure will be explained:
service services: also referred to as a functional service, or functional module, refers to a function that can perform certain business operations. For example, a business service for inquiring bills, a business operator service for face recognition. Business services are typically developed by developers and call interfaces are designed for business services. Different business services can be called mutually.
The server communication method of the AI-based RPA flow control end provided in an embodiment of the present disclosure may be applicable to the RPA system architecture schematic diagram shown in fig. 1. As shown in fig. 1, the RPA system architecture includes: an RPA procedure development terminal 101, an RPA procedure execution terminal 102, and an RPA procedure control terminal 103. The RPA flow development terminal 101 is configured to provide a development platform for a developer, and provide development-completed flow tasks to the RPA flow execution terminal 102 and the RPA flow control terminal 103. The RPA procedure execution end 102 is configured to execute a procedure task. The RPA flow control terminal 103 manages execution of the flow tasks. In the process of executing the process task by the RPA process execution end 102, the RPA process control end 103 may also provide a service to the RPA process execution end. For example, when the RPA flow executing end 102 performs a flow task for generating a table, the RPA flow executing end may call a business service for generating a table.
The RPA flow development terminal 101 and the RPA flow execution terminal 102 may be terminal devices such as a computer and a tablet computer, and the RPA flow control terminal 103 may be a server group.
The RPA flow 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 flow execution end 102 and one or more second servers 105, and the second server 105 is 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 business services, the order of the server communication in the RPA flow execution end 103 can be effectively improved, and further the communication efficiency between the servers in the RPA flow execution end 103 can be improved.
In the server communication method of the AI-based RPA flow control end provided by the embodiment of the present disclosure, a first server sends a communication message requesting to call a service to a second server which is in communication connection with itself in response to receiving a service call request from an RPA flow execution end, and the first server returns a call result in the communication message of the service call response to the RPA flow execution end in response to receiving the communication message of the service call response returned by the second server. Wherein the message type of the communication message between the first server and the second server is a byte type. Therefore, the 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 reused, so that the communication performance of the RPA flow control end under high concurrency is improved.
The following describes in detail, with specific embodiments, a technical solution of an embodiment of the present disclosure and how the technical solution of the present disclosure solves the foregoing technical problems. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present disclosure will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a server communication method of an AI-based RPA flow control end according to an embodiment of the disclosure. As shown in fig. 2, the method includes:
s201, a first server receives a service call request of an RPA flow execution end.
The service calling request comprises a service identifier and a service input parameter of the service requested to be called by the RPA flow executing end. For example, when the RPA process execution end requests to call and inquire the service of the job position of the company employee, the service call request includes the service identifier of the service and the job number of the company employee, and the job number of the company employee is a service input parameter.
S202, if communication connection exists between the first server and the second server, the first server sends a communication message requesting to call the service to the second server.
Compared with the text type communication message, the byte type communication message has no redundant data basically, such as no line feed and no 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 may be binary, octal, hexadecimal, among others.
Specifically, the first server may extract, according to the service identifier in the received service call request, the service identifier in the service call request through a natural language processing (Natural Language Processing, abbreviated as NLP) technology in an actual execution process, and further determine a second server where the service corresponding to the service identifier is located. The first server may convert the data type of the service identification and the service input parameters to byte type if a communication connection exists between the first server and the second server. And taking the converted service identifier and the converted service input parameter as message contents of a communication message for requesting to call the service. And sending a communication message requesting to call the service to the second server. It can be seen that, when a communication connection exists between the first server and the second server, the first server may send a plurality of communication messages requesting for invoking 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 communication message of the service call response returned by the second server, and a call result in the communication message of the service call response is returned to the RPA flow execution end.
Specifically, after receiving the communication message of the first server requesting to call the service, the second server may call the corresponding service according to the service identifier in the communication message requesting to call the service, and input the service input parameter in the communication message requesting to call the service to obtain a call result, where the service server in this embodiment may also identify the service input parameter according to the NLP technology, determine the call result according to the input parameter, for example, based on the NLP technology training, to obtain a deep learning model, where the input of the deep learning model is the service input parameter and output is the corresponding call result, so that the corresponding call result may be obtained according to the deep learning model. The second server converts the data type of the call result into 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.
Specifically, the first server responds to the communication message of the service call response returned by the second server, obtains a call result from a message body of the communication message of the service call response, and returns the call result to the RPA flow execution end.
In the embodiment of the disclosure, the 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.
Fig. 3 is a flowchart of a server communication method of an AI-based RPA flow 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 business service according to the communication message of the call service request, and a call result is obtained.
Specifically, after receiving the communication message of the first server requesting to call the service, the second server may call the corresponding service according to the service identifier in the communication message requesting to call the service, and input the service input parameter in the communication message requesting to call the service to the service, so as to obtain a call result.
As an example, the second server may identify the service identifier in the communication message according to the NLP technology, call the service to generate the table, and may input the table parameter (e.g., the table size) in the communication message requesting to call the service to generate the table.
S303, the second server sends a communication message of the service call response to the first server so as to return a call 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, in this embodiment, the message content in the communication message can be identified according to the NLP technology, further, a response instruction is generated according to the message content, and the corresponding message content is responded according to the response instruction. The second server returns a communication message of the service invocation response to the first server.
In the embodiment of the disclosure, the 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.
Fig. 4 is a flowchart of a server communication method of an AI-based RPA flow control end according to another embodiment of the disclosure. As shown in fig. 4, the method includes:
s401, the first server receives a service call request of the RPA flow execution end.
Specifically, step S301 may refer to the detailed description of step S201, and will not be described in detail.
S402, 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.
Specifically, the first server may obtain, from the service call request of the RPA flow executing end, a service identifier of the service requested to be called by the RPA flow executing end, and determine a second server where the service corresponding to the service identifier is located. If there is no communication connection 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.
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 communication connection, the check bit can be checked through a preset check algorithm, so that the check of the communication message which requests to establish communication connection is realized, whether the communication message which requests to establish communication connection is correct or not is determined, and the accuracy of communication between the first server and the second server is improved.
In one possible implementation, the checking algorithm may employ a cyclic redundancy check (Cyclic Redundancy Check, abbreviated CRC) checking algorithm to improve the accuracy of the communication message check.
S404, if the verification is passed, the second server establishes communication connection with the first server.
Specifically, if the verification is passed, the second server establishes a communication connection with the first server, otherwise, the second server may send a communication message that the communication connection establishment fails to the first server.
S405, the second server sends a communication message of the connection response to the first server.
Specifically, after the second server establishes a 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 can timely learn that the communication connection is established successfully.
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 types of the service representation and the service input parameter in the service call request into byte types, and use the converted service identifier and the converted service input parameter as the message content of the communication message requesting to call the service. And sending a communication message requesting to call the service to the second server.
S407, the second server calls the corresponding business service according to the communication message of the call service request, and a call result is obtained.
Specifically, after receiving the communication message of the first server requesting to call the service, the second server may call the corresponding service according to the service identifier in the communication message requesting to call the service, and input the service input parameter in the communication message requesting to call the service to the service, so as to obtain a call result.
S408, the second server sends a communication message of the service call response to the first server so as to return a call 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 execution end.
Specifically, the first server responds to the communication message of the service call response returned by the second server, obtains a call result from a message body of the communication message of the service call response, and returns the call result to the RPA flow execution end.
Compared with the text type communication message, the byte type communication message has no redundant data basically, such as no line feed and no 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 one 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 the first server and the second server can conveniently read and write the message header (for example, read the service identifier from the message header and write the service identifier into the message header) by fixing the length of the message header, thereby improving the server communication efficiency of the RPA flow control end.
In a possible implementation manner, the message header includes 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 standard 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 each field, thereby effectively improving the server communication efficiency of the RPA flow control end.
Further, the fields comprise a message 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, so that the integrity of the content of the message header is ensured and the compactness of the content of the message header is improved by fixing the positions of the fields in the message header, and the first server and the second server can accurately read the content of each field, thereby effectively improving the communication performance of the server of the RPA flow control end.
The message type comprises a request message and a response message; the communication protocol version number is the version number of the communication protocol on which the first server and the second server currently communicate; the message identifier is a unique identifier 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 the message body in the communication message; the message time is the sending time or the generating time of the communication message; the message types comprise a connection request, a connection response, a service call and a service call response; the reserved bits are used for expanding the message header in the subsequent development process; the check bit is used to check the communication message.
For example, the structure of the 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 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 call response, the service identification is 0.
TABLE 1
Specifically, in a communication message sent by a first server to a second server and requesting 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 by the second server to the first 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 the communication message which is sent by the first server to the second server and requests to call the 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 call request sent by the RPA flow executing end, the message type is a service call, and the message body is obtained by converting the byte type of the service input parameter in the service call request sent by the RPA flow executing end. In the communication message of the service call response sent by the second server to the first server, the message type in the message header is a response message, the service identifier is 0, the message type is a service call response, and the message body is obtained by converting the byte type of the call result.
In a possible implementation manner, the message header and the fixed header can be added, and the added result is processed through a preset verification algorithm to obtain the data of the verification bit in the message header, so that the verification effect is improved. For example, the fixed header "49f785a939c5475594c7ffb a54f173f" 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 check bits of the 60 th to 63 th bytes of the message header shown in table 1.
In a possible implementation manner, in the process of generating a communication message requesting to call a service, the first server may convert a data type of a service identifier in a service call request sent by an RPA procedure 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 call request sent by the RPA flow executing end can be converted into a byte type, the converted service input parameter is determined as a 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, thereby reducing redundant data in the communication message, improving the analysis efficiency of the communication message, and further improving the communication efficiency of the first server and the second server.
In a possible implementation manner, in the process of generating the communication message of the service call response, the second server may generate a message header according to the result of the message header (where the service identifier is 0), convert the data type of the call result of the business service into a byte type, determine the converted call result as a message body, and determine the length of the message body 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 call response, thereby reducing redundant data in the communication message, improving the analysis efficiency of the communication message and further improving the communication efficiency of the first server and the second server. The calling result includes whether the business service is normally called, and output data (such as the work number of the queried company employee) after the business service is called.
In one 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 conversion efficiency of the byte type.
Therefore, after receiving the communication message of the first server requesting to call the service, the second server can obtain the service input parameters 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 implementation, protocol Buffers (abbreviated as ProtoBuf) may be used to sequence service input parameters or call results to improve the serialization effect. ProtoBuf is a method of extensible and serialized structure data that is not limited by language and platform.
In one embodiment, a continuous duration of data transmission between the first server and the second server is obtained, and if the continuous duration is greater than a preset duration threshold, 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, 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, multiplexing of the communication connection is realized, and the capability of the RPA flow control end for coping with high concurrency situations is improved. And when no data transmission exists between the first server and the second server for a long time, the communication connection is disconnected, and the power consumption of the RPA flow control end is reduced.
In the embodiment of the disclosure, through byte type and message header result of the improved communication message, data redundancy in the communication message 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 reused, so that communication performance of the RPA flow control end under high concurrency is improved.
Fig. 5 is a schematic structural diagram of a server communication device of an AI-based RPA flow control end according to an embodiment of the present disclosure, 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 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. As shown in fig. 5, the apparatus includes:
a receiving module 501, configured to receive, by a first server, a service call request from an RPA flow execution end;
a sending module 502, configured to send, if a communication connection exists between the first server and the second server, a communication message requesting to invoke a service to the second server by the first server; and the first server responds to the 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 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, each of which 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, a reserved bit, and a check bit.
In one possible implementation, the sending module 502 is further configured to: 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; 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 call service to the second server.
In a possible embodiment, the apparatus further comprises a connection module for: and acquiring continuous time length of data transmission between the first server and the second server, and disconnecting communication connection between the first server and the second server if the continuous time length is larger than a preset time length threshold value.
In one possible implementation, the sending module 502 is specifically configured to: if communication connection exists between the first server and the second server, the first server acquires a service identifier and a service input parameter from a service call request according to natural language processing NLP; the first server generates a message header of a communication message requesting to call the service according to the service identifier; the first server sequences 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 RPA flow control end based on AI according to another embodiment of the present disclosure, 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 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. As shown in fig. 6, the apparatus includes:
a receiving module 601, configured to receive, by a second server, a communication message sent by a first server and requesting to invoke a service;
The calling module 602 is configured to call a corresponding business service according to a communication message requesting to call the service by using the second server, so as to obtain a call result;
and the sending module 603 is configured to send, by the second server, a communication message of the service call response to the first server, so as to return a call 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, each of which 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 a 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; if the verification is passed, the second server establishes a communication connection with the first server and sends a communication message of the connection response to the first server.
In one possible embodiment, the connection module is further configured to: and acquiring continuous time length of data transmission between the first server and the second server, and disconnecting communication connection between the first server and the second server if the continuous time length is larger than a preset time length threshold value.
The server communication device at the control end of the AI-based RPA procedure provided in fig. 5 and fig. 6 may execute the above corresponding method embodiments, and the implementation principle and technical effects are similar, and are not described herein again.
Fig. 7 is a schematic structural diagram of a server according to an embodiment of the 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-executable instructions, and the processor 702 implements the method according to any of the embodiments described above when executing a computer program.
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 (network processor, NP), etc.; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The memory 703 may include random access memory (random access memory, RAM) and may also include 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 instructions stored therein, 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, including a computer program stored in a storage medium, from which at least one processor can read, the at least one processor executing the computer program can implement the method of any one of the embodiments described above.
Fig. 8 is a block diagram of a server communication device 800 of an AI-based RPA flow 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 applications, executable by processing component 801. The application program stored in the memory 802 may include one or more modules each corresponding to a set of instructions. Further, processing component 801 is configured to execute instructions to perform the methods of any of the embodiments described above.
The apparatus 800 may further comprise a power component 803 configured to perform power management of the apparatus 800, a wired or wireless network interface 804 configured to connect the apparatus 800 to a network, and an input output (I/O) interface 805. The device 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 presently disclosed embodiments, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the front and rear associated objects are an "or" relationship; in the formula, the character "/" indicates that the front and rear associated objects are a "division" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). 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 plural.
It will be understood that references to "first" and "second" in the embodiments of the present disclosure are merely descriptive convenience and are not intended to limit the scope of the embodiments of the present disclosure.
It will be appreciated that the various numerical numbers referred to in the embodiments of the present disclosure are merely descriptive convenience and are not intended to limit the scope of the embodiments of the present disclosure.
It should be understood that, in the embodiments of the present disclosure, the sequence number of each process described above does not mean that the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments 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 present disclosure are intended to cover any adaptations, uses, or adaptations of the disclosure following the general 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 is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected 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 the AI is characterized in that the RPA flow control end comprises a first server and a second server, wherein the first server is used for communicating with the RPA flow execution end and the second server, the second server is used for storing business services, and the 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 call request of the RPA flow execution end;
if 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 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 message 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, each of the fields having a fixed location within the message header.
4. The method of claim 3, wherein the fields comprise a message type, a communication protocol version number, a message identification, a service identification, a message body length, a message time, a message type, a reserved bit, and a check bit.
5. The method of any of claims 1-4, wherein if a communication connection exists between the first server and the second server, the method further comprises, before the first server sends a communication message to the second server requesting invocation of a service:
if no communication connection exists between the first server and the second server, the first server sends a communication message requesting to establish communication connection to the second server;
and if the first server and the second server have communication connection, the first server sends a communication message for requesting to call a service to the second server, wherein the communication message comprises:
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 call service request to the second server.
6. The method according to any one of claims 1-4, further comprising:
and acquiring continuous time length of the first server and the second server which do not perform data transmission, and disconnecting communication connection between the first server and the second server if the continuous time length is larger than a preset time length threshold value.
7. The method of any of claims 1-4, wherein the first server sending 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, comprising:
if communication connection exists between the first server and the second server, the first server acquires a service identifier and a service input parameter from a service call request according to natural language processing NLP;
the first server generates a message header of the communication message requesting to call the service according to the service identifier;
The first server sequences the service input parameters to generate a message body of the communication message requesting to call the service;
the first server sends the communication message requesting to call a service to the second server.
8. The server communication method for the RPA flow execution end is characterized in that the RPA flow control end comprises a first server and a second server, wherein the first server is used for communicating with the RPA flow execution end and the second server, the second server is used for storing business services, and the data type of a communication message between the first server and the second server is a byte type; the method comprises the following steps:
a second server receives a communication message which is sent by the first server and requests to call a service;
the second server calls corresponding business service according to the communication message of the service call request to obtain a call result;
the second server sends a communication message of a service call response to the first server to return the call result to the first server.
9. The method of claim 8, wherein a message header length of the 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, each of the fields having a fixed location within the message header.
11. The method of claim 10, wherein the fields comprise a message type, a communication protocol version number, a message identification, a service identification, a message body length, time information, a message type, a reserved bit, and a check bit.
12. The method according to any one of claims 8-11, wherein before the second server receives the communication message sent by the first server requesting to invoke a 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 verifies the communication message requesting to establish 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 continuous time length of the first server and the second server which do not perform data transmission, and disconnecting communication connection between the first server and the second server if the continuous time length is larger than a preset time length threshold value.
14. The method according to any one of claims 8-11, wherein the second server calls a corresponding business service according to the communication message requesting to call a service, and the call result is obtained, including:
the second server obtains the service identifier of the business service in the message header of the communication message requesting to call the service;
the second server deserializes the message body of the communication message requesting to call the service to obtain service input parameters;
and the second server calls the business service according to the service identifier of the business service and the service input parameter to obtain a call result of the business service.
15. The method according to any one of claims 8-11, wherein the second server sending a communication message of a service invocation response to the first server to return the invocation result to the first server, comprising:
the second server generates a message header of the communication message of the service call response;
the second server sequences the calling result to generate a message body of the communication message of the service calling response;
The second server sends a communication message of the service invocation response to the first server.
16. The server communication device of the RPA flow control end based on the AI is characterized in that the RPA flow control end comprises a first server and a second server, wherein the first server is used for communicating with the RPA flow execution end and the second server, the second server is used for storing business services, and the 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 the service call request of the RPA flow execution end by the first server;
a sending module, configured to send a communication message requesting to invoke a service to the second server if there is a communication connection between the first server and the second server; and the first server responds to the 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, wherein the first server is used for communicating with the 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 a 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 the communication message which is sent by the first server and is used for requesting to call the service by the second server;
the calling module is used for calling the corresponding business service according to the communication message of the service calling request by the second server to obtain a calling result;
and the sending module is used for sending a communication message of a service call response to the first server by the second server so as to return the call result to the first server.
18. A server, comprising: a transceiver, a memory, and a processor;
the transceiver is used for receiving and transmitting data;
the memory is used for storing program instructions;
the processor being 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 having a computer program stored thereon; the computer program, when executed, implements the method of any one of claims 1-7 or any one 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
CN2020106102748 2020-06-30
CN202010610274.8A CN111756851A (en) 2020-06-30 2020-06-30 Server communication method, device, equipment and medium for RPA process control end

Publications (2)

Publication Number Publication Date
CN112235411A CN112235411A (en) 2021-01-15
CN112235411B true 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)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114416049B (en) * 2021-12-23 2023-03-14 北京来也网络科技有限公司 Configuration method and device of service interface combining RPA and AI

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110099031A (en) * 2018-01-30 2019-08-06 普天信息技术有限公司 A kind of service calling method, device and micro services platform
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

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018135926A1 (en) * 2017-01-23 2018-07-26 엘지전자(주) Bluetooth communication method and apparatus
US10324457B2 (en) * 2017-05-11 2019-06-18 Global Eprocure Robotic process automation for supply chain management operations
US10482232B2 (en) * 2017-08-16 2019-11-19 Bank Of America Corporation Robotic process automation using controller execution model
US11366857B2 (en) * 2018-08-21 2022-06-21 Directly, Inc. Artificial intelligence communications agent
US11244233B2 (en) * 2018-08-29 2022-02-08 Accenture Global Solutions Limited Intelligent adaptor service in unified automation platforms for robotic process automation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110099031A (en) * 2018-01-30 2019-08-06 普天信息技术有限公司 A kind of service calling method, device and micro services platform
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

Also Published As

Publication number Publication date
CN111756851A (en) 2020-10-09
CN112235411A (en) 2021-01-15

Similar Documents

Publication Publication Date Title
US10467321B2 (en) Systems and methods for dynamic C# serialization
CN107645562B (en) Data transmission processing method, device, equipment and system
US8788787B2 (en) Systems, methods and architecture for facilitating software access to acceleration technology
US9557734B2 (en) Control network system, master apparatus, control data processing method, and control data processing program
CN113032166B (en) Inter-core communication method, processor, inter-core communication system, and computer-readable storage medium
CN114610404B (en) Component calling method and device based on application framework and computer equipment
CN110955715A (en) ERP system, data conversion method and device of target platform and electronic equipment
CN111967236A (en) Message processing method and device, computer equipment and storage medium
CN112235411B (en) Server communication method, device, equipment and medium of RPA flow control terminal based on AI
CN113642021B (en) Service code submitting method, processing method, device and electronic equipment
CN105487403A (en) Establishment of motion control system based on CAN and simulation modeling method
CN111369237A (en) Data processing method and device and computer storage medium
CN109445973A (en) Position the method and device of application crash
CN104699799A (en) Data transmission method based on cross system
CN113676521A (en) Service request response method and device and electronic equipment
WO2020259286A1 (en) Method and apparatus for obtaining device information, storage medium and electronic device
CN109034768B (en) Financial reconciliation method, apparatus, computer device and storage medium
CN116800807A (en) GPU resource remote calling method, device, equipment and storage medium
CN116226027B (en) Data transmission system, method, device, communication equipment and storage medium
CN117573730B (en) Data processing method, apparatus, device, readable storage medium, and program product
CN111124923B (en) Running state query method and device, server equipment and storage medium
CN111338820B (en) Operation method, client and storage medium
CN116132214B (en) Event transmission method, device, equipment and medium based on event bus model
CN112597502B (en) Large-scale computing service configuration method and system based on trusted cloud
CN115022403B (en) Information processing system for multi-channel service agent

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