Method and system for remotely calling security authentication USB key through RPA

Abstract

The invention provides a method and a system for remotely calling a security certification USB key through RPA. The method comprises the following steps: starting an RPA robot to execute an automatic task; when it is detected that the RPA robot needs security authentication of the USB key to execute the automatic task, a current USB key obtaining request is sent to the client; establishing a virtualization connection with the client, and obtaining a target USB key resource corresponding to the current USB key obtaining request from the client; on the basis of the target USB key resource, the automatic task is continuously executed through the RPA robot; and after the RPA robot uses the target USB key resource, releasing the target USB key resource, and notifying the client that the target USB key resource is used. According to the method, the RPA remote calling of the security authentication USB key is efficiently and conveniently realized, and the flexibility and the security are relatively high.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and system for remotely calling a secure authentication U-shield by RPA. Background Art

[0002] As a tool for identity authentication, USB Key has been widely used in banking, government, enterprise and other fields. It can store and encrypt user's certificates, passwords, digital signatures and other security information, improving information security. In terms of security authentication, USB Key can be used for identity authentication to ensure that only authorized users can access and operate related systems or networks.

[0003] RPA (Robotic Process Automation) is a technology that uses software robots or artificial intelligence assistants to simulate and execute repetitive, rule-defined, and large-scale business process operations performed by humans in a digital environment.

[0004] Using RPA technology to call U-shield for security authentication is a very important part in many scenarios. For example, when a user logs into an enterprise information system, they use the security authentication U-shield to ensure the identity of the current user. For another example, when a user logs into a bank website, they use the bank U-shield to ensure that the current user has the authority to obtain bank account information.

[0005] In order to improve management efficiency, many companies will centralize RPA to a designated server during RPA construction, and users will issue task instructions on the client, or the system's built-in scheduled tasks will automatically issue task instructions; after receiving the instructions, the RPA in the server will automatically execute the task. However, due to the special nature of the USB shield, it needs to be manually inserted into a computer or device for use, which is very inconvenient for users because the server is often in a computer room.

[0006] In order to solve this problem, there are currently integrated hardware and software devices and systems on the market that use remote virtualization technology to achieve remote calls to bank U shields. The bank's U shields are centrally stored on a closed device, and permissions are managed through the server's management software. The client is installed on the user's personal computer to achieve remote calls. Although this method improves the security management of physical U shields, it still has the following shortcomings:

[0007] First, they need to store the U shield in a fixed device, which limits its flexibility and portability to a certain extent. For example, a U shield used for security authentication to log in to an enterprise information system is used in different locations of multiple terminals. If the U shield is stored in a closed device, the problem of automatic RPA call is solved, but some scenarios that cannot be virtualized remotely need to be taken out of the closed device on site and put back into the closed device after use, which limits its flexibility and portability.

[0008] Second, some companies are not comfortable with storing the U-Shield in a closed device for a long time, and hope to have a safer way to ensure the use of the U-Shield. Summary of the invention

[0009] The first object of the present invention is to provide a method for using a more flexible RPA remote call security authentication U shield.

[0010] The second object of the present invention is to provide a system for remotely calling a secure authentication U-shield that implements the above-mentioned RPA remote calling secure authentication U-shield method.

[0011] In order to achieve the above-mentioned first purpose, the present invention provides a method for RPA remote calling security authentication U shield, which is applied to the remote U shield calling end, and includes the following steps: starting the RPA robot to perform automated tasks; when it is detected that the RPA robot needs U shield for security authentication to perform automated tasks, sending the current U shield acquisition request to the client; establishing a virtualized connection with the client, and obtaining the target U shield resource corresponding to the current U shield acquisition request from the client; based on the target U shield resource, continuing to execute the automated task through the RPA robot; after the RPA robot has used up the target U shield resource, releasing the target U shield resource, and notifying the client that the target U shield resource has been used.

[0012] As can be seen from the above scheme, the method of remotely calling the secure authentication U-shield by RPA of the present invention realizes remote calling of the U-shield of the computer connected to the client by virtualizing the connection between the remote U-shield calling end and the client. Compared with the previous technology, the present invention has higher flexibility, security and efficiency, and provides a more convenient use experience. The present invention is conducive to promoting the application and development of RPA technology in more fields, and will also bring more convenience and value to the use of U-shield. Compared with the previous technology that requires the U-shield to be stored in a fixed device, the present invention sends a request to the user through the RPA automation program, and the user can directly insert the U-shield in the U-shield assistant of his personal computer, thereby solving the problem of remote calling of the U-shield, while maintaining the flexibility of use and the portability of the U-shield. The present invention realizes remote calling of the U-shield by establishing a connection between the client and the server where the RPA is located, avoiding the inconvenience of manual use of the same U-shield and improving the security of the use of the U-shield. The present invention enables users to meet the calling needs of the U-shield anytime and anywhere, thereby improving the efficiency and security of enterprise operations. The present invention realizes remote calling of the U-shield, reduces the steps for users to get the U-shield from the storage of the U-shield, and thus provides a more convenient use experience.

[0013] A further solution is to establish a virtualized connection with the client, and when the client obtains the confirmation information corresponding to the target U shield resource, obtain the target U shield resource corresponding to the current U shield acquisition request from the client.

[0014] It can be seen from this that it can be set that the U-shield inserted by the user is allowed to be called by the remote U-shield only after the user clicks confirm in the client, which has higher flexibility.

[0015] A further solution is that the remote U-Shield calling end includes a first server and a second server; when the first server detects that the RPA robot needs U-Shield for security authentication to perform an automated task, it sends the current U-Shield calling request to the second server; after the second server receives the current U-Shield calling request, it verifies the legitimacy of the current U-Shield calling request, and sends the target security token to the first server after the legitimacy verification is passed, and sends the current U-Shield acquisition request to the client; the second server establishes a virtualized connection with the client and obtains the target U-Shield resource from the client; the first server calls the target U-Shield resource from the second server through the target security token, and controls the RPA robot to continue to perform the automated task in combination with the target U-Shield resource.

[0016] It can be seen that by verifying the legitimacy of the current U-Shield call request, it can be ensured that only the RPA robot that has passed the legitimacy verification can remotely call the required U-Shield through the second server, ensuring the security of calling the U-Shield.

[0017] A further solution is that after the second server sends the target security token to the first server, before sending a U-shield acquisition request to the client, it also includes: checking to determine whether the usage status of the target U-shield resource is currently available.

[0018] A further solution is that the U-Shield call request includes task information and U-Shield identification, the task information includes task identification, task type, task priority, initiator information, initiator access credentials, and the U-Shield identification includes the U-Shield serial number and U-Shield user information.

[0019] A further solution is that when the second server verifies the legitimacy of the U-Shield call request, it includes: verifying the initiator information and the initiator access credentials; when the second server checks to determine that the usage status of the target U-Shield resource is currently available, it includes: checking whether the target U-Shield resource is available according to the U-Shield serial number, if so, allocating the target U-Shield resource, if not, determining the position of the task identifier in the waiting queue according to the task type and task priority.

[0020] This shows that the U-Shield call can be guaranteed to be efficient and convenient.

[0021] A further solution is that when the second client establishes a virtualized connection with the client, it includes: establishing a connection through an SSL encrypted channel.

[0022] This shows that the security of the U-Shield calling process can be guaranteed.

[0023] A further solution is that when the first server calls the target U shield resource from the second server through the target security token, it includes: the second server virtualizes the target U shield resource and maps it to the first server through the network.

[0024] It can be seen from this that the RPA robot on the first server needs to use the target security token to call the U-Shield resource corresponding to the target security token, further ensuring the security of calling the U-Shield.

[0025] In order to achieve the above-mentioned second purpose, the present invention provides a system for RPA remote calling security authentication U-shield, which includes: a remote U-shield calling end and a client; the remote U-shield calling end is used to: start the RPA robot to perform automated tasks; when it is detected that the RPA robot needs U-shield for security authentication to perform automated tasks, send a U-shield acquisition request to the client; establish a virtualized connection with the client, and obtain the U-shield resource corresponding to the U-shield acquisition request from the client; based on the U-shield resource, continue to execute the automated task through the RPA robot; after the RPA robot uses the U-shield resource, release the U-shield resource and notify the client that the U-shield resource is used; the client is used to: after obtaining the U-shield acquisition request from the remote U-shield calling end, detect whether the U-shield corresponding to the U-shield resource is connected, and after the U-shield corresponding to the U-shield resource is connected, send the U-shield resource to the remote U-shield calling end.

[0026] As can be seen from the above scheme, the present invention cooperates with the client through the remote U shield calling end, and the client communicates with the connected U shield. The remote U shield calling end realizes the remote, efficient and safe calling of the U shield through the client to support the RPA robot to efficiently complete the automation task. The present invention solves the geographical restrictions and operational inconveniences in the use of traditional U shields, while ensuring the security and reliability of the calling process.

[0027] A further solution is that the remote U-Shield calling end includes a first server and a second server; the first server is used to: when it is detected that the RPA robot needs U-Shield for security authentication to perform an automated task, send a U-Shield calling request to the second server; call the target U-Shield resource from the second server through the target security token, and control the RPA robot to continue to perform the automated task in combination with the target U-Shield resource; the second server is used to: after receiving the U-Shield calling request, verify the legitimacy of the U-Shield calling request, and send the target security token to the first server after the legitimacy verification is passed, and send a U-Shield acquisition request to the client; the client establishes a virtualized connection and obtains the target U-Shield resource from the client.

[0028] It can be seen that the first server, as the execution center of the RPA task, is responsible for the automated execution of the task and the generation of the U-shield call request. The second server, as the management center of the U-shield resource, is responsible for the forwarding of requests, authority verification, task scheduling and provision of virtualization services. The client is equipped with a U-shield assistant module and a U-shield information acquisition module to realize the communication and virtualization establishment of the physically accessed U-shield. The multi-level and distributed system architecture constructed by the present invention makes the RPA remote call to the security authentication U-shield more flexible and secure, and improves the call efficiency and maintainability. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 It is a system block diagram of an embodiment of the RPA remote call security authentication system of the present invention.

[0030] Figure 2 It is a flowchart of an embodiment of the RPA remote call security authentication method of the present invention.

[0031] The present invention is further described below in conjunction with the accompanying drawings and embodiments. DETAILED DESCRIPTION

[0032] The method of remotely calling a securely authenticated U-shield by RPA of the present invention realizes remote and secure calling of the U-shield, and solves the problem of inconvenient operation of the traditional U-shield. Specifically, the RPA robot is started to perform an automated task through the remote U-shield calling end. When it is detected that the RPA robot needs the U-shield for security authentication to perform an automated task, a U-shield acquisition request is sent to the client. The client prompts the user to access the corresponding physical U-shield. After the client reads the physical U-shield accessed by the user, it establishes a virtualized connection with the remote U-shield calling end, and sends the target U-shield resource to the remote U-shield calling end. The RPA robot of the remote U-shield calling end continues to perform automated tasks based on the target U-shield resource, and after using the target U-shield resource, releases the target U-shield resource, and notifies the client that the target U-shield resource has been used. The RPA remote call security authentication system of the present invention implements the above method.

[0033] RPA remote call security authentication system implementation example:

[0034] See also Figure 1 , this embodiment includes a first server 1, a second server 2 and a client 3. The second server 2 is connected to the first server 1 and the client 3 respectively, and realizes data transmission with the first server 1 and the client 3 respectively.

[0035] The first server 1 includes an RPA centralized operation center module 11 and a virtualization software client 12 , and the RPA centralized operation center module 11 is connected to the virtualization software client 12 .

[0036] The RPA centralized operation center module 11 is used to execute automated tasks and apply for U-shield call through the set RPA robot. The virtualization software client 12 is used to generate U-shield call request.

[0037] The RPA centralized operation center module 11 includes a task execution unit 111 and a U-shield calling management unit 112 , and the task execution unit 111 is connected to the U-shield calling management unit 112 .

[0038] The task execution unit 111 is used to extract the automation task from the task queue of the automation task, and start the corresponding RPA robot to execute the automation task. Some RPA robots need to call the U shield for security authentication during the execution of the automation task. The U shield call management unit 112 is used to detect the request that the RPA robot needs to call the U shield for security authentication, and after detecting the request that the RPA robot needs to call the U shield for security authentication, request the virtualization software client 12 to create a corresponding U shield call request, which is used to request the detected U shield resources required by the RPA robot.

[0039] The virtualization software client 12 includes a request generation unit 121. The request generation unit 121 is used to create a corresponding U shield call request according to the request of the U shield call management unit 112.

[0040] The U-Shield call request includes task information and U-Shield information. Task information includes task identification, task type, task priority, initiator information and initiator access credentials. The U-Shield identification includes the U-Shield serial number and U-Shield user information.

[0041] Task ID is used to assign a unique identifier to each call task for tracking and managing the call task. Task type is used to specify the nature of the call task, such as downloading bank receipts and bank statements. Task priority is used to assign priorities to call tasks, such as high, medium, and low, to determine the order in which the call tasks are executed. Initiator information is used to record the identity information of the task initiator of the call task to ensure the traceability of the task. Initiator access credentials are used to provide access credentials, such as a user name and corresponding password, or a digital certificate.

[0042] The U-Shield serial number is the hardware serial number of the U-Shield, which is used to uniquely identify each U-Shield device. The U-Shield user information is used for the user information associated with the U-Shield, such as the user name or user ID.

[0043] The second server 2 includes a U-shield management center module 21 and a virtualization software server 22. The U-shield management center module 21 is used to forward requests, verify permissions, schedule tasks and send notifications. Specifically, the U-shield management center module 21 verifies the initiator information of the task initiator of the call task, that is, the RPA robot corresponding to the U-shield call request, to determine whether the RPA robot is allowed to call the U-shield, and forms a corresponding call task based on the received U-shield call request that has passed the legality verification, and provides the corresponding U-shield resources to the corresponding RPA robot by executing the call task. The virtualization software server 22 is used to provide virtualization services for U-shield resources.

[0044] The U-Shield management center module 21 includes a request forwarding unit 211 , a permission verification unit 212 , a task scheduler 213 and a notification coordinator 214 .

[0045] The request forwarding unit 211 is used to forward the U shield calling request received from the first server 1 to the authority verification unit 212.

[0046] The authority verification unit 212 is used to verify the legitimacy of the received U-shield call request to ensure that the task initiator who calls the task has the right to call the corresponding U-shield resource. The legitimacy verification includes verifying the initiator information and the initiator access credentials. The initiator information and initiator access credentials of the task initiator are entered when starting the RPA robot or set in the parameters of the RPA robot.

[0047] Specifically, first, the authority verification unit 212 verifies the initiator access credentials of the U shield call request, for example, checks the username and password provided by the initiator access credentials of the U shield call request, or the digital information provided by the initiator access credentials of the U shield call request. Then, after the initiator access credentials are verified, the authority verification unit 212 will check the initiator information of the task initiator to determine whether it has the right to call the U shield resource, specifically by querying the access control list (ACL) or the role-based access control (RBAC) policy. Then, after the initiator information is verified, the task type and required U shield resource of the U shield call request are evaluated to ensure that the U shield call request is reasonable and necessary. Finally, if it is determined that the U shield call request is reasonable and necessary, it means that the task initiator, that is, the RPA robot corresponding to the U shield call request, has passed the identity authentication and has the appropriate authority, then the second server 2 generates a security token and sends it to the first server 1. The security token is used to grant the task initiator, that is, the corresponding RPA robot, the authority to call a specific U shield resource to the second server 2.

[0048] The functions of the task scheduler 213 include (1) real-time monitoring of the status of all U-shield resources, including whether the physical U-shield is connected (whether it is connected is determined by whether it can be obtained by the U-shield information acquisition module 31), whether it is currently in use, and the type of task in use. (2) According to the preset resource allocation strategy, evaluate and determine which calling tasks can use the U-shield resources first. The evaluation factors may include: the urgency of the calling task, the task type or the task authority. (3) Task queue management. The task scheduler 213 maintains one or more task queues, each of which stores a number of calling tasks, and sorts the calling tasks waiting for U-shield resources according to priority and other scheduling parameters. (4) When a new calling task requests a U-shield resource, the task scheduler 213 checks the status of the U-shield resource. If the resource is available, it is directly allocated; if the resource is not available, the calling task is placed in the waiting queue. (5) The task scheduler 213 makes scheduling decisions based on the current execution of the calling task and the resource status. If there is a conflict between the U-shield resources required by different calling tasks, the scheduler needs to preempt resources or adjust the task priority according to the strategy. (6) Once the U-shield resource is allocated to a specific calling task, the task scheduler 213 cooperates with the virtualization software server 22 to prepare the virtualization environment to ensure that the U-shield resource can be virtualized and safely delivered to the corresponding task initiator. (7) After the calling task obtains the U-shield resource, it starts to execute. The task scheduler 213 continues to monitor the task execution status and the U-shield resource usage to ensure that the calling task proceeds as planned and releases the resource in time after the calling task is completed. (8) After the calling task is completed, the task scheduler 213 ensures that the U-shield resource of the calling task is released, updates the resource status information, and feedbacks the U-shield resource usage results to the relevant tasks or users.

[0049] The notification coordinator 214 sends a U-shield acquisition request to the client 3. When the U-shield resource is allocated to a specific call task and the call task is executed, the notification coordinator 214 sends a U-shield acquisition request to the client 3 to request the U-shield resource corresponding to the call task from the client.

[0050] The client 3 includes a U shield information acquisition module 31 and a U shield assistant module 32, and the U shield information acquisition module 31 is connected to the U shield assistant module 32. The U shield information acquisition module 31 is used to communicate data with the physically connected U shield. The U shield assistant module 32 is used for request reception, user interaction, U shield access coordination and virtualization establishment.

[0051] The U shield information acquisition module 31 includes a U shield communication unit 311, and the U shield communication unit 311 is used to communicate with the connected physical U shield. The physical U shield is connected through USB.

[0052] In other embodiments, the physical U-Shield can be accessed through a U-Shield box. The U-Shield box is a separate hardware device used to place the U-Shield and realize closed storage, permission control and other functions. When the RPA robot runs for a long time, the U-Shield is stored in the U-Shield box to facilitate the safe use of the U-Shield.

[0053] The U-shield assistant module 32 includes a request receiver 321 , a user interaction unit 322 , a U-shield access coordinator 323 and a virtualization builder 324 .

[0054] The request receiver 321 is used to receive a U-shield acquisition request from the second client 2. The user interaction unit 322 is used to provide a graphical interface for user interaction and obtain interactive information input by the user. For example, when the physical U-shield corresponding to the U-shield acquisition request is not connected, that is, the U-shield information acquisition module 31 does not communicate with the physical U-shield, the graphical user interface provided by the user interaction unit 322 notifies that the physical U-shield is not connected and prompts the user to access the corresponding physical U-shield; when the physical U-shield corresponding to the U-shield acquisition request is connected, that is, the U-shield information acquisition module 31 communicates with the physical U-shield, the graphical user interface provided by the user interaction unit 322 notifies the user that the corresponding physical U-shield is connected, and the user does not need to operate at this time. The U-shield access coordinator 323 is used to obtain the data of the physical U-shield from the U-shield information acquisition module 31. The virtualization builder 324 is used to communicate with the virtualization software service unit 221 of the second server end, and use an encrypted channel (such as SSL) to establish a secure virtualization connection.

[0055] In the above RPA remote call security authentication system, when the RPA robot in the first server 1 needs to use the U shield to perform an automated task, the U shield call process will be triggered. At this time, the user of the client 3 will receive the request, and after the user accesses the U shield, the client 3 communicates data with the connected U shield. With the cooperation of the second server 2 and the user terminal 3, the second server 2 virtualizes the physical U shield read by the user terminal 3 into a U shield resource, so that the RPA robot in the first server 1 can safely and effectively use the U shield resource to complete the automated task. For the specific process, see the RPA remote call security authentication method embodiment, which will not be repeated here.

[0056] RPA remote call security authentication method embodiment:

[0057] This embodiment is based on the RPA remote call security authentication system of the above embodiment. The scenario applied in this embodiment is an automated office environment of a financial institution, in which the first server 1, the second server 2 and the client 3 have been deployed and configured. The first server 1 and the second server 2 run on different servers, and the client 3 runs on a personal computer controlled by Zhang San. As a user of the client 3, Zhang San holds and keeps his own bank U shield, which is used for authentication and authorization of online banking operations.

[0058] In the initial state, in the RPA centralized operation center module 11 on the first server 1, the task execution unit 111 is monitoring and executing the predetermined automated tasks through the RPA robot, including a bank receipt automatic downloading RPA robot specially designed for automatically downloading bank receipts. When the RPA robot reaches the link where it needs to log in to the online banking, it triggers the U-shield call process, and the U-shield call management unit 112 issues a U-shield call request.

[0059] At this time, the U shield management center module 21 of the second server 2 is on standby, ready to accept the request of the first server 2 and perform subsequent forwarding, verification, scheduling and notification work. The U shield information acquisition module 31 and the U shield assistant module 32 of the client 3 are also on standby, ready to respond to the request of the second server 2.

[0060] Specifically, see Figure 2 , specifically including the following steps:

[0061] Step S1: extract a task from the task queue and start execution.

[0062] Among them, the task execution unit 111 of the first server 1 extracts the bank receipt automatic downloading task from the task queue of the automated task, and starts the bank receipt automatic downloading RPA robot to execute the bank receipt automatic downloading task.

[0063] Step S2: A request to call the USB shield for security authentication is detected.

[0064] Among them, when the bank receipt automatic download RPA robot accesses the online banking login page in the simulated browser, the online banking login will prompt the access U shield request. At this time, the U shield call management unit 112 of the first server 1 detects that the bank receipt automatic download RPA robot needs to call the U shield for security authentication, and then requests the virtualization software client 12 to create the current U shield call request. The current U shield call request corresponds to the target U shield resource required by the bank receipt automatic download RPA robot.

[0065] Step S3: Create a current U-Shield call request.

[0066] Among them, the request generation unit 121 of the virtualization software client 12 automatically downloads the U shield required by the RPA robot according to the bank receipt to create the current U shield call request.

[0067] In this embodiment, the request generation unit 121 creates a bank receipt to automatically download the current U-shield call request corresponding to the U-shield currently required by the RPA robot.

[0068] Step S4: Send the current U-Shield call request.

[0069] Among them, the first service 1 sends the current U-shield call request to the second service end 2.

[0070] Step S5: Verify the legitimacy of the current USB-shield call request.

[0071] Among them, after receiving the current U shield call request, the request forwarding unit 211 of the second server 2 forwards it to the authority verification unit 212. The authority verification unit 212 verifies the legitimacy of the current U shield call request to ensure that the bank receipt corresponding to the current U shield call request automatically downloads the authorized U shield resource. The legitimacy verification includes checking the initiator information and initiator access credentials of the current U shield call request.

[0072] Step S6: Generate a target security token and send it.

[0073] Among them, after the current U-Shield call request passes the legitimacy verification, the target security token is sent to the first server. The target security token is used in subsequent communications between the first server and the second server to prove that the bank receipt automatic downloading RPA robot of the first server has the right to call the target U-Shield resource to the second server.

[0074] Step S7: Check and determine the target U-shield resource status and prepare for virtualization processing.

[0075] Among them, when the task scheduler 213 checks that the target U-Shield resource can be arranged for allocation, it allocates the target U-Shield resource to the call task corresponding to the current U-Shield call request, and then prepares the virtualization environment to ensure that the target U-Shield resource can be virtualized and safely delivered to the bank receipt automatic download RPA robot corresponding to the current U-Shield call request.

[0076] Step S8: Send a request to obtain the current USB shield.

[0077] Among them, the notification coordinator 214 of the second server 2 sends the current U-shield acquisition request to the client 3, and the U-shield assistant module 32 of the client 3 receives the current U-shield acquisition request.

[0078] S9: Get the status and confirmation information of the physical USB shield.

[0079] At this time, if the status of the U-Shield physical object corresponding to the current U-Shield acquisition request is that it has been connected to the personal computer running client C, that is, the U-Shield communication unit 311 can communicate with the U-Shield physical object, then the user interaction unit 322 notifies the user by providing a graphical user interface, that is, Zhang San in this embodiment, and Zhang San does not need to perform other operations; if the status of the U-Shield physical object corresponding to the current U-Shield acquisition request is that it is not connected to the personal computer of client C, then the user interaction unit 322 notifies the user to access the U-Shield physical object by providing a graphical user interface, and then the user manually connects the U-Shield physical object to the personal computer running client C, so that the U-Shield communication unit 311 can establish communication with the U-Shield physical object.

[0080] In this embodiment, after confirming that the physical status of the U-Shield corresponding to the current U-Shield acquisition request has been connected to the personal computer running the client C, the user interaction unit 322 notifies the user whether to confirm to allow the second server 2 to remotely call the physical U-Shield through the client 3 by providing a graphical user interface, and only when the user interaction unit 322 receives the confirmation information entered by the user, will it continue to execute step S10, thereby ensuring that the user is fully aware of the call of his U-Shield and ensuring that the U-Shield is called safely.

[0081] S10: Establish a virtualized connection through an encrypted channel.

[0082] The virtualization builder 324 of the client 3 communicates with the virtualization software service unit 221 of the second server 2 and establishes a secure virtualization connection using an SSL encryption channel.

[0083] S11: Virtualize the target U shield resource and perform network mapping.

[0084] Among them, the virtualization software server 22 virtualizes the connected U shield physical object as the target U shield resource and maps it to the first server 1 through the network. When the virtualization software server 22 is mapped to the first server 1 through the network, it is necessary to ensure that the target security token in step S6 is obtained from the first server 1. Only when the target security token is obtained from the first server 1, the virtualization software server 22 maps the target U shield resource network to the first server 1.

[0085] S12: Use the target USB shield resources to continue executing the automation task.

[0086] Among them, the bank receipt automatic downloading RPA robot of the first server 1 uses the virtualized target U shield resource on the first server 1 to complete the online banking login and obtain the bank receipt data.

[0087] S13: Send a target USB shield resource release request.

[0088] Among them, after the bank receipt automatic download RPA task is completed, the task execution unit 111 of the first server 1 sends a resource release request to the second server 2.

[0089] S14: Release the target U shield resources.

[0090] S15: Notify the target U-shield resource that use is complete.

[0091] Among them, the task scheduler 213 and the notification coordinator 214 of the second server 2 release the target U shield resource, and the U shield assistant software of the client 3 notifies the user that the U shield has been used up and released successfully.

[0092] After receiving the notification that the target U-Shield resource has been used, client 3 can choose to disconnect the U-Shield connection by itself, or wait for client 3 to disconnect automatically.

[0093] In this embodiment, the second server 2 uses an audit log recorder to record all key operations during the entire calling process, including request time, operating user, execution task, etc., to facilitate later tracing and maintenance.

[0094] As a result, the system component returns to the standby state, waiting for the next calling task to be triggered and executed.

[0095] In summary, the present invention has higher flexibility, security and efficiency than the one-network technology, and provides a more convenient user experience, which is conducive to promoting the application and development of RPA technology in more fields, and will also bring more convenience and value to the use of U shield. Compared with the previous technology that requires the U shield to be stored in a fixed device, the present invention sends a request to the user through the RPA automation program, and the user can directly insert the U shield in the U shield assistant of his personal computer, thereby solving the problem of remote calling of the U shield, while maintaining the flexibility and mobility of use. The present invention realizes the remote calling of the U shield by establishing a connection between the client and the server where the RPA is located, avoiding the inconvenience of manual use of the same U shield and improving the security of the use of the U shield; the present invention enables users to meet the calling needs of the U shield anytime and anywhere, thereby improving the efficiency and security of enterprise operations. The present invention realizes the remote calling of the U shield, reduces the steps for users to get the U shield from the storage of the U shield, and thus provides a more convenient user experience.

[0096] Finally, it should be emphasized that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various changes and modifications. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for remotely calling a secure authentication USB shield by RPA, applied to a remote USB shield calling end, characterized in that: The following steps are involved: Start the RPA robot to perform automation tasks; When detecting that the RPA robot needs a USB shield for security authentication when executing the automation task, sending a current USB shield acquisition request to the client; Establishing a virtualized connection with the client, and obtaining a target U-shield resource corresponding to the current U-shield acquisition request from the client; Based on the target USB shield resource, continue to execute the automation task through the RPA robot; After the RPA robot has finished using the target U shield resource, the target U shield resource is released, and the client is notified that the target U shield resource has been used up.

2. The method for remotely calling a secure authentication USB shield by RPA according to claim 1, characterized in that: A virtualized connection is established with the client, and when the client obtains confirmation information corresponding to the target U shield resource, the target U shield resource corresponding to the current U shield acquisition request is obtained from the client.

3. The method for remotely calling a secure authentication USB shield by RPA according to claim 1 or 2, characterized in that: The remote U-shield calling end includes a first server and a second server; When the first server detects that the RPA robot needs a USB shield to perform security authentication when executing the automation task, the first server sends a current USB shield call request to the second server; After receiving the current U-Shield call request, the second server verifies the legitimacy of the current U-Shield call request, and sends the target security token to the first server after the legitimacy verification passes, and sends the current U-Shield acquisition request to the client; The second server establishes a virtualized connection with the client and obtains the target U shield resource from the client; The first server calls the target U shield resource from the second server through the target security token, and controls the RPA robot to continue to execute the automation task in combination with the target U shield resource.

4. The method for remotely calling a secure authentication USB shield by RPA as claimed in claim 3, characterized in that: After the second server sends the target security token to the first server, before sending the U shield acquisition request to the client, it also includes: checking to determine that the usage status of the target U shield resource is currently available.

5. The method for remotely calling a secure authentication USB shield by RPA as claimed in claim 4, characterized in that: The U-Shield call request includes task information and a U-Shield identifier. The task information includes a task identifier, a task type, a task priority, initiator information, and an initiator access credential. The U-Shield identifier includes a U-Shield serial number and a U-Shield user information.

6. The method for remotely calling a secure authentication USB shield by RPA as claimed in claim 5, characterized in that: When the second server verifies the legitimacy of the U-Shield call request, it includes: verifying the initiator information and the initiator access credential; When the second server checks and determines that the usage status of the target U-Shield resource is currently available, it includes: checking whether the target U-Shield resource is available according to the U-Shield serial number, if so, allocating the target U-Shield resource, if not, determining the position of the task identifier in the waiting queue according to the task type and the task priority.

7. The method for remotely calling a secure authentication USB shield by RPA as claimed in claim 6, characterized in that: When the second client establishes a virtualized connection with the client, it includes: establishing a connection through an SSL encrypted channel.

8. The method for remotely calling a secure authentication USB shield by RPA as claimed in claim 7, characterized in that: When the first server calls the target U shield resource from the second server through the target security token, it includes: the second server virtualizes the target U shield resource and maps it to the first server through the network.

9. A system for RPA remotely calling a secure authentication USB shield, characterized in that: include: Remote U-Shield calling end and client; The remote U-shield calling end is used to: start the RPA robot to perform automation tasks; When detecting that the RPA robot needs a USB shield for security authentication when executing the automation task, a USB shield acquisition request is sent to the client; Establish a virtualized connection with the client, and obtain the U shield resource corresponding to the U shield acquisition request from the client; based on the U shield resource, continue to execute the automation task through the RPA robot; after the RPA robot has used up the U shield resource, release the U shield resource and notify the client that the U shield resource has been used up; The client is used to: after obtaining the U-shield acquisition request from the remote U-shield calling end, detect whether the U-shield physical object corresponding to the U-shield resource is connected, and after the U-shield physical object corresponding to the U-shield resource is connected, send the U-shield resource to the remote U-shield calling end.

10. The system for remotely calling a secure authentication USB shield by RPA as claimed in claim 9, characterized in that: The remote U-shield calling end includes a first server and a second server; The first server is used to: when detecting that the RPA robot needs a USB shield for security authentication to execute the automation task, send a USB shield call request to the second server; call the target USB shield resource from the second server through the target security token, and control the RPA robot to continue to execute the automation task in combination with the target USB shield resource; The second server is used to: after receiving the U-shield call request, verify the legitimacy of the U-shield call request, and send the target security token to the first server after the legitimacy verification is passed, and send the U-shield acquisition request to the client; the client establishes a virtualized connection and obtains the target U-shield resource from the client.

Images