CN116405526A - Robot management method, electronic device, management system, and storage medium - Google Patents

Robot management method, electronic device, management system, and storage medium Download PDF

Info

Publication number
CN116405526A
CN116405526A CN202310327008.8A CN202310327008A CN116405526A CN 116405526 A CN116405526 A CN 116405526A CN 202310327008 A CN202310327008 A CN 202310327008A CN 116405526 A CN116405526 A CN 116405526A
Authority
CN
China
Prior art keywords
robot
user
server
information
permission
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
CN202310327008.8A
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.)
Uditech Co Ltd
Original Assignee
Uditech 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 Uditech Co Ltd filed Critical Uditech Co Ltd
Priority to CN202310327008.8A priority Critical patent/CN116405526A/en
Publication of CN116405526A publication Critical patent/CN116405526A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/01—Customer relationship services
    • G06Q30/015—Providing customer assistance, e.g. assisting a customer within a business location or via helpdesk
    • G06Q30/016—After-sales
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/105—Multiple levels of security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Accounting & Taxation (AREA)
  • Medical Informatics (AREA)
  • Bioethics (AREA)
  • Manipulator (AREA)

Abstract

The invention relates to a robot management method, electronic equipment and a storage medium, and belongs to the technical field of electronic equipment control. A robot management method includes: sending an authorization request to a server according to the user information, wherein the server is used for managing the user information and the robot; receiving a license response fed back by the server based on the authorization request, and establishing an association relationship according to the use permission of the license response and the user information; and receiving a use instruction sent by a user to the robot, and responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use permission. If the user wants to experience various functions of the robot, the user needs to send an authorization request to the server based on the robot, after the user obtains the authorization permission, the user side can use the robot in the use range of the permission, and the newly developed functions of the robot can be conveniently authorized to the user for use by the server, so that the product use experience is improved.

Description

Robot management method, electronic device, management system, and storage medium
Technical Field
The present invention relates to the field of electronic device control technologies, and in particular, to a robot management method, a robot management device, an electronic device, a robot management system, and a computer readable storage medium.
Background
With the rapid development of artificial intelligence technology, the robot industry has rapidly developed in recent years, has wide application in different fields, and permeates various aspects of social life. With the increase of the number of robots, how to effectively manage a large number of robots becomes an important research direction. At present, for the robot after selling or renting, the robot manufacturer does not perform standardization management on after-sales services of the robot, so that users are difficult to keep pace with development of the robot manufacturer in the process of purchasing and using the robot, and the product use experience is poor.
Disclosure of Invention
The invention provides a robot management method, electronic equipment and a storage medium, which are used for improving the experience of product use.
In a first aspect, the present invention proposes a robot management method, applied to a robot, the method comprising:
sending an authorization request to a server according to the user information, wherein the server is used for managing the user information and the robot;
receiving a license response fed back by the server based on the authorization request, and establishing an association relationship according to the use permission of the license response and the user information;
and receiving a use instruction sent by a user to the robot, and responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use permission.
In other embodiments of the invention, the user information includes a user account and a password to log in to the user account;
the step of sending an authorization request to the server according to the user information comprises the following steps:
receiving a user account and a password input by a user, and sending the user account and the password to a server for validity verification, wherein the server verifies the user according to the received user account and password, if the user account and the password are successfully registered in the server, the user is a registered user, and a verification result fed back to the robot is that the user is the registered user;
if the verification result fed back by the robot is that the user is a registered user, generating an authorization request based on the user account and the password of the login user account;
an authorization request is sent to a server.
In other embodiments of the present invention, the step of establishing an association between the usage rights of the license response and the user information by the receiving server based on the license response fed back by the authorization request includes:
receiving a permission response fed back by the server based on the authorization request, wherein the server verifies whether the user information is the information of the registered user according to the received authorization request, and if the user information is the information of the registered user, feeds back the permission response to the robot, wherein the permission response carries the use range of the use permission of the robot function;
And establishing an association relation between the use authority of the permission response and the user information so that the user can operate the robot based on the use range of the use authority.
In other embodiments of the present invention, the steps of receiving a use instruction sent by a user to a robot, and responding to the use instruction to enable the robot to perform a corresponding action within a use range of a use right, include:
receiving a use instruction sent by a user to a robot;
if the use instruction indicates that the corresponding action executed by the robot belongs to the use range of the authorized use authority, responding to the use instruction to enable the robot to execute the corresponding action in the use range of the use authority;
if the use instruction indicates that the corresponding action executed by the robot does not belong to the use range of the authorized use permission, the use instruction is not responded or a prompt message is given to prompt that no permission operation exists.
In other embodiments of the invention, the use instruction is a first instruction for instructing the robot to send a first request to the server requesting use of the first additional function;
the method comprises the steps of receiving a use instruction sent by a user to a robot, responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use authority, and comprising the following steps:
And receiving a first instruction sent by the user to the robot, and responding to the first instruction to enable the robot to send a first request for requesting to use the first additional function to the server, wherein the server requests to pay corresponding first fees to the user according to the first request, and if the user pays the first fees to the server, the server opens corresponding first additional functions to the robot, and the use range of the use permission comprises the use range of the first additional function.
In other embodiments of the present invention, after the step of establishing the association between the usage rights of the license response and the user information, the method further includes:
establishing a secret folder in a robot local storage;
the use data generated by the robot operation is stored in a secret folder;
after the user authentication passes, the user may access the data of the secure folder.
In other embodiments of the present invention, before the step of sending the authorization request to the server according to the user information, the method further comprises:
and sending a user registration request to the server according to the identity information of the user, wherein if the server successfully registers according to the identity information of the user, the user information successfully registered by the user is fed back to the robot.
In other embodiments of the invention, the method further comprises:
when the robot fails, requesting a user whether to request a server for fault diagnosis;
after obtaining user consent, the fault diagnosis is requested to the server, and the robot is subjected to fault processing based on the fault diagnosis result.
In a second aspect, the present invention also provides a robot management device applied to a robot, the device comprising:
the request module is used for sending an authorization request to the server according to the user information, wherein the server is used for managing the user information and the robot;
the association module is used for receiving a license response fed back by the server based on the authorization request, and establishing an association relationship according to the use permission of the license response and the user information;
and the management module is used for receiving the use instruction sent by the user to the robot and responding to the use instruction so as to enable the robot to execute corresponding actions within the use range of the use permission.
In a third aspect, the present invention also proposes an electronic device comprising a memory, a processor and a computer program stored in said memory and executable on said processor, said processor implementing the steps of the robot management method according to the first aspect described above when said computer program is executed.
The fourth aspect of the present invention also proposes a management system, comprising:
the robot according to the first aspect;
and the server is used for managing the user information and the robot.
In a fifth aspect, an embodiment of the present invention proposes a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the robot management method according to the first aspect described above.
In a sixth aspect, an embodiment of the present invention provides a computer program product for causing an electronic device to execute the steps of the robot management method according to the first aspect.
In the present invention, an authorization request is transmitted to a server according to user information, unlike the case of the related art; receiving a license response fed back by the server based on the authorization request, and establishing an association relationship according to the use permission of the license response and the user information; and receiving a use instruction sent by a user to the robot, and responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use permission. Therefore, if a user wants to experience various functions of the robot, the user needs to send an authorization request to the server based on the robot, after the user obtains the authorization permission, the user side can use the robot in the use range of the permission, and the newly developed functions of the robot can be conveniently authorized to the user through the server for use, so that the product use experience is improved.
Drawings
One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures of the drawings are not to scale, unless expressly stated otherwise.
Fig. 1 is a schematic view of an application scenario of a robot management method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a robot management method according to an embodiment of the present invention;
FIG. 3 is a functional block diagram of a robot management device according to an embodiment of the present invention;
fig. 4 is a schematic hardware structure of an electronic device according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
It should be noted that, if not in conflict, the features of the embodiments of the present invention may be combined with each other, which are all within the protection scope of the present invention. In addition, while the division of functional blocks is performed in a device diagram and the logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in a device diagram or the sequence in a flowchart.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items.
Referring to fig. 1, fig. 1 is a schematic view of an application scenario of a robot management method according to an embodiment of the invention. The execution main body of the robot management method is electronic equipment, and the electronic equipment can be a mobile service robot and has an autonomous positioning navigation function. The robot can provide various robot services such as goods distribution, welcome guidance, carrying, cleaning, inspection, advertisement pushing and the like in application scenes such as hotels, KTVs and the like, and the functions of the robot are not limited herein. As shown in fig. 1, the robot 10 is in communication connection with the server 20, the robot 10 is in communication connection with the user terminal 30, the server 20 is in communication connection with the user terminal 30, and the communication connection mode includes wired network and/or wireless network connection, and it is understood that the network includes wireless networks such as 2G, 3G, 4G, 5G, wireless local area network, bluetooth, and the like, and may also include wired networks such as serial port line, network line, and the like. The server 20 in the embodiment of the present invention is a platform for unified management of all robots 10 shipped from a robot manufacturer, and may also be referred to as a company-level background management system, for unified management of various types of robots 10 produced by the robot manufacturer. The user terminal 30 is a platform for managing the robot 10, which may also be referred to as a background management system of the robot 10, and a robot manufacturer may develop corresponding program software for a customer to use, so that the customer manages or uses the robot 10 through the user terminal 20.
Referring to fig. 2, fig. 2 is a flowchart illustrating a robot management method according to an embodiment of the invention. In a first aspect, an embodiment of the present invention proposes a robot management method, an execution subject of which is an electronic device, for example, a robot 10 as shown in fig. 1, the robot management method includes steps S21 to S23 as follows:
and step S21, sending an authorization request to a server according to the user information, wherein the server is used for managing the user information and the robot.
The user information is used to identify the user, for example, the user information includes a user account and a password to log in to the user account. The user can register or log in the account number in the corresponding program software of the user terminal, and after the user successfully logs in the user account number, the robot associated with the user account can be operated in the user terminal so that the robot can execute corresponding actions. The server is for recording or managing user information of the user and information of the robot. Illustratively, the database of the server stores a robot number for identifying each robot, a function of the robot, or all information about the robot. Simultaneously, the database of the server also stores user information of the user. When a user applies for an account to a server based on a user terminal, the server records a user account number provided by the user, a password for logging in the user account, user authentication information (password, fingerprint or voiceprint) and the like, and sends a user registration request to the server at home, and if the server successfully registers according to the identity information of the user, a database of the server stores the registration information of the user or various information of the user.
In this embodiment, after the user has applied for and successfully registered the user account in the server, if the user inputs the user account and the password for logging in the user account to the robot, if logging in is successful, an authorization request is sent to the server according to the user information. The authorization request is used to apply a server for a scope of use of the use right to use the robot function.
Illustratively, the user information includes a user account and a password to log in to the user account. The step of sending an authorization request to the server according to the user information comprises: receiving a user account and a password input by a user, and sending the user account and the password to a server for validity verification, wherein the server verifies the user according to the received user account and password, if the user account and the password are successfully registered in the server, the user is a registered user, and a verification result fed back to the robot is that the user is the registered user; if the verification result fed back by the robot is that the user is a registered user, generating an authorization request based on the user account and the password of the login user account; an authorization request is sent to a server.
In some embodiments, the robot is provided with a user interface (e.g., a touch screen) for the robot to interact with a user human. The user interface of the robot is displayed with a display frame for guiding a user to input a user account number and a login password. The robot is communicatively connected to the server. When a user outputs user account information and a password on a user interface, the robot sends the received user account and password to a server. When the server receives the user account and the password sent by the robot, the server performs validity verification on the user according to the user account and the password. For example, if the user has successfully registered the user account with the server, the cryptographic association of the user account and the login user account is stored in the server. When the server searches the database of the server based on the user account, if the recorded account of the registered user matched with the user account is found, the user is indicated to be successfully registered in the server, and the user is the registered user; and if the recorded account number of the registered user matched with the user account number is not found, the user is described as an unregistered user. When the server determines that the user is a registered user according to the user account and the password, the authentication result fed back to the robot is that the user is the registered user, so that the robot generates an authorization request based on the user account and the password of the login user account, and sends the authorization request to the server. When the server determines that the user is an unregistered user according to the user account number and the password, the verification result fed back to the robot is that the user is an unregistered user, so that the robot pops up prompt information, for example, the prompt information is that the user is an unregistered user, and the robot cannot be used. And, the robot does not generate an authorization request based on the unregistered user account and password.
The robot generates an authorization request based on the user account of the registered user and the password of the login user account, and sends the authorization request to the server. The authorization request carries a robot number for uniquely identifying the robot, and the file information of the robot is stored in the server in an associated manner through the robot number. In the process of production, debugging, use and maintenance of the robot, various information data generated by the robot are stored in a database of a server through file information of the robot, for example, the file information of the robot comprises hardware information, software version information, delivery time, maintenance records, functional parameters of the robot and the like. It will be appreciated that the server may find and access profile information for the robot based on the robot number.
In other embodiments of the present invention, before the step of sending the authorization request to the server according to the user information, the robot management method further includes: and sending a user registration request to the server according to the identity information of the user, wherein if the server successfully registers according to the identity information of the user, the user information successfully registered by the user is fed back to the robot.
The user may initiate a registration request to the server based on the robot or user terminal. Taking a user interface of a robot as an example, a user establishes communication connection with a server based on the user interface of the robot, and the user interface of the robot is displayed with a window for guiding the user to initiate registration to the server. The identity information of the user is input to the user according to the guidance of a user interface of the robot, wherein the identity information can be the identity ID of the user, the name of the user account, the login password of the user account, the reserved mobile phone number or fingerprint information and the like, and the robot sends the identity information of the user to the server. If the server already has the identity information of the user, the user is indicated to be a registered user. And if the server does not have the identity information of the user, registering the user to record the user as a registered user.
If the server registers successfully according to the identity information of the user, user information of the user successfully registered is fed back to the robot, for example, a successfully registered user account and password are fed back to the robot, so that the robot displays the user account of the user and the password of the login user account to the user based on a user interface.
Step S22, the receiving server establishes an association relationship according to the use authority of the license response and the user information based on the license response fed back by the authorization request.
When the server receives an authorization request sent by the robot, the server authorizes the robot to the registered user for use according to the authorization request. That is, the server authorizes the robot corresponding to the robot number in the authorization request to the current registered user, wherein the authorization request carries the robot number of the robot and the user information of the current user. The license response is a feedback signal made by the server based on the received authorization request, wherein the license response may carry information of the usage range of the usage rights, including, but not limited to, a distribution function on or off, an attach guide function on or off, a cleaning function on or off, a patrol function on or off, an entertainment function on or off, and so on. The use rights of the license response are used to open certain part or all of the functions of the robot for use by authorized users. When the robot receives the permission response, the server is indicated to permit the robot to be used by the current user. Illustratively, the permission response is a permission to turn on the cleaning function, and when the robot receives the permission response, the robot then initiates the associated hardware and software drivers of the cleaning function, thereby providing the robot with an automatic cleaning capability. For another example, the permission response may be a permission to start the entertainment function, and when the robot receives the permission response, the robot starts hardware and software drivers associated with the entertainment function, thereby enabling the robot to have the multimedia entertainment function.
After receiving the license response, the robot establishes an association relationship according to the use authority of the license response and the user information. That is, the user can operate the robot based on the usage rights of the function module opened by the robot. After the robot establishes an association relationship between the use authority of the permission response and the user information, the robot is controlled and used by the user in a specific use range based on the established association relationship. For example, the user a applies to the server that the cleaning function is started, and after the authorization is obtained, the cleaning function of the robot R is controlled and used by the user a; further, the user B applies to the server for the use authority to start the distribution function, and after the authorization is obtained, the distribution function of the robot R is controlled and used by the user B.
In the present embodiment, one robot may have various functions, for example, function 1, function 2, function 3, … …, function n, and the use range of the use authority includes turning on the use of these functions, or turning off these functions. One user may apply for one or more functions to one robot, and another other user may apply for one or more functions to the robot, and the functions required to be used by the two users may be the same or partially the same or all different, and after obtaining the server authorization permission, one user or more users may share the robot at the same time, thereby improving the use efficiency of the robot, and in addition, the service resources of the robot may be utilized with maximum benefit.
Illustratively, in step S22, the step of receiving a license response fed back by the server based on the authorization request, and establishing an association relationship according to the usage rights of the license response and the user information includes: receiving a permission response fed back by the server based on the authorization request, wherein the server verifies whether the user information is the information of the registered user according to the received authorization request, and if the user information is the information of the registered user, feeds back the permission response to the robot, wherein the permission response carries the use range of the use permission of the robot function; and establishing an association relation between the use authority of the permission response and the user information so that the user can operate the robot based on the use range of the use authority.
After the robot sends an authorization request to the server, the server determines whether to feed back a permission response to the robot according to the authorization request, and if the server feeds back the permission response to the robot, the robot establishes an association relation between the use permission of the permission response and the user information so that the user can operate the robot based on the use range of the use permission. The server verifies whether the user information is the information of the registered user according to the received authorization request, if the user information is the information of the registered user, the user is informed that the registered information is registered for the server, the user has the right of using the robot, the server feeds back a permission response to the robot, and the permission response carries the use range of the use right of the robot function; if the user information is the information of the unregistered user, the user is not registered with the server, the user does not have the right to use the robot, the server does not feed back a permission response to the robot, and further, the server can feed back prompt information to the robot so as to convey the warning information that the user is the unregistered user and the robot cannot be used to the robot.
In other embodiments, step S22, after the step of receiving the license response fed back by the server based on the authorization request and establishing the association relationship according to the usage rights of the license response and the user information, the robot management method further includes the steps of: establishing a secret folder in a robot local storage; the use data generated by the robot operation is stored in a secret folder; after the user authentication passes, the user may access the data of the secure folder.
The robot local storage has a data storage function, and a secret folder is established in the robot local storage and is used for storing data in various formats. For example, a window for guiding a user to establish a local security folder is displayed on a user interface of the robot, during the process of establishing the security folder, the user inputs a personal user account number and a login password and sends the personal user account number and the login password to a server for verification, after the server passes the verification to determine that the user is a user authorized to use the robot (registered user), the user is prompted to establish the security folder locally on the robot and the security folder is protected by a password of the user, so that other people are prevented from illegally accessing user data. After the robot local storage establishes the secret folder, the use data generated by the robot operation is stored in the secret folder, and other people have to illegally access the data content in the secret folder under the condition that the personal authorization or password of the user is not obtained. If the data content of the security folder is to be accessed, the identity verification is to be carried out, namely, if the input password or the biological information of the user is consistent with the prestored password for opening the security folder, the identity verification is confirmed to be passed by presetting the password or the biological information of the user (fingerprint, voiceprint, human face characteristics and the like), and the user can access the data content of the security folder; otherwise, the authentication is not passed, and the user cannot access the data content of the secure folder.
It will be appreciated that users not authorized to use the robot (unregistered users) may not establish a secure folder in the robot's local store.
The data content generated by the robot operation is stored in the secret folder, and only the authorized licensor of the user can access the secret folder, so that the user privacy data is ensured, and the user privacy data is prevented from being revealed.
Step S23, receiving a use instruction sent to the robot by a user, and responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use permission.
After determining that the robot function is authorized by the server for use by the user, the robot is provided with the function to serve the user. Thereafter, the robot may receive a use instruction transmitted from the user to the robot and respond to the use instruction to cause the robot to perform a corresponding action within the use range of the use authority. The instructions are for the user to operate the robot, e.g., the instructions are intended to dispense items to room 505, or the instructions are intended to clean the current office, etc. Optionally, the use instruction includes verification information for identity verification and an instruction body, the verification information is used for verifying whether a user sending the use instruction is an authorized user, and the instruction body is used for instructing the robot to execute corresponding actions, including but not limited to dispensing articles and cleaning floors. The authentication information used for authentication may be an identification for uniquely identifying the user, a user terminal identification of the user, or a user account of the user. The robot analyzes the use instruction to acquire the identity authentication information of the user who sends the use instruction and the intention of the robot to execute the action, and if the authentication information of the user who sends the use instruction is consistent with the authentication information of the authorized user, the corresponding action is executed according to the intention of the robot to execute the action.
It will be appreciated that the robot may accept instructions and be able to execute the instructions to make corresponding actions. In one embodiment, after the cleaning function of the robot is authorized by the server for use by the user, the user sends a cleaning instruction to the robot, which then cleans the target area in accordance with the cleaning instruction.
In the invention, if a user wants to experience various functions of the robot, the user needs to send an authorization request to the server based on the robot, and after the user obtains the authorization permission, the user side can use the robot in the use range of the permission, and the newly developed functions of the robot can be conveniently authorized to the user for use by the server, so that the product use experience is improved.
Illustratively, step S23, a step of receiving a use instruction sent by a user to the robot, and responding to the use instruction to make the robot execute a corresponding action within a use range of the use right, includes: receiving a use instruction sent by a user to a robot; if the use instruction indicates that the corresponding action executed by the robot belongs to the use range of the authorized use authority, responding to the use instruction to enable the robot to execute the corresponding action in the use range of the use authority; if the use instruction indicates that the corresponding action executed by the robot does not belong to the use range of the authorized use permission, the use instruction is not responded or a prompt message is given to prompt that no permission operation exists.
After determining that the robot function is authorized by the server for use by the user, the robot is provided with the function to serve the user. The robot may receive a use instruction sent by a user to the robot, for example, the user sends a use instruction to the robot based on a user terminal or a user interface of the robot. Optionally, the use instruction includes verification information for identity verification and an instruction body, the verification information is used for verifying whether a user sending the use instruction is an authorized user, and the instruction body is used for instructing the robot to execute corresponding actions, including but not limited to dispensing articles and cleaning floors. For example, when the robot determines that the user who transmitted the use instruction is the authorized user through the authentication information, the instruction body is executed so that the robot performs the action of dispensing the article. It will be appreciated that when the robot determines that the user who sent the use instruction is an unauthorized user through the authentication information, the instruction body is not executed, and further, a prompt message may be sent to the current user to inform that the current user is an unauthorized user, and the instruction is invalid.
In other embodiments, the use instruction is a first instruction for instructing the robot to send a first request to the server requesting use of the first additional function. Accordingly, step S23, a step of receiving a use instruction sent by a user to the robot, and responding to the use instruction to make the robot execute a corresponding action within the use range of the use authority, includes: and receiving a first instruction sent by the user to the robot, and responding to the first instruction to enable the robot to send a first request for requesting to use the first additional function to the server, wherein the server requests to pay corresponding first fees to the user according to the first request, and if the user pays the first fees to the server, the server opens corresponding first additional functions to the robot, and the use range of the use permission comprises the use range of the first additional function.
It will be appreciated that the robot has a plurality of functions, for example, a plurality of functions including a function 1, a function 2 and a function 3. The user applies for the function of the robot authorized to use to the server as the function 1, and if the user wants to use the function 2, the user needs to apply for the function 2 authorized to use the robot to the server again. The use instruction is a first instruction, where the first instruction is used to instruct the robot to send a first request for requesting to use a first additional function to the server, that is, the instruction body of the use instruction is a first request for instructing the robot to send the request for using the first additional function to the server, where the first additional function is a function of the robot other than the function of the robot that is currently authorized to use, and the first request is used to send the request to the server, where optionally the first request carries information requiring the first additional function authorized to be used by the user. After the server receives the first request, the server parses the first request to obtain a first additional function required to be authorized for the user, and then, the server pays a corresponding first fee to the user according to the first request, where the first additional function corresponds to the first fee, that is, each additional function corresponds to a fee, for example, the fee corresponding to the additional function 1 is 10 yuan, and the fee corresponding to the additional function 2 is 20 yuan. If the user pays the first fee to the server, the server opens a corresponding first additional function to the robot. At this time, the use range of the use authority of the user includes the use range of the first additional function, that is, the user can use the first additional function of the robot.
For example, a user initially applies for a delivery function of authorizing use of the robot to the server, and after obtaining a use right to use the delivery function, the user applies for an additional function (e.g., a cleaning function) of authorizing use of the robot to the server, and after the user pays a corresponding fee for the additional function, the server opens the cleaning function to the robot so that the cleaning function of the robot is available to the user.
In the invention, the user can experience the basic functions of the robot based on the registered user account, if the user wants to experience the additional functions of the robot, the user needs to pay corresponding fees for the additional functions, and after the user pays the fees, the robot can provide more additional functions for the user, so that the operation management is carried out on the robot through the server, the added value of the robot is increased, and the upgrading and transformation of the robot are promoted.
In other embodiments, the robot management method further comprises the steps of: when the robot fails, requesting a user whether to request a server for fault diagnosis; after obtaining user consent, the fault diagnosis is requested to the server, and the robot is subjected to fault processing based on the fault diagnosis result.
The robots are used and managed by the user after being authorized for use by the user. During operation of the robot, if a failure occurs, for example, motor control failure, laser radar failure, network communication device failure, etc., the robot requests from the user whether a failure diagnosis needs to be requested from the server.
It can be appreciated that a fault diagnosis strategy can be operated at the server end, and is used for collecting various operation parameters of the robot and diagnosing the fault of the robot according to the operation parameters. Of course, before the robot calls for help from the server, the user needs to confirm that the robot can collect the running parameters of the robot and feed the parameters back to the server.
Illustratively, when the robot fails to locate, the robot itself determines that a fault has occurred, and sends a request to the user if a fault diagnosis needs to be requested from the server. After obtaining the consent signal sent by the user, the fault diagnosis is requested to the server, and meanwhile, the robot collects own operation parameters, for example, operation diaries or parameter information obtained by the laser radar is sent to the server, the server determines whether the laser radar has faults according to the operation parameters of the operation diaries or the laser radar, and proposes a strategy for eliminating the faults, including but not limited to, enabling the robot to be restarted after soft power failure, enabling the robot to return to an initial position for initial repositioning, recalibrating the laser radar or replacing the laser radar, and the like.
In the present invention, the server may run a fault diagnosis model for performing fault diagnosis and fault handling for the robot. When the robot breaks down, the robot needs to be agreed by an authorized user, and the robot operation parameters can be sent to the server to perform fault diagnosis, so that the server with stronger calculation power is used for diagnosing and assisting in maintaining the fault of the robot, and the use rights and interests of the user are also ensured.
Referring to fig. 3, in a second aspect, a robot management device 30 is provided in an embodiment of the present invention, where the device 30 is configured to be deployed on a robot 10, and the device 30 includes:
a request module 31, configured to send an authorization request to a server according to user information, where the server is configured to manage the user information and the robot;
the association module 32 is configured to receive a license response fed back by the server based on the authorization request, and establish an association relationship according to the usage rights of the license response and the user information;
and the management module 33 is used for receiving the use instruction sent by the user to the robot and responding to the use instruction so as to enable the robot to execute corresponding actions within the use range of the use authority.
In other embodiments, the user information includes a user account and a password to log in to the user account; the request module 31 is further configured to receive a user account and a password input by a user, and send the user account and the password to the server for validity verification, where the server verifies the user according to the received user account and password, if the user account and the password are already registered successfully in the server, the user is a registered user, and the verification result fed back to the robot is that the user is the registered user; if the verification result fed back by the robot is that the user is a registered user, generating an authorization request based on the user account and the password of the login user account; an authorization request is sent to a server.
In other embodiments, the association module 32 is further configured to receive a license response fed back by the server based on the authorization request, where the server verifies whether the user information is information of the registered user according to the received authorization request, and if the user information is information of the registered user, feeds back a license response to the robot, where the license response carries a usage range of usage rights of the robot function; and establishing an association relation between the use authority of the permission response and the user information so that the user can operate the robot based on the use range of the use authority.
In other embodiments, the management module 33 is further configured to receive a use instruction sent by the user to the robot; if the use instruction indicates that the corresponding action executed by the robot belongs to the use range of the authorized use authority, responding to the use instruction to enable the robot to execute the corresponding action in the use range of the use authority; if the use instruction indicates that the corresponding action executed by the robot does not belong to the use range of the authorized use permission, the use instruction is not responded or a prompt message is given to prompt that no permission operation exists.
In other embodiments, the use instruction is a first instruction for instructing the robot to send a first request to the server requesting use of the first additional function; the management module 33 is further configured to receive a first instruction sent by the user to the robot, and respond to the first instruction to cause the robot to send a first request for requesting to use the first additional function to the server, where the server requests to pay a corresponding first fee to the user according to the first request, and if the user pays the first fee to the server, the server opens the corresponding first additional function to the robot, and the usage range of the usage right includes the usage range of the first additional function.
In other embodiments, the management module 33 is further configured to create a secure folder in the robot local store; the use data generated by the robot operation is stored in a secret folder; after the user authentication passes, the user may access the data of the secure folder.
In other embodiments, the request module 31 is further configured to send a user registration request to the server according to the identity information of the user, where if the server successfully registers according to the identity information of the user, the user information of the successful registration of the user is fed back to the robot.
In other embodiments, the management module 33 is further configured to, when the robot fails, request from the user whether a failure diagnosis needs to be requested from the server; after obtaining user consent, the fault diagnosis is requested to the server, and the robot is subjected to fault processing based on the fault diagnosis result.
It can be understood that the implementation principle and the technical effect of the robot management device 30 according to the second aspect of the present invention can refer to the implementation principle and the technical effect of the robot management method according to the first aspect, which are not described herein.
The invention also proposes a management system comprising a robot in the robot management method according to the first aspect described above and a server for managing user information and the robot. The relation between the robot and the server can refer to the implementation principle and the technical effect of the robot management method provided in the first aspect, and are not described herein.
Referring to fig. 4, fig. 4 is a schematic hardware structure of an electronic device 400 according to an embodiment of the invention. The electronic device 400 may be a robot. The electronic device 400 includes: at least one processor 401, and a memory 402 communicatively coupled to the at least one processor 401, one processor 401 being illustrated in fig. 4. The memory 402 stores instructions (or programs) executable by the at least one processor 401, the instructions being executable by the at least one processor 401 to enable the at least one processor 401 to perform the steps of the robot management method of the first aspect of the present invention. The processor 401 and the memory 402 may be connected by a bus or otherwise, for example in fig. 4.
The memory 402 is used as a readable storage medium, and may be used to store a software program, an executable program, and a module, such as a program instruction/module corresponding to a robot management method that needs to be executed by an electronic device in an embodiment of the present invention. The processor 401 executes various functional applications and data processing by running software programs, instructions and modules stored in the memory 402, i.e. implements the steps of the robot management method according to the first aspect of the embodiment of the present invention.
Memory 402 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created by performing the robot management method, and the like. Memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 402 may optionally include memory located remotely from processor 401, which may be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The one or more modules are stored in a memory 402, which when executed by the one or more processors 401, implements the steps of performing the robot management method according to the first aspect of the present invention, e.g. the request module 31, the association module 32 and the management module 33 in the robot management device 30 according to the second aspect of the present invention are stored in the memory 402.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; the technical features of the above embodiments or in the different embodiments may also be combined within the idea of the invention, the steps may be implemented in any order, and there are many other variations of the different aspects of the invention as described above, which are not provided in detail for the sake of brevity; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.

Claims (11)

1. A robot management method, applied to a robot, the method comprising:
sending an authorization request to a server according to the user information, wherein the server is used for managing the user information and the robot;
receiving a license response fed back by the server based on the authorization request, and establishing an association relationship according to the use permission of the license response and the user information;
and receiving a use instruction sent by a user to the robot, and responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use permission.
2. The robot managing method according to claim 1, wherein the user information includes a user account and a password for logging in the user account;
the step of sending an authorization request to the server according to the user information comprises the following steps:
receiving a user account and a password input by a user, and sending the user account and the password to a server for validity verification, wherein the server verifies the user according to the received user account and password, if the user account and the password are successfully registered in the server, the user is a registered user, and a verification result fed back to the robot is that the user is the registered user;
if the verification result fed back by the robot is that the user is a registered user, generating an authorization request based on the user account and the password of the login user account;
An authorization request is sent to a server.
3. The robot managing method according to claim 1, wherein the step of establishing an association between the usage right of the license response and the user information by the receiving server based on the license response fed back by the authorization request, comprises:
receiving a permission response fed back by the server based on the authorization request, wherein the server verifies whether the user information is the information of the registered user according to the received authorization request, and if the user information is the information of the registered user, feeds back the permission response to the robot, wherein the permission response carries the use range of the use permission of the robot function;
and establishing an association relation between the use authority of the permission response and the user information so that the user can operate the robot based on the use range of the use authority.
4. The robot managing method according to claim 1, wherein the step of receiving a use instruction transmitted from the user to the robot and responding to the use instruction to cause the robot to perform a corresponding action within the use range of the use authority, comprises:
receiving a use instruction sent by a user to a robot;
if the use instruction indicates that the corresponding action executed by the robot belongs to the use range of the authorized use authority, responding to the use instruction to enable the robot to execute the corresponding action in the use range of the use authority;
If the use instruction indicates that the corresponding action executed by the robot does not belong to the use range of the authorized use permission, the use instruction is not responded or a prompt message is given to prompt that no permission operation exists.
5. The robot management method according to claim 1, wherein the use instruction is a first instruction for instructing the robot to send a first request requesting use of the first additional function to the server;
the method comprises the steps of receiving a use instruction sent by a user to a robot, responding to the use instruction to enable the robot to execute corresponding actions within the use range of the use authority, and comprising the following steps:
and receiving a first instruction sent by the user to the robot, and responding to the first instruction to enable the robot to send a first request for requesting to use the first additional function to the server, wherein the server requests to pay corresponding first fees to the user according to the first request, and if the user pays the first fees to the server, the server opens corresponding first additional functions to the robot, and the use range of the use permission comprises the use range of the first additional function.
6. The robot managing method according to claim 1, wherein after the step of establishing an association between the license response based on the usage right of the license response and the user information by the receiving server based on the license response fed back by the authorization request, the method further comprises:
Establishing a secret folder in a robot local storage;
the use data generated by the robot operation is stored in a secret folder;
after the user authentication passes, the user may access the data of the secure folder.
7. The robot managing method according to claim 1, wherein before the step of transmitting the authorization request to the server according to the user information, the method further comprises:
and sending a user registration request to the server according to the identity information of the user, wherein if the server successfully registers according to the identity information of the user, the user information successfully registered by the user is fed back to the robot.
8. The robot management method according to claim 1, further comprising:
when the robot fails, requesting a user whether to request a server for fault diagnosis;
after obtaining user consent, the fault diagnosis is requested to the server, and the robot is subjected to fault processing based on the fault diagnosis result.
9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the robot management method according to any of claims 1 to 8 when the computer program is executed.
10. A management system, comprising:
a robot as claimed in any one of claims 1 to 8;
and the server is used for managing the user information and the robot.
11. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the robot management method according to any one of claims 1 to 8.
CN202310327008.8A 2023-03-24 2023-03-24 Robot management method, electronic device, management system, and storage medium Pending CN116405526A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310327008.8A CN116405526A (en) 2023-03-24 2023-03-24 Robot management method, electronic device, management system, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310327008.8A CN116405526A (en) 2023-03-24 2023-03-24 Robot management method, electronic device, management system, and storage medium

Publications (1)

Publication Number Publication Date
CN116405526A true CN116405526A (en) 2023-07-07

Family

ID=87019233

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310327008.8A Pending CN116405526A (en) 2023-03-24 2023-03-24 Robot management method, electronic device, management system, and storage medium

Country Status (1)

Country Link
CN (1) CN116405526A (en)

Similar Documents

Publication Publication Date Title
US10943418B2 (en) Method, server, smart terminal and storage device for access authentication
CN100583114C (en) System and method for remote security enablement
US11855984B2 (en) Method and system of providing secure access to a cloud service in a cloud computing environment
CN110121873A (en) A kind of access token management method, terminal and server
WO2016127417A1 (en) Leasing method, leasing system and leasing terminal for mobile power supply
CN103714273B (en) A kind of software authorization system and method based on online dynamic authorization
CN111526111B (en) Control method, device and equipment for logging in light application and computer storage medium
CN109637034B (en) Vehicle time-sharing leasing method and system based on virtual key
CN112566061B (en) Internet of vehicles data transmission method and system and vehicle service cloud
CN113542399B (en) Remote control method and device for vehicle, vehicle and storage medium
CN110930561B (en) Control method and device of intelligent lock
US20230336982A1 (en) Virtual key sharing system and method
US20140164258A1 (en) Mobile station apparatus and communication method thereof
CN110713084A (en) Visitor management method, device and system for elevator
CN113111339A (en) Access control method, device, equipment and medium for application service
US10973060B2 (en) Methods and systems for management of an association between a user and a vehicle
CN108011978A (en) A kind of method and system using mobile terminal APP control spliced display walls
CN106156549A (en) Application program authorization processing method and device
CN116305217A (en) Multi-tenant management method, device, computer equipment and storage medium
CN116405526A (en) Robot management method, electronic device, management system, and storage medium
JP2006309355A (en) Service system, and operating method for server device of the system
CN101364871B (en) Method, system and apparatus for domain manager to carry out domain management to user equipment
CN113660245B (en) Terminal access right control method, device, equipment and medium
JP7437567B2 (en) Apparatus and method for managing electric vehicle charging stations based on user location
US20230229994A1 (en) System, method, and program for controlling access to a machine or equipment

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