Robot remote operation and maintenance method and system, robot and readable storage medium
By introducing two-way authentication and session-level isolation encrypted communication into the robot remote operation and maintenance system, the security deficiencies in existing technologies are resolved, thereby improving the security and operational reliability of robot remote operation and maintenance.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- UBTECH ROBOTICS CORP LTD
- Filing Date
- 2026-01-28
- Publication Date
- 2026-04-28
AI Technical Summary
Existing remote robot operation and maintenance systems are inadequate in terms of security authentication, lacking effective security authentication during remote operation and maintenance, which makes robots vulnerable to unauthorized control.
The operation and maintenance platform verifies the robot's remote operation and maintenance requests and status, generates session identifiers and establishes two-way identity authentication, dynamically generates operation and maintenance sessions, and establishes encrypted communication channels based on session identifiers to achieve session-level isolation.
It enhances the security of remote operation and maintenance, prevents communication from being eavesdropped on, tampered with, or exploited laterally, ensures that operation and maintenance operations are performed in a controlled and encrypted environment, and reduces misoperation and command loss.
Smart Images

Figure CN121940433A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of robotics, and in particular to a method, system, robot, and readable storage medium for remote operation and maintenance of a robot. Background Technology
[0002] Existing remote robot operation and maintenance systems typically rely on network boundary-based security protection models, primarily achieving remote access and control through fixed account authentication and virtual private network configuration. In practical applications, after initial authentication, the system often assumes the operation and maintenance entity is in a trusted state, lacking security authentication during the remote operation and maintenance process, which can easily lead to unauthorized remote control of the robot. Summary of the Invention
[0003] In view of this, the purpose of this invention is to overcome the shortcomings of the prior art and provide a method, system, robot and readable storage medium for remote operation and maintenance of robots, so as to solve the problem of low security in the existing remote operation and maintenance of robots.
[0004] This invention provides the following technical solution: In a first aspect, the present invention provides a method for remote operation and maintenance of a robot, comprising: The current remote maintenance request of the robot is obtained from the maintenance terminal through the maintenance platform, and the current remote maintenance request and the current status of the robot are verified. Once the verification is successful, the operation and maintenance platform generates a session identifier corresponding to the current remote operation and maintenance request, and establishes an operation and maintenance session based on the session identifier; Based on the operation and maintenance session, two-way authentication is performed between the operation and maintenance platform and the robot. After the two-way authentication is successful, a communication channel between the operation and maintenance platform and the robot is established according to the session identifier. The robot executes the current remote maintenance request based on the communication channel.
[0005] In an optional implementation, the step of executing the current remote maintenance request via the robot based on the communication channel includes: The operation and maintenance platform generates operation and maintenance permission policies based on the current remote operation and maintenance request and preset security policies. The operation and maintenance permission policy is transmitted from the operation and maintenance platform to the robot through the communication channel; The robot executes instructions according to the operation and maintenance permission policy.
[0006] In an optional implementation, the step of executing instructions through the robot according to the operation and maintenance permission policy includes: The robot determines executable instructions based on the operation and maintenance permission policy. The executable instruction is validated for permissions based on the operation and maintenance permission policy and the current remote operation and maintenance request. After the permission verification is successful, the executable instruction will be executed.
[0007] In an optional implementation, after the robot executes the instruction according to the operation and maintenance permission policy, it includes: Record the execution log of the executable instructions and the status of operational and maintenance behaviors; Perform security audits on the operational and maintenance behavior status.
[0008] In an optional implementation, the method further includes: If abnormal operation and maintenance behavior is detected, security measures will be triggered according to the preset security policy.
[0009] In an optional implementation, the method further includes: After the current remote operation and maintenance request is completed, or after the operation and maintenance session is terminated abnormally, the operation and maintenance session is destroyed, operation and maintenance permissions are revoked, and data is erased.
[0010] In an optional implementation, the current remote maintenance request includes dynamic authentication information, context-aware information, and risk-driven decision information; the current state includes operating state, firmware state, and network environment state; and the verification of the current remote maintenance request and the robot's current state includes: Multi-factor authentication is performed on the dynamic identity verification information, the context-aware information, and the risk-driven decision information; The operating status, firmware status, and network environment status are verified using a trusted method.
[0011] Secondly, the present invention provides a remote operation and maintenance system for robots, comprising: The operation and maintenance platform is used to obtain the current remote operation and maintenance request of the robot from the operation and maintenance terminal, verify the current remote operation and maintenance request and the current status of the robot; generate a session identifier corresponding to the current remote operation and maintenance request, and establish an operation and maintenance session based on the session identifier; perform two-way authentication with the robot based on the operation and maintenance session, and after the two-way authentication is successful, establish a communication channel between the operation and maintenance platform and the robot according to the session identifier; The robot is used to execute the current remote maintenance request based on the communication channel.
[0012] Thirdly, the present invention provides a robot including a memory and a processor, wherein the memory stores a computer program, and the computer program, when executed by the processor, implements the robot remote operation and maintenance method as described in any of the foregoing embodiments.
[0013] Fourthly, the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the remote operation and maintenance method for a robot as described in any of the foregoing embodiments.
[0014] This invention discloses a remote operation and maintenance method, system, robot, and readable storage medium for robots. The method involves obtaining the robot's current remote operation and maintenance request from the operation and maintenance terminal through an operation and maintenance platform, and verifying the current remote operation and maintenance request and the robot's current state. Upon successful verification, the operation and maintenance platform generates a session identifier corresponding to the current remote operation and maintenance request and establishes an operation and maintenance session based on the session identifier. Based on the operation and maintenance session, two-way authentication is performed between the operation and maintenance platform and the robot. After successful two-way authentication, a communication channel is established between the operation and maintenance platform and the robot according to the session identifier. The robot then executes the current remote operation and maintenance request through the communication channel. This verification of the current remote operation and maintenance request and the robot's current state avoids the security risks associated with traditional one-time authentication and long-term trust, effectively improving the overall security of remote operation and maintenance. By dynamically establishing an independent two-way authenticated encrypted communication operation and maintenance session for each remote operation and maintenance task, session-level isolation of the operation and maintenance communication link is achieved, preventing eavesdropping, tampering, or lateral exploitation of communication. Attached Figure Description
[0015] To more clearly illustrate the technical solution of the present invention, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope of protection of the present invention. In the various drawings, similar components are numbered similarly.
[0016] Figure 1 A flowchart of the robot remote operation and maintenance method proposed in this embodiment is shown; Figure 2 Another flowchart of the robot remote operation and maintenance method proposed in this embodiment is shown; Figure 3 This illustration shows another flowchart of the robot remote operation and maintenance method proposed in this embodiment; Figure 4 A schematic diagram of the robot remote operation and maintenance system proposed in this embodiment is shown.
[0017] Explanation of reference numerals in the attached diagram: 400 - Robotic Remote Operation and Maintenance System; 401 - Operation and Maintenance Platform; 402 - Robot. Detailed Implementation
[0018] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.
[0019] The components of the embodiments of the invention described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.
[0020] In the following, the terms “comprising,” “having,” and their cognates, which may be used in various embodiments of the invention, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as excluding, firstly, the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations thereof.
[0021] Furthermore, the terms "first," "second," and "third" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.
[0022] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of the invention pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be interpreted as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of the invention.
[0023] This disclosure provides a method for remote operation and maintenance of robots, which addresses the issue of low security in existing remote operation and maintenance processes for robots.
[0024] Please see Figure 1 The remote operation and maintenance method for this robot includes steps S101 to S104, and each step is described in detail below.
[0025] Step S101: Obtain the robot's current remote maintenance request from the maintenance terminal through the maintenance platform, and verify the current remote maintenance request and the robot's current status.
[0026] In this embodiment, maintenance personnel initiate a current remote maintenance request for the robot to the maintenance platform via a maintenance terminal. The maintenance platform verifies the current remote maintenance request and the robot's current status. The current remote maintenance request includes at least the maintenance personnel's identity information, maintenance terminal characteristics, the target robot identifier, and the maintenance task type.
[0027] In one specific embodiment, the current remote operation and maintenance request includes dynamic authentication information, context-aware information, and risk-driven decision information, and the current state includes running state, firmware state, and network environment state. Step S101 includes: performing multi-factor authentication on the dynamic authentication information, the context-aware information, and the risk-driven decision information; and performing trusted verification on the running state, the firmware state, and the network environment state.
[0028] In this embodiment, the operations and maintenance platform is based on a zero-trust architecture and performs multi-factor authentication on dynamic identity verification information, context-aware information, and risk-driven decision-making information. Dynamic identity verification information includes the identity information of operations and maintenance personnel, operations and maintenance terminals, and the operations and maintenance platform, such as usernames and passwords, TOTP verification codes, biometrics, and hardware tokens. Context-aware information may include geolocation verification. Risk-driven decision-making information may include intelligent risk control.
[0029] Simultaneously, trusted verification is performed on the running status, firmware status, and network environment status. The running status may include at least one of the following: CPU status, memory status, process status, etc.; the firmware status may include firmware integrity status; and the network environment status may include communication channel security status, abnormal traffic status, and authorized connection status.
[0030] Understandably, by introducing the zero-trust security concept into the remote operation and maintenance process, continuous identity verification is implemented for operation and maintenance personnel, operation and maintenance terminals, operation and maintenance platforms and robotic equipment, avoiding the security risks brought about by the traditional one-time authentication and long-term trust mechanism, and fundamentally improving the security and reliability of the remote operation and maintenance process.
[0031] Step S102: After verification, the operation and maintenance platform generates a session identifier corresponding to the current remote operation and maintenance request, and establishes an operation and maintenance session based on the session identifier.
[0032] In this embodiment, once the verification is successful, the operation and maintenance platform generates a unique session identifier for the current remote operation and maintenance request, providing an accurate operation context marker for subsequent operations. Different operation and maintenance tasks do not interfere with each other, avoiding permission confusion or cross-contamination. Furthermore, an operation and maintenance session is established based on the session identifier, and the session management state is entered.
[0033] In this context, successful verification means that both multi-factor authentication and trusted verification are successful. If either fails, the establishment of an operation and maintenance session will be refused.
[0034] It should be noted that the specific steps for generating a session identifier include: generating a unique ID based on the maintenance task and participating entities (personnel, equipment, etc.) information in the current remote maintenance request, combined with a timestamp; further using an encryption algorithm (such as HMAC) to ensure that the session identifier cannot be forged; and further digitally signing the session identifier to ensure that it is not tampered with during transmission.
[0035] Step S103: Based on the operation and maintenance session, two-way identity authentication is performed between the operation and maintenance platform and the robot. After the two-way identity authentication is successful, a communication channel between the operation and maintenance platform and the robot is established according to the session identifier.
[0036] In this embodiment, based on the operation and maintenance session, the operation and maintenance platform and the robot perform two-way identity authentication. After the two-way identity authentication is successful, an independent and encrypted communication channel is established between the operation and maintenance platform and the robot according to the session identifier, so as to realize session-level isolation of the operation and maintenance communication link.
[0037] It should be noted that for two-way authentication, the operation and maintenance platform and the robot device each generate a public-private key pair; the two parties exchange public keys and verify each other's identities; the operation and maintenance platform sends an encryption challenge to the robot device, the device decrypts it with its private key and returns the verification information; the robot device sends an encryption challenge to the platform, and the platform establishes a communication channel after successful verification.
[0038] Step S104: The robot executes the current remote maintenance request based on the communication channel.
[0039] In this embodiment, the robot executes the current remote operation and maintenance request based on the communication channel, thereby ensuring that all remote operations are performed in a controlled, encrypted, and traceable communication channel environment, eliminating plaintext transmission, bypass operation, or local privilege escalation to bypass remote supervision, and realizing closed-loop security management throughout the entire process; at the same time, it also reduces the problem of misoperation or loss of instructions due to identity confusion, and improves the success rate of operation and maintenance.
[0040] Please see Figure 2 In one specific embodiment, step S104 includes steps S1041 to S1043, and each step is described in detail below.
[0041] Step S1041: The operation and maintenance platform generates an operation and maintenance permission policy based on the current remote operation and maintenance request and the preset security policy.
[0042] In this embodiment, the operation and maintenance platform generates an operation and maintenance permission policy based on the preset security policy, as well as the operation and maintenance task type, operation instruction level, and operation and maintenance time window in the current remote operation and maintenance request. Generally, only the permissions required to complete the current task are granted to prevent permission abuse or lateral penetration.
[0043] Step S1042: The operation and maintenance permission policy is transmitted from the operation and maintenance platform to the robot through the communication channel.
[0044] In this embodiment, the operation and maintenance permission policy is transmitted from the operation and maintenance platform to the robot through a communication channel to prevent the policy from being eavesdropped on, tampered with or forged, and to ensure that the robot receives original and reliable authorization instructions.
[0045] Step S1043: The robot executes instructions according to the operation and maintenance permission policy.
[0046] In this embodiment, the robot executes instructions according to the operation and maintenance permission policy, thereby achieving fine-grained access control and operation and maintenance security.
[0047] Please see Figure 3 In one specific embodiment, step S1043 includes steps S301 to S303, and each step is described in detail below.
[0048] Step S301: The robot determines the executable instructions according to the operation and maintenance permission policy.
[0049] In this embodiment, the robot determines the executable instructions for which permissions are granted based on the operation and maintenance permission policy, and only allows instructions within the predefined function set to be executed, preventing arbitrary code execution or script injection attacks.
[0050] Step S302: Perform permission verification on the executable instruction according to the operation and maintenance permission policy and the current remote operation and maintenance request.
[0051] In this embodiment, the executable instructions are validated according to the operation and maintenance permission policy and the current remote operation and maintenance request to avoid unauthorized operations.
[0052] As an example, the process involves verifying the authorization scope of executable instructions based on the operation and maintenance (O&M) permission policy; obtaining O&M personnel permissions based on their identity information and instruction permissions based on the executable instructions; matching O&M personnel permissions and instruction permissions to determine the instruction permission verification result for the executable instructions; obtaining the O&M time window in the current O&M request and the instruction time window corresponding to the executable instructions to determine the time limit verification result; if all verification results are successful, the permission verification passes. Security policies can also be configured, such as requiring additional secondary verification for certain sensitive operations.
[0053] Step S303: After the permission verification is passed, the executable instruction is executed.
[0054] In this embodiment, after the permission verification is passed, the robot executes executable instructions to achieve remote operation and maintenance, ensuring that any instruction has undergone a strict approval process and complies with information security.
[0055] In one specific embodiment, after step S1043, the following steps are included: recording the execution log of the executable instruction and the operation and maintenance behavior status; and performing security audit on the operation and maintenance behavior status.
[0056] In this embodiment, the execution process of executable instructions is monitored in real time, execution logs and operation and maintenance behavior status are recorded, and security audits are performed to achieve full-process traceability, support post-event traceability analysis, and provide a data foundation for the generation of automated compliance reports.
[0057] In one specific embodiment, the method further includes: if abnormal operation and maintenance behavior exists, triggering a security handling operation according to a preset security policy.
[0058] In this embodiment, if there are abnormal operation and maintenance behaviors such as unauthorized operation, abnormal instructions, or changes in risk level, security actions such as permission revocation, permission downgrade, session freezing, or communication interruption will be triggered according to the preset security policy to realize an active defense mechanism. When suspicious behavior is detected, the session can be automatically interrupted, the account can be locked, or an alarm can be reported, thus shortening the response time.
[0059] Among them, unauthorized operations are detected by comparing the permissions of maintenance personnel with the instructions required; if the permissions are exceeded, it is considered unauthorized. Abnormal instructions are detected through behavior analysis and pattern recognition; if they do not conform to the preset operation process, they are detected. Changes in risk level are assessed through real-time monitoring; for example, abnormal access frequency, abnormal geographical location, or changes in device identification can trigger an increase in risk level.
[0060] In one specific embodiment, the method further includes: after the current remote operation and maintenance request is completed, or after the operation and maintenance session is abnormally terminated, performing operation and maintenance session destruction, operation and maintenance permission revocation, and data erasure.
[0061] In this embodiment, if the current remote operation and maintenance request is completed, or if the operation and maintenance session is terminated abnormally, the operation and maintenance session is automatically destroyed, the operation and maintenance permissions are revoked, and the communication key and session-related data are cleared through data erasure to prevent residual sessions from being reused or permissions from being persistently abused, thus ensuring data security.
[0062] The robot remote operation and maintenance method proposed in this embodiment obtains the robot's current remote operation and maintenance request from the operation and maintenance terminal through the operation and maintenance platform, and verifies the current remote operation and maintenance request and the robot's current state. Upon successful verification, the operation and maintenance platform generates a session identifier corresponding to the current remote operation and maintenance request, and establishes an operation and maintenance session based on the session identifier. Based on the operation and maintenance session, two-way authentication is performed between the operation and maintenance platform and the robot. After successful two-way authentication, a communication channel is established between the operation and maintenance platform and the robot according to the session identifier. The robot then executes the current remote operation and maintenance request through the communication channel. This verification of the current remote operation and maintenance request and the robot's current state avoids the security risks associated with traditional one-time authentication and long-term trust, effectively improving the overall security of remote operation and maintenance. By dynamically establishing an independent two-way authenticated encrypted communication operation and maintenance session for each remote operation and maintenance task, session-level isolation of the operation and maintenance communication link is achieved, preventing eavesdropping, tampering, or lateral exploitation of communication.
[0063] Furthermore, this disclosure provides a robot remote operation and maintenance system 400, please refer to [link to relevant documentation]. Figure 4 ,include: The operation and maintenance platform 401 is used to obtain the current remote operation and maintenance request of the robot from the operation and maintenance terminal, verify the current remote operation and maintenance request and the current status of the robot; generate a session identifier corresponding to the current remote operation and maintenance request, and establish an operation and maintenance session based on the session identifier; perform two-way authentication with the robot based on the operation and maintenance session, and after the two-way authentication is successful, establish a communication channel between the operation and maintenance platform and the robot according to the session identifier; The robot 402 is used to execute the current remote maintenance request based on the communication channel.
[0064] Optionally, the operation and maintenance platform 401 is further configured to generate an operation and maintenance permission policy based on the current remote operation and maintenance request and a preset security policy; and transmit the operation and maintenance permission policy to the robot through the communication channel; The robot 402 is also used to execute instructions according to the operation and maintenance permission policy.
[0065] Optionally, the robot 402 is further configured to determine executable instructions based on the operation and maintenance permission policy; perform permission verification on the executable instructions based on the operation and maintenance permission policy and the current remote operation and maintenance request; and execute the executable instructions after the permission verification is passed.
[0066] Optionally, the operation and maintenance platform 401 is also used to record the execution log of the executable instructions and the operation and maintenance behavior status; and to perform security audits on the operation and maintenance behavior status.
[0067] Optionally, the operation and maintenance platform 401 is also used to trigger a security handling operation according to a preset security policy if abnormal operation and maintenance behavior occurs.
[0068] Optionally, the operation and maintenance platform 401 is also used to perform operation and maintenance session destruction, operation and maintenance permission revocation and data erasure when the current remote operation and maintenance request is completed or when the operation and maintenance session is abnormally terminated.
[0069] Optionally, the current remote operation and maintenance request includes dynamic authentication information, context-aware information, and risk-driven decision information. The current state includes running state, firmware state, and network environment state. The operation and maintenance platform 401 is also used to perform multi-factor authentication on the dynamic authentication information, the context-aware information, and the risk-driven decision information; and to perform trusted verification on the running state, the firmware state, and the network environment state.
[0070] The system provided in this embodiment can execute the steps of the aforementioned remote operation and maintenance method for robots, and will not be repeated here to avoid repetition.
[0071] The robot remote operation and maintenance system proposed in this embodiment obtains the robot's current remote operation and maintenance request from the operation and maintenance terminal through the operation and maintenance platform, and verifies the current remote operation and maintenance request and the robot's current state. Upon successful verification, the operation and maintenance platform generates a session identifier corresponding to the current remote operation and maintenance request, and establishes an operation and maintenance session based on the session identifier. Based on the operation and maintenance session, two-way authentication is performed between the operation and maintenance platform and the robot. After successful two-way authentication, a communication channel is established between the operation and maintenance platform and the robot according to the session identifier. The robot then executes the current remote operation and maintenance request through the communication channel. This verification of the current remote operation and maintenance request and the robot's current state avoids the security risks associated with traditional one-time authentication and long-term trust, effectively improving the overall security of remote operation and maintenance. By dynamically establishing an independent two-way authenticated encrypted communication operation and maintenance session for each remote operation and maintenance task, session-level isolation of the operation and maintenance communication link is achieved, preventing eavesdropping, tampering, or lateral exploitation of communication.
[0072] Furthermore, embodiments of this disclosure provide a robot, including a memory and a processor, wherein the memory stores a computer program, and the computer program, when executed by the processor, implements the aforementioned remote operation and maintenance method for the robot.
[0073] The device provided in this embodiment can perform the steps of the aforementioned remote operation and maintenance method for robots, and will not be repeated here to avoid repetition.
[0074] This disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned remote robot operation and maintenance method.
[0075] In this embodiment, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0076] The computer-readable storage medium provided in this embodiment can implement the aforementioned remote operation and maintenance method for robots. To avoid repetition, it will not be described again here.
[0077] In all examples shown and described herein, any specific values should be interpreted as merely exemplary and not as limitations; therefore, other examples of exemplary embodiments may have different values.
[0078] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.
[0079] The above-described embodiments are merely illustrative of several implementations of the present invention, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention.
Claims
1. A method for remote operation and maintenance of a robot, characterized in that, include: The current remote maintenance request of the robot is obtained from the maintenance terminal through the maintenance platform, and the current remote maintenance request and the current status of the robot are verified. Once the verification is successful, the operation and maintenance platform generates a session identifier corresponding to the current remote operation and maintenance request, and establishes an operation and maintenance session based on the session identifier; Based on the operation and maintenance session, two-way identity authentication is performed between the operation and maintenance platform and the robot. After the two-way identity authentication is successful, a communication channel between the operation and maintenance platform and the robot is established according to the session identifier. The robot executes the current remote maintenance request based on the communication channel.
2. The remote operation and maintenance method for robots according to claim 1, characterized in that, The step of executing the current remote maintenance request via the robot based on the communication channel includes: The operation and maintenance platform generates operation and maintenance permission policies based on the current remote operation and maintenance request and preset security policies. The operation and maintenance permission policy is transmitted from the operation and maintenance platform to the robot through the communication channel; The robot executes instructions according to the operation and maintenance permission policy.
3. The remote operation and maintenance method for robots according to claim 2, characterized in that, The execution of instructions by the robot according to the operation and maintenance permission policy includes: The robot determines executable instructions based on the operation and maintenance permission policy. The executable instruction is validated for permissions based on the operation and maintenance permission policy and the current remote operation and maintenance request. After the permission verification is successful, the executable instruction will be executed.
4. The remote operation and maintenance method for robots according to claim 3, characterized in that, After the robot executes the instruction according to the operation and maintenance permission policy, it includes: Record the execution log of the executable instructions and the status of operational and maintenance behaviors; Perform security audits on the operational and maintenance behavior status.
5. The remote operation and maintenance method for robots according to claim 1, characterized in that, The method further includes: If abnormal operation and maintenance behavior is detected, security measures will be triggered according to the preset security policy.
6. The remote operation and maintenance method for robots according to claim 1, characterized in that, The method further includes: After the current remote operation and maintenance request is completed, or after the operation and maintenance session is terminated abnormally, the operation and maintenance session is destroyed, operation and maintenance permissions are revoked, and data is erased.
7. The remote operation and maintenance method for robots according to claim 1, characterized in that, The current remote maintenance request includes dynamic authentication information, context-aware information, and risk-driven decision information. The current state includes operating status, firmware status, and network environment status. Verifying the current remote maintenance request and the robot's current state includes: Multi-factor authentication is performed on the dynamic identity verification information, the context-aware information, and the risk-driven decision information; The operating status, firmware status, and network environment status are verified using a trusted method.
8. A remote operation and maintenance system for robots, characterized in that, include: The operation and maintenance platform is used to obtain the current remote operation and maintenance request of the robot from the operation and maintenance terminal, and to verify the current remote operation and maintenance request and the current status of the robot. Generate a session identifier corresponding to the current remote operation and maintenance request, and establish an operation and maintenance session based on the session identifier; perform two-way authentication with the robot based on the operation and maintenance session, and after the two-way authentication is successful, establish a communication channel between the operation and maintenance platform and the robot according to the session identifier; The robot is used to execute the current remote maintenance request based on the communication channel.
9. A robot, characterized in that, It includes a memory and a processor, the memory storing a computer program that, when executed by the processor, implements the robot remote operation and maintenance method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the remote operation and maintenance method for robots as described in any one of claims 1 to 7.