CN116915840A - Communication method, terminal device, server, communication system and electronic device - Google Patents

Communication method, terminal device, server, communication system and electronic device Download PDF

Info

Publication number
CN116915840A
CN116915840A CN202310913409.1A CN202310913409A CN116915840A CN 116915840 A CN116915840 A CN 116915840A CN 202310913409 A CN202310913409 A CN 202310913409A CN 116915840 A CN116915840 A CN 116915840A
Authority
CN
China
Prior art keywords
client
identifier
rpa
connection
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310913409.1A
Other languages
Chinese (zh)
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.)
Shanghai Newtouch Software Co ltd
Original Assignee
Shanghai Newtouch Software 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 Shanghai Newtouch Software Co ltd filed Critical Shanghai Newtouch Software Co ltd
Priority to CN202310913409.1A priority Critical patent/CN116915840A/en
Publication of CN116915840A publication Critical patent/CN116915840A/en
Pending legal-status Critical Current

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/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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/2866—Architectures; Arrangements
    • H04L67/2869—Terminals specially adapted for communication

Abstract

The application provides a communication method, terminal equipment, a server, a communication system, electronic equipment and a computer readable storage medium, and relates to the field of communication. The communication method comprises the following steps: acquiring characteristic data of an RPA client as a client identifier; acquiring user information logged in an RPA client as a user identifier; sending a connection request to a server, and establishing communication connection with the server, wherein the connection request comprises a client identifier and a user identifier; and receiving a client connection identifier sent by the server, and communicating with the server by using the client connection identifier, wherein the client connection identifier is generated according to the client identifier and the user identifier. Compared with the prior art, the communication method, the terminal equipment, the server, the communication system, the electronic equipment and the computer readable storage medium provided by the embodiment of the application have the advantage of improving the communication efficiency between the RPA management platform and the RPA robot software.

Description

Communication method, terminal device, server, communication system and electronic device
Technical Field
The present application relates to the field of communications, and in particular, to a communication method, a terminal device, a server, a communication system, an electronic device, and a computer-readable storage medium.
Background
RPA (Robotic Process Automation ) is the automated execution of process tasks on rules by a specific "robot software" that simulates the operation of a human on a computer. The RPA robot software can intelligently understand the existing application of enterprises through a user use interface, automate the regular operation based on rules and finish the work with high repeatability but fixed business logic. If the mail reading work is automatically repeated, files and reports are generated in batches, and the work such as boring file inspection is completed.
In the prior art, when the RPA management platform is adopted to manage the RPA robot software, only the unique RPA robot software is allowed to run on a single user terminal, so that the communication efficiency between the RPA management platform and the RPA robot software is lower.
Disclosure of Invention
The application aims to provide a communication method, terminal equipment, a server, a communication system, electronic equipment and a computer readable storage medium, which can improve the communication efficiency between an RPA management platform and RPA robot software.
In a first aspect, the present application provides a communication method applied to a terminal device, where an RPA client is operated by the terminal device, the communication method includes: acquiring characteristic data of the RPA client as a client identifier; acquiring user information logged in the RPA client as a user identifier; sending a connection request to a server, and establishing communication connection with the server, wherein the connection request comprises the client identifier and the user identifier; and receiving a client connection identifier sent by the server, and communicating with the server by using the client connection identifier, wherein the client connection identifier is generated according to the client identifier and the user identifier.
Compared with the prior art, in the communication method provided by the embodiment of the application, before the RPA client performs data communication with the RPA management platform in the server, the characteristic data of the RPA client is obtained in advance as the client identifier, and the user information logged in the RPA client is used as the user identifier, then the client identifier and the user identifier are added into the connection request and sent to the server together, the server can determine the client connection identifier uniquely corresponding to the RPA client according to the client identifier and the user identifier, and when the subsequent RPA client performs data communication with the RPA management platform, the communication data can be marked by using the client connection identifier, so that the data communication between the RPA client and the RPA management platform is realized.
In an alternative embodiment, the communicating with the server using the client connection identifier includes: acquiring terminal operation data of terminal equipment where the RPA client is located; and the terminal operation data and the client connection identifier are sent to the server together.
In an alternative embodiment, the communicating with the server using the client connection identifier further includes: receiving RPA flow data sent by the server, wherein the RPA flow data comprises a feedback connection identifier and a control instruction; and executing the control instruction when the feedback connection identifier is the client connection identifier.
In an optional embodiment, the obtaining the characteristic data of the RPA client as the client identifier includes: and acquiring a system serial number of an operating system currently running the RPA client and/or a device serial number of terminal equipment currently running the RPA client as the client identifier.
In an alternative embodiment, the establishing a communication connection with the server includes: and establishing WebSocket connection with the server.
In a second aspect, the present application provides a communication method, applied to a server, the communication method including: receiving a connection request sent by an RPA client, wherein the connection request comprises a client identifier of the RPA client and a user identifier of a user logged in the RPA client; and determining a client connection identifier according to the client identifier and the user identifier, establishing communication connection with the RPA client, sending the client connection identifier to the RPA client, and using the client connection identifier to communicate with the RPA client.
Compared with the prior art, in the communication method provided by the embodiment of the application, after receiving the connection request sent by the RPA client, the server can analyze and obtain the client identifier of the RPA client and the user identifier of the user logging in the RPA client, which are included in the connection request, so that the client connection identifier uniquely corresponding to the RPA client is determined according to the client identifier and the user identifier, when the subsequent server and the RPA client perform data communication, the communication data can be marked by using the client connection identifier, thereby realizing the data communication between the server and the RPA client.
In an optional embodiment, the determining the client connection identifier according to the client identifier and the user identifier includes: judging whether a history identifier corresponding to the client identifier and the user identifier exists in the server or not; if the history identifier corresponding to the client identifier and the user identifier exists in the server, the history identifier is used as the client connection identifier; and if the history identifier corresponding to the client identifier and the user identifier does not exist in the server, generating the client connection identifier according to the client identifier and the user identifier.
In an alternative embodiment, the communicating with the RPA client using the client connection identifier includes: receiving communication data sent by the RPA client, wherein the communication data comprises the client connection identifier and terminal operation data of terminal equipment where the RPA client is located; generating a control instruction according to the terminal operation data; and sending RPA flow data to the RPA client, wherein the RPA flow data comprises the client connection identifier and the control instruction.
In an alternative embodiment, the establishing a communication connection with the RPA client includes: and establishing WebSocket connection with the RPA client.
In a third aspect, the present application provides a terminal device, including: the identification acquisition module is used for acquiring characteristic data of the RPA client as a client identification, and is also used for acquiring user information of the login RPA client as a user identification; the communication module is used for sending a connection request to a server, establishing communication connection with the server, wherein the connection request comprises the client side identifier and the user identifier, and the communication module is also used for receiving the client side connection identifier sent by the server, communicating with the server by using the client side connection identifier, and generating the client side connection identifier according to the client side identifier and the user identifier.
In a fourth aspect, the present application provides a server comprising: the communication module is used for receiving a connection request sent by an RPA client, wherein the connection request comprises a client identifier of the RPA client and a user identifier of a user logged in the RPA client; the processing module is used for determining a client connection identifier according to the client identifier and the user identifier; the communication module is also used for establishing communication connection with the RPA client, sending the client connection identifier to the RPA client, and communicating with the RPA client by using the client connection identifier.
In a fifth aspect, the present application provides a communication system, comprising a terminal device as described in the foregoing embodiments, for performing the communication method as described in any one of the foregoing embodiments, and a server as described in the foregoing embodiments, for performing the communication method as described in any one of the foregoing embodiments.
In a sixth aspect, the present application provides an electronic device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the communication method of any one of the preceding embodiments.
In a seventh aspect, the present application provides a computer-readable storage medium storing a computer program for execution by a processor to implement the communication method of any one of the preceding embodiments.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a communication method according to a first embodiment of the present application;
fig. 2 is a flow chart of a communication method according to a second embodiment of the present application;
fig. 3 is a schematic structural diagram of a terminal device according to a third embodiment of the present application;
fig. 4 is a schematic structural diagram of a server according to a fourth embodiment of the present application;
fig. 5 is a schematic structural diagram of a communication system according to a fifth embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the present application, it should be noted that, if the terms "upper", "lower", "inner", "outer", and the like indicate an azimuth or a positional relationship based on the azimuth or the positional relationship shown in the drawings, or the azimuth or the positional relationship in which the inventive product is conventionally put in use, it is merely for convenience of describing the present application and simplifying the description, and it is not indicated or implied that the apparatus or element referred to must have a specific azimuth, be configured and operated in a specific azimuth, and thus it should not be construed as limiting the present application.
Furthermore, the terms "first," "second," and the like, if any, are used merely for distinguishing between descriptions and not for indicating or implying a relative importance.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
The first embodiment of the application provides a communication method applied to communication between terminal equipment and a server, wherein an RPA client is operated on the terminal equipment, and an RPA management platform is operated on the server.
Step S101: and acquiring characteristic data of the RPA client as a client identifier.
Specifically, in this step, before communicating with the RPA management platform, the RPA client may acquire feature data of the RPA client as a client identifier of the RPA client.
In some embodiments of the present application, the feature data of the RPA client may be a system serial number of an operating system currently running the RPA client, that is, the system serial number of the operating system currently running the RPA client is obtained as a client identifier corresponding to the current RPA client.
It may be understood that the foregoing feature data of the RPA client may be a system serial number of an operating system currently running the RPA client, which is merely illustrative of the feature data of the RPA client in some embodiments of the present application, and not exclusive, and in some other embodiments of the present application, the feature data of the RPA client may also be a device serial number of a terminal device currently running the RPA client, that is, a device serial number of a terminal device currently running the RPA client may be obtained as a client identifier corresponding to the current RPA client, which may be specifically and flexibly used according to actual needs.
Step S102: and acquiring user information logged in the RPA client as a user identifier.
In some embodiments of the present application, after a user logs on an RPA client, the RPA client may further obtain user information logged on the RPA client as a user identifier before communicating with the RPA management platform.
In some embodiments of the present application, the user information of the logged-in RPA client may be information such as a user name, user data, user history data, etc., and specifically may be flexibly selected according to actual needs, and the information that may be used to identify the logged-in RPA client may be all used as the user identifier in the embodiments of the present application.
Step S103: and sending a connection request to the server, and establishing communication connection with the server, wherein the connection request comprises a client identifier and a user identifier.
In some embodiments of the present application, after the RPA management platform on the server is started, the agreed service port is exposed according to the preset agreement, and the terminal device sends the connection request to the server, that is, the connection request is sent to the agreed service port, so that a communication connection is established with the server.
The connection request includes the client identifier obtained in the foregoing step S101 and the user identifier obtained in the foregoing step S102. Specifically, in some embodiments of the present application, the request identifier may be obtained by packaging, storing and encrypting the client identifier and the user identifier obtained in the foregoing steps and then sending the obtained client identifier and the encrypted user identifier to the server, or may be obtained by performing agreed data conversion on the client identifier and the user identifier obtained in the foregoing steps and then sending the obtained client identifier and the encrypted user identifier to the server, where the agreed data conversion is a data conversion method, such as hash conversion, that is pre-agreed between the terminal device and the server or between the RPA client and the RPA management platform, and the method specifically may be selected according to actual data transmission requirements, so that the server or the RPA management platform may restore and obtain the client identifier and the user identifier obtained in the foregoing steps.
Further, in some embodiments of the present application, a communication connection in the form of a WebSocket connection may be established with a server. The WebSocket connection can allow the two-way communication between the terminal equipment and the server, so that the two-way communication between the RPA client and the RPA management platform is realized, namely, the RPA client can actively send information to the RPA management platform, the data generated in the RPA client can be acquired more timely, and the control effect of the RPA management platform on the RPA client is improved. In addition, because the WebSocket connection is full duplex, the server can actively send data to the user terminal at any time, and the delay is obviously reduced; meanwhile, the WebSocket connection needs to be established firstly, so that the WebSocket connection becomes a stateful protocol, and part of state information can be omitted during communication, so that the control effect of the RPA management platform on the RPA client is improved.
Further, in some embodiments of the application, the RPA application may be built based on an electronics desktop application framework.
Step S104: and receiving a client connection identifier sent by the server, and communicating with the server by using the client connection identifier, wherein the client connection identifier is generated according to the client identifier and the user identifier.
In some embodiments of the present application, after receiving a connection request sent by a user terminal, an RPA management platform in the server may generate, according to a client identifier and a user identifier included in the connection request, a client connection identifier uniquely corresponding to the client for marking the RPA client, and then send the client connection identifier to the RPA client, and when a subsequent RPA client performs data communication with the RPA management platform, the communication data may be marked by using the client connection identifier, so as to implement data communication between the RPA client and the RPA management platform.
Specifically, in some embodiments of the present application, the RPA client may collect terminal operation data of a terminal device where the RPA client is located, and send the terminal operation data and a client connection identifier to the server together, that is, label the terminal operation data by using the client connection identifier, so as to send the terminal operation data to an RPA management platform in the server, so that the RPA management platform can more timely send the terminal operation data according to a management policy of the terminal operation data, and improve management efficiency of the RPA management platform on the RPA client.
After receiving terminal operation data sent by an RPA client, an RPA management platform in a server can generate a corresponding management strategy according to the terminal operation data, wherein the management strategy can be issued to the RPA client in the form of RPA flow data, the RPA flow data comprises a feedback connection identifier and a control instruction, the control instruction is a command for controlling the RPA client, the feedback connection identifier is identification data for marking the control instruction, and the feedback connection identifier can be a client connection identifier for identifying the terminal operation data received by the RPA management platform in the server. After the RPA client receives the RPA flow data, analyzing to obtain a feedback connection identifier and a control instruction in the RPA flow data terminal, verifying the RPA flow data according to the feedback connection identifier, and if the feedback connection identifier is the same as the client connection identifier of the RPA client, sending the received RPA flow data to the RPA flow data of the RPA client by the server, wherein the control instruction can be executed at the moment.
Compared with the prior art, in the communication method provided by the embodiment of the application, before the RPA client performs data communication with the RPA management platform in the server, the characteristic data of the RPA client is obtained in advance as the client identifier, and the user information of the login RPA client is used as the user identifier, then the client identifier and the user identifier are added into the connection request and are sent to the server together, the server can determine the client connection identifier uniquely corresponding to the RPA client according to the client identifier and the user identifier, when the subsequent RPA client performs data communication with the RPA management platform, the communication data can be marked by using the client connection identifier, so that the data communication between the RPA client and the RPA management platform is realized, and as the client connection identifier corresponds to the RPA client one by one, the marking corresponds to the unique RPA client when the client is used for performing data communication with the server, even if a plurality of RPA clients are operated on the same terminal equipment, the data communication between each RPA client and the server can not affect each other, the communication efficiency between the RPA client and the RPA management platform is further realized, and the RPA client can be further improved.
The second embodiment of the present application provides a communication method applied to a server and a terminal device for communication, where the server is operated with an RPA management platform and the terminal device is operated with an RPA client, and the communication method provided by the embodiment of the present application can be applied to data communication between the RPA management platform operated on the server and the RPA client operated on the terminal device, as shown in fig. 2, where the communication method includes:
step S201: and receiving a connection request sent by the RPA client, wherein the connection request comprises a client identifier of the RPA client and a user identifier of a user logged in the RPA client.
In some embodiments of the present application, after the RPA management platform in the server is started, i.e., exposing the agreed service port according to the agreement, the RPA client sends the connection request to the agreed service port, and the server uses the service port to receive the connection request sent by the RPA client. The connection request includes a client identifier of the RPA client and a user identifier of a user logged in to the RPA client, and the specific methods for obtaining the client identifier and the user identifier may refer to the specific description in step S101 in the first embodiment, which is not described herein.
Step S202: and determining a client connection identifier according to the client identifier and the user identifier, establishing communication connection with the RPA client, sending the client connection identifier to the RPA client, and communicating with the RPA client by using the client connection identifier.
In some embodiments of the present application, the RPA management platform in the server may determine, according to the client identifier and the user identifier included in the received connection request, a client connection identifier uniquely corresponding to the RPA client that sent the connection request. For example, a unique client ID may be generated as a client connection identifier uniquely corresponding to the RPA client, or the client connection identifier uniquely corresponding to the RPA client may be generated by performing data transformation on the client identifier and the user identifier, and may be specifically used according to actual needs. The unique correspondence between the client connection identifier and the RPA client is that each client connection identifier corresponds to only one RPA client, and each RPA client corresponds to only one client connection identifier.
After determining the connection identifier of the client, the server can establish communication connection in the form of WebSocket connection with the RPA client sending the connection request, then send the connection identifier of the client to the RPA client according to the established communication connection, and subsequently can use the connection identifier of the client to communicate with the RPA client. Specifically, when the subsequent client sends a message to the RPA client, the client connection identifier uniquely corresponding to the RPA client may be used to label the message, and when the server receives the message sent by the RPA client, the server may use the client connection identifier to obtain the RPA client that sends the message.
Specifically, in some embodiments of the present application, the determining the client connection identifier according to the client identifier and the user identifier may be generating a new client connection identifier according to the client identifier and the user identifier, or may be acquiring an existing client connection identifier, that is, determining whether there is a history identifier corresponding to the received client identifier and user identifier in the server; if the history identifier corresponding to the client identifier and the user identifier exists in the server, the RPA client is indicated to have data communication with the server before, and the history identifier is directly sent to the RPA client as the client connection identifier.
In addition, in the process of communicating with the RPA client by using the client connection identifier, the RPA management platform in the server can receive communication data sent by the RPA client, wherein the communication data comprises the client connection identifier and terminal operation data of terminal equipment where the RPA client is located, after the communication data is received, the RPA management platform in the server can generate a corresponding control instruction according to the received terminal operation data, then the control instruction is marked by using the client connection identifier in the received communication data, RPA flow data is formed, and then the RPA flow data is sent to the corresponding RPA client. It can be understood that the client connection identifier marked with the control instruction in the RPA flow data is the feedback connection identifier in the foregoing embodiment at the user terminal side.
In some embodiments of the present application, the RPA management platform may generate a corresponding control instruction according to the received terminal operation data based on the springboot frame.
Compared with the prior art, in the communication method provided by the second embodiment of the application, after receiving the connection request sent by the RPA client, the server can analyze and obtain the client identifier of the RPA client included in the connection request and the user identifier of the user logged in the RPA client, further determine the client connection identifier uniquely corresponding to the RPA client according to the client identifier and the user identifier, and when the subsequent server and the RPA client perform data communication, the client connection identifier can be used for marking communication data, thereby realizing data communication between the server and the RPA client.
The third embodiment of the present application relates to a terminal device, as shown in fig. 3, including: the identification acquisition module 301, the identification acquisition module 301 is configured to acquire feature data of the RPA client as a client identification, and the identification acquisition module 301 is further configured to acquire user information of a user logged in the RPA client as a user identification; the communication module 302 is configured to send a connection request to the server, establish a communication connection with the server, where the connection request includes a client identifier and a user identifier, and receive the client connection identifier sent by the server, and use the client connection identifier to communicate with the server, where the client connection identifier is generated according to the client identifier and the user identifier.
Compared with the prior art, in the terminal device provided by the third embodiment of the present application, before the RPA client running in the terminal device performs data communication with the RPA management platform in the server, the identifier acquisition module 301 acquires the characteristic data of the RPA client in advance as the client identifier and the user information of the user logged in to the RPA client as the user identifier, and then the communication module 302 adds the client identifier and the user identifier into the connection request and sends the connection request to the server, so that the server can determine the client connection identifier uniquely corresponding to the RPA client according to the client identifier and the user identifier, and the subsequent RPA client and the RPA management platform can use the client connection identifier to mark the communication data when performing data communication via the communication module 302, thereby realizing data communication between the RPA client and the RPA management platform.
A fourth embodiment of the present application relates to a server, as shown in fig. 4, including: the communication module 401 is configured to receive a connection request sent by an RPA client, where the connection request includes a client identifier of the RPA client and a user identifier of a user logged into the RPA client; the processing module 402 is configured to determine a client connection identifier according to the client identifier and the user identifier; the communication module 401 is further configured to establish a communication connection with the RPA client, send a client connection identifier to the RPA client, and communicate with the RPA client using the client connection identifier.
Compared with the prior art, in the server provided by the embodiment of the application, after the communication module 401 receives the connection request sent by the RPA client, the processing module 402 can analyze and obtain the client identifier of the RPA client included in the connection request and the user identifier of the user logged in to the RPA client, further determine the client connection identifier uniquely corresponding to the RPA client according to the client identifier and the user identifier, and when the subsequent communication module 401 performs data communication with the RPA client, the client connection identifier can be used for marking communication data, thereby realizing data communication between the server and the RPA client.
A fifth embodiment of the present application relates to a communication system, as shown in fig. 5, including: the terminal device 501 as provided in the foregoing embodiment and the server 502 as provided in the foregoing embodiment, the terminal device 501 being configured to perform the communication method as provided in the foregoing embodiment one, and the server 502 being configured to perform the communication method as provided in the foregoing embodiment two.
A sixth embodiment of the present application relates to an electronic device, as shown in fig. 6, including: at least one processor 601; and a memory 602 communicatively coupled to the at least one processor 601; the memory 602 stores instructions executable by the at least one processor 601, and the instructions are executed by the at least one processor 601, so that the at least one processor 601 can perform the communication method in the above embodiments.
It can be understood that, when the electronic device provided in the embodiment of the present application performs the communication method provided in the first embodiment, the electronic device is a user terminal, and when the electronic device provided in the embodiment of the present application performs the communication method provided in the second embodiment, the electronic device is a server.
Where the memory and the processor are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the buses connecting the various circuits of the one or more processors and the memory together. The bus may also connect various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or may be a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor is transmitted over the wireless medium via the antenna, which further receives the data and transmits the data to the processor.
The processor is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory may be used to store data used by the processor in performing operations.
The seventh embodiment of the application relates to a computer-readable storage medium storing a computer program. The computer program implements the above-described method embodiments when executed by a processor.
That is, it will be understood by those skilled in the art that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, where the program includes several instructions for causing a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps in the methods of the embodiments of the application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only memory (ROM), a random access memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The present application is not limited to the above embodiments, and any changes or substitutions that can be easily understood by those skilled in the art within the technical scope of the present application are intended to be included in the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims (14)

1. A communication method, applied to a terminal device, where the terminal device operates with an RPA client, the communication method comprising:
acquiring characteristic data of the RPA client as a client identifier;
acquiring user information logged in the RPA client as a user identifier;
sending a connection request to a server, and establishing communication connection with the server, wherein the connection request comprises the client identifier and the user identifier;
and receiving a client connection identifier sent by the server, and communicating with the server by using the client connection identifier, wherein the client connection identifier is generated according to the client identifier and the user identifier.
2. The method of communicating according to claim 1, wherein said communicating with said server using said client connection identification comprises:
acquiring terminal operation data of terminal equipment where the RPA client is located;
and the terminal operation data and the client connection identifier are sent to the server together.
3. The method of communicating of claim 2, wherein the communicating with the server using the client connection identification further comprises:
receiving RPA flow data sent by the server, wherein the RPA flow data comprises a feedback connection identifier and a control instruction;
and executing the control instruction when the feedback connection identifier is the client connection identifier.
4. A communication method according to any one of claims 1 to 3, wherein said obtaining characteristic data of the RPA client as a client identification comprises:
and acquiring a system serial number of an operating system currently running the RPA client and/or a device serial number of terminal equipment currently running the RPA client as the client identifier.
5. The communication method according to claim 1, wherein the establishing a communication connection with the server comprises:
and establishing WebSocket connection with the server.
6. A communication method, applied to a server, the communication method comprising:
receiving a connection request sent by an RPA client, wherein the connection request comprises a client identifier of the RPA client and a user identifier of a user logged in the RPA client;
and determining a client connection identifier according to the client identifier and the user identifier, establishing communication connection with the RPA client, sending the client connection identifier to the RPA client, and using the client connection identifier to communicate with the RPA client.
7. The communication method according to claim 6, wherein said determining a client connection identity from said client identity and said user identity comprises:
judging whether a history identifier corresponding to the client identifier and the user identifier exists in the server or not;
if the history identifier corresponding to the client identifier and the user identifier exists in the server, the history identifier is used as the client connection identifier;
and if the history identifier corresponding to the client identifier and the user identifier does not exist in the server, generating the client connection identifier according to the client identifier and the user identifier.
8. The method of communicating according to claim 6, wherein said communicating with said RPA client using said client connection identification comprises:
receiving communication data sent by the RPA client, wherein the communication data comprises the client connection identifier and terminal operation data of terminal equipment where the RPA client is located;
generating a control instruction according to the terminal operation data;
and sending RPA flow data to the RPA client, wherein the RPA flow data comprises the client connection identifier and the control instruction.
9. The communication method according to any one of claims 6 to 8, wherein the establishing a communication connection with the RPA client comprises:
and establishing WebSocket connection with the RPA client.
10. A terminal device, comprising:
the identification acquisition module is used for acquiring characteristic data of the RPA client as a client identification, and is also used for acquiring user information of the login RPA client as a user identification;
the communication module is used for sending a connection request to a server, establishing communication connection with the server, wherein the connection request comprises the client side identifier and the user identifier, and the communication module is also used for receiving the client side connection identifier sent by the server, communicating with the server by using the client side connection identifier, and generating the client side connection identifier according to the client side identifier and the user identifier.
11. A server, comprising:
the communication module is used for receiving a connection request sent by an RPA client, wherein the connection request comprises a client identifier of the RPA client and a user identifier of a user logged in the RPA client;
the processing module is used for determining a client connection identifier according to the client identifier and the user identifier;
the communication module is also used for establishing communication connection with the RPA client, sending the client connection identifier to the RPA client, and communicating with the RPA client by using the client connection identifier.
12. A communication system comprising a terminal device according to claim 10 for performing the communication method according to any one of claims 1 to 5 and a server according to claim 11 for performing the communication method according to any one of claims 6 to 9.
13. An electronic device, comprising:
at least one processor; and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the communication method of any one of claims 1 to 9.
14. A computer readable storage medium storing a computer program, wherein the computer program is executed by a processor to implement the communication method of any one of claims 1 to 9.
CN202310913409.1A 2023-07-24 2023-07-24 Communication method, terminal device, server, communication system and electronic device Pending CN116915840A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310913409.1A CN116915840A (en) 2023-07-24 2023-07-24 Communication method, terminal device, server, communication system and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310913409.1A CN116915840A (en) 2023-07-24 2023-07-24 Communication method, terminal device, server, communication system and electronic device

Publications (1)

Publication Number Publication Date
CN116915840A true CN116915840A (en) 2023-10-20

Family

ID=88357916

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310913409.1A Pending CN116915840A (en) 2023-07-24 2023-07-24 Communication method, terminal device, server, communication system and electronic device

Country Status (1)

Country Link
CN (1) CN116915840A (en)

Similar Documents

Publication Publication Date Title
CN104254844B (en) The network printer is exposed to WI FI clients
CN103516690B (en) A kind of business processing status information query method and device
CN111193602B (en) Automatic operation and maintenance management system and method
CN110808948B (en) Remote procedure calling method, device and system
CN110290185B (en) Internet of things equipment integration system based on Agent and application method thereof
US20200351352A1 (en) Semantic Ontology-Based Internet Scale Communication Method of Machine Tools for Providing Remote Operational Services
CN113419920B (en) Real-time monitoring method for joint debugging test process of simulation test system of Internet of things management platform
CN107295003B (en) Data transmission method, device and system
EP2790100A1 (en) Version construction system and method
CN110912805A (en) Message reading state synchronization method, terminal, server and system
CN108540516B (en) Running state information acquisition method, control terminal, network equipment and system
CN104468248A (en) Service performance monitoring method, reverse proxy server, statistical analysis server and system
CN103997509A (en) Service oriented architecture-based service processing method and apparatus
CN116915840A (en) Communication method, terminal device, server, communication system and electronic device
CN111240904A (en) Database backup method and device, electronic equipment and storage medium
KR20160004030A (en) Test apparatus of mobile device, system and controlling method
WO2013121572A1 (en) Method of providing different-type system data in distributed system
CN103701799A (en) Parameter acquiring method, server and terminal
CN114461337A (en) Cloud simulation system and method, electronic equipment and storage medium
CN112766486A (en) Searching method of neural network structure, terminal, server and readable storage medium
CN106445694A (en) Application access method, device and system
CN110597192A (en) Workflow execution method, system and storage medium
CN111478945B (en) Pumped storage operation and inspection data processing system and method
CN114070824B (en) Registration method of Internet of things equipment, registration cloud server and medium
US20040088395A1 (en) Method for probing a server

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