Method for automatic registration and connection of a robot to a server, robot, and server

Abstract

The present application provides a method for automatically registering and connecting a robot to a server, a robot, and a server, relating to the field of information processing technology. The method comprises: the robot sending a robot registration request message to a first server; the robot receiving a robot registration address sent by the first server, the robot registration address being the address of a second server determined based on a robot identifier; the robot sending robot registration information to the second server based on the robot registration address, the robot registration information including the robot identifier; the robot receiving a message server address sent by the second server, the second server establishing a connection with the message server upon startup; the robot establishing a connection with the message server corresponding to the message server address; and the robot establishing a connection with the second server via the message server, thereby achieving automatic robot registration and server connection, reducing the error rate of manual registration, and improving robot management efficiency.

Description

Technical Field

[0001] The present application relates to the field of information processing technology, and in particular to a method for a robot to automatically register and connect to a server, a robot, and a server. Background Art

[0002] With the rapid development of artificial intelligence technology, the robotics industry has developed rapidly in recent years, and has been widely used in different fields and has penetrated into all aspects of social life. As the number of robots increases, in order to facilitate the management of a large number of robots.

[0003] Currently, after a robot is sold, it is typically registered manually on a platform that manages the robot, such as a cloud platform or a server that provides robot management. This requires entering the robot's device ID and other information to complete the registration process. This allows the robot to be managed on the platform. However, manual registration is not only inefficient but also prone to errors, and robot manufacturers are unable to effectively manage robots after they are sold. Summary of the Invention

[0004] The embodiments of the present application provide a method, robot, and server for automatic robot registration and server connection, which can quickly realize automatic robot registration and server connection, reduce the error rate of manual registration, and improve robot management efficiency.

[0005] In a first aspect, the present application provides a method for automatic registration and connection of a robot to a server, comprising: the robot sends a robot registration request message to a first server, the first server being used to uniformly manage all robots leaving the factory; the robot receives a robot registration address sent by the first server, the robot registration address being the address of a second server determined based on a robot identifier, the second server being used to manage a certain type of robot; the robot sends robot registration information to the second server based on the robot registration address, the robot registration information including the robot identifier; the robot receives a message server address sent by the second server, the second server establishing a connection with the message server upon startup; the robot establishes a connection with the message server corresponding to the message server address; the robot establishes a connection with the second server through the message server.

[0006] In the embodiment of the present application, the robot automatically completes the registration of the robot on the second server by sending a robot registration request message to the first server, and sending the robot registration information to the second server according to the robot registration address sent by the first server, and receives the message server address sent by the second server, establishes a connection with the message server, and connects with the second server through the message server after the connection is established, so that the robot can establish a connection with the second server that directly manages the robot, realizes automatic registration and connection to the server, reduces the error rate of manual registration, and improves the efficiency of robot management.

[0007] The robot identification provided in this application includes a first identification and a second identification. The above-mentioned first identification is the software number of the above-mentioned robot, and the above-mentioned second identification is the number of the holder of the above-mentioned robot. The above-mentioned first identification and the above-mentioned second identification are bound to each of the above-mentioned second identifications. Each of the above-mentioned first identifications can only be bound to one of the above-mentioned second identifications; the above-mentioned first identification is included in the above-mentioned robot registration request information.

[0008] In an optional manner provided in the first aspect, the robot establishing a connection with the second server through the message server includes:

[0009] The robot verifies whether a connection is successfully established between the robot and the second server by publishing a message to the message server;

[0010] After verifying that the robot has successfully established a connection with the second server, the robot sends the online status of the robot to the second server.

[0011] In a second aspect, the present application provides another method for automatic robot registration and connection to a server, comprising: a first server receives robot registration request information sent by a robot, the first server being used to uniformly manage all robots leaving the factory, the robot registration request information including a first identifier, the first identifier being the software number of the robot; the first server searches for a second identifier bound to the first identifier based on the first identifier, the second identifier being the number of the holder of the robot; the first server determines a robot registration address based on the first identifier and / or the second identifier, the robot registration address being the address of the second server determined based on the first identifier and / or the second identifier, the second server being used to manage a certain type of robot; the first server sends the robot registration address to the robot, the robot registration address being used to instruct the robot to send robot registration information to the second server based on the robot registration address, and establish a connection with the second server.

[0012] The first server in the embodiment of the present application receives the robot registration request information sent by the robot, and searches for the second identifier bound to the above-mentioned first identifier based on the first identifier in the robot registration request information. Then, based on the above-mentioned first identifier and / or the above-mentioned second identifier, the robot registration address is determined and the robot registration address is sent to the robot, so that the robot can send the robot registration information to the second server according to the robot registration address and establish a connection with the second server, thereby realizing automatic registration and connection of the robot to the server, reducing the error rate of manual registration, and improving the efficiency of robot management.

[0013] In an optional manner provided in the second aspect, before the first server receives the robot registration request information sent by the robot, the method includes:

[0014] The first server obtains purchase information of the robot, wherein the purchase information includes the first identifier and robot owner information;

[0015] The first server creates the second identifier according to the robot owner information;

[0016] The first server binds the second identifier to the first identifier, and stores the binding relationship between the second identifier and the first identifier in an identifier binding table. Each second identifier is bound to at least one first identifier, and each first identifier can only be bound to one second identifier.

[0017] In another optional manner provided in the second aspect, after the first server binds the second identifier to the first identifier and stores the binding relationship between the second identifier and the first identifier in the identifier binding table, the method further includes:

[0018] The first server synchronously sends the first identifier and the second identifier to the second server.

[0019] In a third aspect, the present application provides a system for automatically registering and connecting a robot to a server, comprising:

[0020] A robot registration request information sending unit, configured to send a robot registration request information from the robot to a first server, wherein the first server is configured to uniformly manage all robots shipped from the factory;

[0021] a robot registration address receiving unit, configured to receive, by the robot, the robot registration address sent by the first server, wherein the robot registration address is the address of a second server determined based on the robot identifier, and the second server is configured to manage a certain type of robot;

[0022] a robot registration information sending unit, configured to send, by the robot, robot registration information to the second server according to the robot registration address, the robot registration information including the robot identifier;

[0023] A message server address receiving unit, configured to receive, by the robot, a message server address sent by the second server, wherein the second server establishes a connection with the message server when starting;

[0024] A first connection establishing unit, configured to establish a connection between the robot and the message server corresponding to the message server address;

[0025] The second connection establishing unit is used for the robot to establish a connection with the second server through the message server.

[0026] In an optional method provided in the third aspect, the above-mentioned robot identifier includes a first identifier and a second identifier, the above-mentioned first identifier is the software number of the above-mentioned robot, the above-mentioned second identifier is the number of the holder of the above-mentioned robot, the above-mentioned first identifier and the above-mentioned second identifier are bound to at least one above-mentioned first identifier, and each above-mentioned first identifier can only be bound to one above-mentioned second identifier; the above-mentioned robot registration request information includes the above-mentioned first identifier.

[0027] In another optional manner provided in the third aspect, the second connection establishing unit includes:

[0028] a connection verification subunit, configured to verify whether the robot has successfully established a connection with the second server by publishing a message to the message server;

[0029] The online status sending subunit is used for the robot to send the online status of the robot to the second server after verifying that the robot has successfully established a connection with the second server.

[0030] In a fourth aspect, the present application provides another system for automatically registering and connecting a robot to a server, comprising:

[0031] a robot registration request information receiving unit, configured to receive robot registration request information sent by a robot from a first server, the first server being configured to centrally manage all robots shipped from the factory, the robot registration request information including a first identifier, the first identifier being the software serial number of the robot;

[0032] A second identification search unit, configured to enable the first server to search for a second identification bound to the first identification based on the first identification, wherein the second identification is a serial number of the owner of the robot;

[0033] a robot registration address determining unit, configured to determine, by the first server, a robot registration address based on the first identifier and / or the second identifier, the robot registration address being an address of a second server determined based on the first identifier and / or the second identifier, the second server being configured to manage a certain type of robot;

[0034] The robot registration address sending unit is used to send the robot registration address to the robot from the first server. The robot registration address is used to instruct the robot to send robot registration information to the second server according to the robot registration address and establish a connection with the second server.

[0035] In an optional manner provided in the fourth aspect, the system further includes:

[0036] a purchase information acquisition unit, configured to acquire purchase information of the robot from the first server, the purchase information including the first identifier and robot owner information;

[0037] A second identification creation unit, configured to create the second identification by the first server according to the robot owner information;

[0038] The identifier binding unit is used for the first server to bind the second identifier with the first identifier, and store the binding relationship between the second identifier and the first identifier in the identifier binding table, each of the second identifiers is bound to at least one of the first identifiers, and each of the first identifiers can only be bound to one of the second identifiers.

[0039] In another optional manner provided in the fourth aspect, the system further includes:

[0040] The identification sending unit is used for the first server to synchronously send the first identification and the second identification to the second server.

[0041] In a fifth aspect, the present application provides a robot comprising a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method described in the first aspect or any optional method of the first aspect is implemented.

[0042] In the sixth aspect, the present application provides a server comprising a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method described in the second aspect or any optional method of the second aspect is implemented.

[0043] In the seventh aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method described in the first aspect or any optional method of the first aspect, or implements the method described in the second aspect or any optional method of the second aspect.

[0044] In an eighth aspect, an embodiment of the present application provides a computer program product, which, when running on a robot, enables the robot to execute the steps of the method for automatic robot registration and connection to the server in the first aspect or the second aspect.

[0045] It can be understood that the beneficial effects of the second to eighth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0047] Figure 1 This is a flowchart of a method for automatically registering and connecting a robot to a server provided in an embodiment of the present application;

[0048] Figure 2 This is a flowchart of a method for establishing a connection between a robot and a second server provided in an embodiment of the present application;

[0049] Figure 3 This is a flowchart of another method for automatically registering and connecting a robot to a server provided by an embodiment of the present application;

[0050] Figure 4 This is a flowchart of a method for binding a robot identifier provided in an embodiment of the present application;

[0051] Figure 5 This is a schematic diagram of the structure of a system for automatic robot registration and server connection provided by an embodiment of the present application;

[0052] Figure 6 This is a schematic diagram of the structure of another system for automatic robot registration and server connection provided by an embodiment of the present application;

[0053] Figure 7 This is a schematic structural diagram of a robot provided in an embodiment of the present application;

[0054] Figure 8This is a structural diagram of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, systems, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0056] It should be understood that the term "and / or" used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations. In addition, in the description of this specification and the appended claims, the terms "first," "second," "third," etc. are used only to distinguish descriptions and are not to be understood as indicating or implying relative importance.

[0057] It should also be understood that references to "one embodiment" or "some embodiments" in the present specification mean that one or more embodiments of the present application include a particular feature, structure, or characteristic described in conjunction with that embodiment. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0058] Before describing the method for automatic robot registration and server connection provided by the embodiment of the present application, the robot, first server, second server, and message server involved in the embodiment of the present application are described as follows:

[0059] The robots in the embodiments of the present application include but are not limited to detection robots, cleaning robots, industrial robots, disinfection robots, military intelligent robots, civilian intelligent machines, etc.

[0060] The first server in the embodiment of the present application is a platform for unified management of all robots shipped by robot manufacturers, also known as a company-level background management system, which uniformly manages different types of machines produced by robot manufacturers.

[0061] The second server in the embodiment of the present application is a platform for managing a certain type of robot, also known as the robot's backend management system, which can be developed for customers so that customers can understand the robot's status information through the second server.

[0062] The message server in the embodiment of the present application is a communication middleware that connects the robot and the second server. The robot and the second server publish and receive messages through the message server. The message server in the embodiment of the present application is preferably an MQTT message server. Other communication middleware that can connect the robot and the second server can also be used as the message server in the embodiment of the present application.

[0063] After the robot in the embodiment of the present application is purchased, the owner of the robot, that is, the enterprise or individual that purchases the robot, needs to perform a registration operation on the robot and register it with the second server that directly manages the robot. In order to facilitate the unified management of all robots by the robot manufacturer and improve the management efficiency of all robots by the robot manufacturer, the robot registration address where the robot registers with the second server is stored on the first server, so that the first server can effectively manage the robots shipped by the robot manufacturer and improve the management efficiency of the robots.

[0064] The following describes in detail the method for automatic robot registration and server connection provided by this application in conjunction with specific embodiments.

[0065] Example 1

[0066] See Figure 1 , Figure 1 This is a flowchart of a method for automatically registering and connecting to a server for a robot provided in an embodiment of the present application, which is described in detail as follows:

[0067] Step S101: The robot sends a robot registration request message to the first server.

[0068] In an embodiment of the present application, for each robot produced by the robot manufacturer, a software number generation tool is used to generate a unique software number for each robot as an identification of the robot, and the software number is stored in the first server so that the first server can find the corresponding robot according to the software number and effectively manage the robot.

[0069] After the robot is purchased, the owner of the robot performs a registration operation on the robot. The robot obtains a first identifier, that is, the software number of the robot, generates robot registration request information, and sends the robot registration request information to the first server.

[0070] Step S102: The robot receives the robot registration address sent by the first server. The robot registration address is the address of the second server determined based on the robot identifier.

[0071] In an embodiment of the present application, the robot identifier includes a first identifier and a second identifier, the first identifier is the software number of the robot, the second identifier is the number of the holder of the robot, the first identifier and the second identifier are bound to each other, and each of the second identifiers is bound to at least one of the first identifiers, and each of the first identifiers can only be bound to one of the second identifiers.

[0072] In some embodiments of the present application, after the robot sends a robot registration request message to the first server, the first server, after receiving the robot registration request message, searches the identifier binding table for the second identifier bound to the first identifier based on the first identifier in the robot registration request message, and then determines the robot registration address based on the first identifier and / or the second identifier, and then feeds back the determined robot registration address to the robot.

[0073] In the embodiments of the present application, the second identifier is the robot owner's serial number. After selling a robot, the robot manufacturer uploads the robot's purchase information to the first server. The first server then creates a second identifier based on the purchaser's information, which is also the robot owner's serial number. After creating the second identifier, the first server binds it to the first identifier. Since each buyer purchases at least one robot, to ensure the uniqueness of each buyer, each second identifier must be bound to at least one first identifier, and each first identifier can only be bound to one second identifier.

[0074] In the embodiment of the present application, the first identifier and the second identifier of the robot are both unique. The robot registration address can be determined through the first identifier. Since the second identifier is bound to the first identifier, the robot registration address can actually also be determined through the second identifier. Therefore, the first server can determine the robot registration address through the first identifier and / or the second identifier.

[0075] It should be noted that since the second identifier is the identifier of the robot holder, in order to better provide the robot holder with a robot management server, the robot registration address is generally determined by the second identifier so that the server corresponding to the robot registration address can be developed for the robot holder to use.

[0076] Step S103: The robot sends robot registration information to the second server according to the robot registration address.

[0077] In this embodiment of the present application, the robot registration information includes the aforementioned robot identifier. After receiving the robot registration address from the first server, the robot, because the robot registration address actually includes the first identifier and the second identifier, applies to the second server for registration based on the robot registration address. The robot then sends the robot registration information including the robot identifier to the second server to complete the robot registration on the second server.

[0078] Step S104: the robot receives the message server address sent by the second server.

[0079] In an embodiment of the present application, after the robot completes registration on the second server, the second server sends the address of the message server to which it is connected to the robot. The robot receives the message server address sent by the second server so as to establish a connection with the corresponding message server according to the message server address.

[0080] The message server in the embodiment of the present application establishes a connection with the second server when it is started. Generally, the message server, as the communication terminal of the second server, can be a communication device set on the second server, or a separate communication device set on another server, which is not specifically limited here.

[0081] Step S105: The robot establishes a connection with the message server corresponding to the message server address.

[0082] In an embodiment of the present application, after receiving the message server address sent by the second service area, the robot establishes a connection with the corresponding message server through the message server address. At this time, if the robot is online, it can push and publish information with the second server through the message server.

[0083] Step S106: The robot establishes a connection with the second server through the message server.

[0084] In an embodiment of the present application, the robot can establish a connection with the second server through the message server. Before the robot pushes information to the second server, it is also necessary to verify whether the second server and the robot are online at the same time. When the second server and the robot are online at the same time, the robot's online status can be displayed on the second server, and messages can be pushed to the robot through the second server, such as issuing instructions, etc. At this point, the robot automatically registers and connects to the server.

[0085] See Figure 2 , Figure 2 : This is a flowchart of a method for establishing a connection between a robot and a second server provided in an embodiment of the present application, which is described in detail as follows:

[0086] In step S201, the robot verifies whether a connection is successfully established between the robot and the second server by publishing a message to the message server.

[0087] In an embodiment of the present application, after the robot is successfully registered, the robot publishes a message to the message server to verify whether the robot has successfully established a connection with the server.

[0088] Step S202: After verifying that the robot has successfully established a connection with the second server, the robot sends the online status of the robot to the second server.

[0089] In an embodiment of the present application, after the robot publishes a message to the message server, the message server pushes the message to the second server. After the second server receives the message, it replies to the message through the message server. After receiving the reply message, the robot determines that the robot is successfully connected to the second server and displays the robot's online status on the second server.

[0090] In an embodiment of the present application, the robot automatically completes the registration of the robot on the second server by sending a robot registration request message to the first server and sending the robot registration information to the second server according to the robot registration address sent by the first server, and receives the message server address sent by the second server, establishes a connection with the message server, and connects with the second server through the message server after the connection is established, so that the robot can establish a connection with the second server that directly manages the robot, realizes automatic registration and connection to the server, reduces the error rate of manual registration, and improves the efficiency of robot management.

[0091] Example 2

[0092] See Figure 3 , Figure 3 This is a flowchart of another method for automatically registering and connecting to a server for a robot provided in an embodiment of the present application, which is described in detail as follows:

[0093] Step S301: The first server receives robot registration request information sent by the robot.

[0094] In an embodiment of the present application, after the robot is sold, the first server obtains the purchase information of the robot so as to assign a robot registration address to the robot according to the purchase information of the robot, so that the owner of the robot can manage the robot on the corresponding platform, such as the second server.

[0095] In order to facilitate the allocation of a robot registration address for the robot, after the robot is sold, the first server needs to complete the binding between the robot and the robot holder.

[0096] For details, see Figure 4 , Figure 4 This is a flowchart of a method for binding a robot identifier provided in an embodiment of the present application, which is described in detail as follows:

[0097] Step S401: The first server obtains purchase information of the robot, where the purchase information includes the first identifier and robot owner information.

[0098] Step S402: The first server creates the second identifier according to the robot owner information.

[0099] In step S403, the first server binds the second identifier to the first identifier, and stores the binding relationship between the second identifier and the first identifier in an identifier binding table.

[0100] In an embodiment of the present application, by binding the second identifier and the first identifier, it is possible to facilitate group management of the robot holders, so that different subscription topics can be pushed to the robot through the second server, solving the problem that different service topics cannot be provided to the holders of different robots quickly and effectively due to the different subscription topics of the holders of different robots, thereby improving the management efficiency of the robot.

[0101] In some embodiments of the present application, the first server simultaneously sends the first identifier and the second identifier to the second server, so that the second server can provide the robot with a corresponding robot registration address based on the first identifier and / or the second identifier.

[0102] Step S302: The first server searches for a second identifier bound to the first identifier based on the first identifier.

[0103] Step S303: The first server determines the robot registration address according to the first identifier and / or the second identifier.

[0104] The robot registration address in the embodiment of the present application is the address of the second server determined based on the robot identifier, that is, the first identifier and / or the second identifier.

[0105] In step S304, the first server sends the robot registration address to the robot. The robot registration address is used to instruct the robot to send robot registration information to the second server according to the robot registration address and establish a connection with the second server.

[0106] In an embodiment of the present application, the first server receives the robot registration request information sent by the robot, and searches for the second identifier bound to the above-mentioned first identifier based on the first identifier in the robot registration request information. Then, based on the above-mentioned first identifier and / or the above-mentioned second identifier, the robot registration address is determined and the robot registration address is sent to the robot, so that the robot can send the robot registration information to the second server according to the robot registration address and establish a connection with the second server, thereby realizing automatic registration and connection of the robot to the server, reducing the error rate of manual registration, and improving the efficiency of robot management.

[0107] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0108] Example 3

[0109] Based on the method for automatic robot registration and server connection provided in the first embodiment above, the embodiment of the present application further provides a system embodiment for implementing the above method embodiment.

[0110] See Figure 5 , Figure 5 This is a schematic diagram of a system for automatically registering and connecting to a server provided by an embodiment of the present application. The units included are used to execute Figure 1 Each step in the corresponding embodiment. Please refer to Figure 1 For the convenience of explanation, only the parts related to this embodiment are shown. Figure 5 , the system 5 for the robot to automatically register and connect to the server includes:

[0111] A robot registration request information sending unit 51 is configured to send a robot registration request information to a first server, where the first server is configured to centrally manage all robots shipped from the factory.

[0112] a robot registration address receiving unit 52, configured to receive, by the robot, the robot registration address sent by the first server, wherein the robot registration address is the address of a second server determined based on the robot identifier, and the second server is configured to manage a certain type of robot;

[0113] a robot registration information sending unit 53, configured to send robot registration information including the robot identifier to the second server according to the robot registration address;

[0114] A message server address receiving unit 54 is configured to receive, by the robot, the message server address sent by the second server, and the second server establishes a connection with the message server when it is started;

[0115] A first connection establishing unit 55 is configured to establish a connection between the robot and the message server corresponding to the message server address;

[0116] The second connection establishing unit 56 is configured to enable the robot to establish a connection with the second server via the message server.

[0117] The robot identifier in the embodiment of the present application includes a first identifier and a second identifier. The first identifier is the software number of the robot, and the second identifier is the number of the holder of the robot. There is a binding relationship between the first identifier and the second identifier. Each of the second identifiers is bound to at least one of the first identifiers, and each of the first identifiers can only be bound to one of the second identifiers. The robot registration request information includes the first identifier.

[0118] In some embodiments of the present application, the second connection establishing unit 56 includes:

[0119] a connection verification subunit, configured to verify whether the robot has successfully established a connection with the second server by publishing a message to the message server;

[0120] The online status sending subunit is used for the robot to send the online status of the robot to the second server after verifying that the robot has successfully established a connection with the second server.

[0121] Example 4

[0122] Based on the method for automatic robot registration and server connection provided in the second embodiment above, this embodiment of the present application further provides a system embodiment for implementing the above method embodiment.

[0123] See Figure 6 , Figure 6 This is a schematic diagram of another system for automatically registering and connecting to a server provided by an embodiment of the present application. The units included are used to execute Figure 3 Each step in the corresponding embodiment. Please refer to Figure 3 For the convenience of explanation, only the parts related to this embodiment are shown. Figure 6 , the system 6 for the robot to automatically register and connect to the server includes:

[0124] a robot registration request information receiving unit 61, configured to receive robot registration request information sent by a robot from a first server, the first server being configured to centrally manage all robots shipped from the factory, the robot registration request information including a first identifier, which is the software serial number of the robot;

[0125] A second identification search unit 62 is configured to search, by the first server, for a second identification bound to the first identification based on the first identification, where the second identification is the number of the owner of the robot;

[0126] a robot registration address determining unit 63, configured to determine, by the first server, a robot registration address based on the first identifier and / or the second identifier, wherein the robot registration address is an address of a second server determined based on the first identifier and / or the second identifier, and the second server is configured to manage a certain type of robot;

[0127] The robot registration address sending unit 64 is used to send the robot registration address to the robot from the first server. The robot registration address is used to instruct the robot to send robot registration information to the second server according to the robot registration address and establish a connection with the second server.

[0128] In some embodiments of the present application, the system further includes:

[0129] a purchase information acquisition unit, configured to acquire purchase information of the robot from the first server, the purchase information including the first identifier and robot owner information;

[0130] A second identification creation unit, configured to create the second identification by the first server according to the robot owner information;

[0131] The identifier binding unit is used for the first server to bind the second identifier with the first identifier, and store the binding relationship between the second identifier and the first identifier in the identifier binding table, each of the second identifiers is bound to at least one of the first identifiers, and each of the first identifiers can only be bound to one of the second identifiers.

[0132] In some other embodiments of the present application, the system further includes:

[0133] The identifier sending unit is used for the first server to synchronously send the first identifier and the second identifier to the second server.

[0134] It should be noted that the information interaction, execution process and other contents between the above modules are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0135] Figure 7 Schematic diagram of the robot provided in the embodiment of the present application. Figure 7 As shown, the robot 7 of this embodiment includes: a processor 70, a memory 71, and a computer program 72 stored in the memory 71 and executable on the processor 70, such as a program for the robot to automatically register and connect to a server. When the processor 70 executes the computer program 72, the steps in the above-mentioned method embodiments of the robot automatically registering and connecting to a server are implemented, such as Figure 1 Alternatively, when the processor 70 executes the computer program 72, the functions of each module / unit in the above-mentioned system embodiments are realized, for example Figure 5 The functions of units 51-56 are shown.

[0136] Exemplarily, the computer program 72 can be divided into one or more modules / units, one or more modules / units are stored in the memory 71 and executed by the processor 70 to complete the present application. One or more modules / units can be a series of computer program instruction segments that can complete specific functions, and the instruction segments are used to describe the execution process of the computer program 72 in the robot 7. For example, the computer program 72 can be divided into a robot registration request information sending unit 51, a robot registration address receiving unit 52, a robot registration information sending unit 53, a message server address receiving unit 54, a first connection establishing unit 55, and a second connection establishing unit 56. For the specific functions of each unit, please refer to Figure 1 The relevant descriptions in the corresponding embodiments are not repeated here.

[0137] The robot may include, but is not limited to, a processor 70 and a memory 71. It will be understood by those skilled in the art that Figure 7 This is only an example of the robot 7 and does not constitute a limitation of the robot 7. The robot may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the robot may also include input and output devices, network access devices, buses, etc.

[0138] The processor 70 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0139] Memory 71 can be an internal storage unit of robot 7, such as the robot's hard drive or memory. Memory 71 can also be an external storage device of robot 7, such as a plug-in hard drive, a SmartMedia Card (SMC), a Secure Digital (SD) card, a flash memory card, etc. Furthermore, memory 71 can include both the robot's internal storage unit and an external storage device. Memory 71 is used to store computer programs and other programs and data required by the robot. Memory 71 can also be used to temporarily store data that has been output or is about to be output.

[0140] Figure 8 Schematic diagram of the server provided in the embodiment of the present application. Figure 8 As shown, the server 8 of this embodiment includes: a processor 80, a memory 81, and a computer program 82 stored in the memory 81 and executable on the processor 80, such as a program for automatic server registration and server connection. When the processor 80 executes the computer program 82, the steps in the above-mentioned embodiments of the method for automatic server registration and server connection are implemented, such as Figure 3 Alternatively, when the processor 80 executes the computer program 82, the functions of each module / unit in the above-mentioned system embodiments are realized, for example Figure 6 The functions of units 61-64 are shown.

[0141] Exemplarily, the computer program 82 can be divided into one or more modules / units, one or more modules / units are stored in the memory 81 and executed by the processor 80 to complete the present application. One or more modules / units can be a series of computer program instruction segments that can complete specific functions, and the instruction segments are used to describe the execution process of the computer program 82 in the server 8. For example, the computer program 82 can be divided into a robot registration request information receiving unit 61, a second identification search unit 62, a robot registration address determination unit 63, and a robot registration address sending unit 64. For the specific functions of each unit, please refer to Figure 1 The relevant descriptions in the corresponding embodiments are not repeated here.

[0142] The server may include, but is not limited to, a processor 80 and a memory 81. Those skilled in the art will appreciate that Figure 8 This is only an example of the server 8 and does not constitute a limitation on the server 8. The server 8 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the server may also include input and output devices, network access devices, buses, etc.

[0143] The processor 80 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0144] Memory 81 can be an internal storage unit of server 8, such as the server's hard drive or memory. Memory 81 can also be an external storage device of server 8, such as a plug-in hard drive, a SmartMedia Card (SMC), a Secure Digital (SD) card, a flash memory card, etc. Furthermore, memory 81 can include both an internal storage unit of server 8 and an external storage device. Memory 81 is used to store computer programs and other programs and data required by the server. Memory 81 can also be used to temporarily store data that has been output or is about to be output.

[0145] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the above-mentioned method of automatic robot registration and connection to the server.

[0146] An embodiment of the present application provides a computer program product, which, when executed on a robot or a server, enables the robot to implement the above-mentioned method of automatic robot registration and server connection.

[0147] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0148] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0149] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0150] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A method for a robot to automatically register and connect to a server, characterized in that: The method comprises: The robot sends a robot registration request message to the first server, which is used to centrally manage all robots shipped from the factory; The robot receives a robot registration address sent by the first server, where the robot registration address is an address of a second server determined based on the robot identifier, and the second server is used to manage a certain type of robot; The robot sends robot registration information to the second server according to the robot registration address, where the robot registration information includes the robot identifier; The robot receives the message server address sent by the second server, and the second server establishes a connection with the message server when it is started; The robot establishes a connection with the message server corresponding to the message server address; The robot establishes a connection with the second server through the message server; Among them, the robot identifier includes a first identifier and a second identifier, the first identifier is the software number of the robot, the second identifier is the number of the holder of the robot, the first identifier and the second identifier are bound to each other, each second identifier is bound to at least one first identifier, and each first identifier can only be bound to one second identifier; the robot registration request information includes the first identifier.

2. The method for automatic robot registration and server connection according to claim 1, wherein: The robot establishes a connection with the second server through the message server, including: The robot verifies whether a connection is successfully established between the robot and the second server by publishing a message to the message server; After verifying that the robot is successfully connected to the second server, the robot sends the online status of the robot to the second server.

3. A method for a robot to automatically register and connect to a server, characterized in that: The method comprises: A first server receives robot registration request information sent by a robot, the first server being used to uniformly manage all robots shipped from the factory, the robot registration request information including a first identifier, which is the software number of the robot; The first server searches for a second identifier bound to the first identifier based on the first identifier, where the second identifier is a serial number of the owner of the robot; The first server determines a robot registration address based on the first identifier and / or the second identifier, where the robot registration address is an address of a second server determined based on the first identifier and / or the second identifier, and the second server is used to manage a certain type of robot; The first server sends the robot registration address to the robot, where the robot registration address is used to instruct the robot to send robot registration information to the second server according to the robot registration address and establish a connection with the second server; Before the first server receives the robot registration request information sent by the robot, it includes: The first server obtains purchase information of the robot, where the purchase information includes the first identifier and robot owner information; The first server creates the second identifier according to the robot holder information; The first server binds the second identifier to the first identifier, and stores the binding relationship between the second identifier and the first identifier in an identifier binding table. Each second identifier is bound to at least one first identifier, and each first identifier can only be bound to one second identifier.

4. A system for automatic robot registration and server connection, characterized in that: The system comprises: a robot registration request information sending unit, configured to send the robot registration request information to a first server by the robot, wherein the first server is configured to uniformly manage all robots shipped from the factory; a robot registration address receiving unit, configured to receive, by the robot, a robot registration address sent by the first server, wherein the robot registration address is an address of a second server determined based on the robot identifier, and the second server is configured to manage a certain type of robot; a robot registration information sending unit, configured to send, by the robot, robot registration information to the second server according to the robot registration address, the robot registration information including the robot identifier; a message server address receiving unit, configured to receive, by the robot, a message server address sent by the second server, wherein the second server establishes a connection with the message server when starting; A first connection establishing unit, configured to establish a connection between the robot and the message server corresponding to the message server address; A second connection establishing unit, configured for the robot to establish a connection with the second server via the message server; Among them, the robot identifier includes a first identifier and a second identifier, the first identifier is the software number of the robot, the second identifier is the number of the holder of the robot, the first identifier and the second identifier are bound to each other, each second identifier is bound to at least one first identifier, and each first identifier can only be bound to one second identifier; the robot registration request information includes the first identifier.

5. A system for automatic robot registration and server connection, characterized in that: The system comprises: a robot registration request information receiving unit, configured to receive robot registration request information sent by a robot from a first server, the first server being configured to uniformly manage all robots shipped from the factory, the robot registration request information including a first identifier, the first identifier being the software number of the robot; a second identification search unit, configured to enable the first server to search, based on the first identification, for a second identification bound to the first identification, where the second identification is a serial number of the owner of the robot; a robot registration address determining unit, configured to determine, by the first server, a robot registration address based on the first identifier and / or the second identifier, the robot registration address being an address of a second server determined based on the first identifier and / or the second identifier, the second server being configured to manage a certain type of robot; a robot registration address sending unit, configured to send the robot registration address from the first server to the robot, wherein the robot registration address is used to instruct the robot to send robot registration information to the second server according to the robot registration address and establish a connection with the second server; a purchase information acquiring unit, configured to acquire, from the first server, purchase information of the robot, the purchase information including the first identifier and robot owner information; A second identification creating unit, configured to create the second identification by the first server according to the robot holder information; An identifier binding unit is used for the first server to bind the second identifier with the first identifier, and store the binding relationship between the second identifier and the first identifier in an identifier binding table, each second identifier is bound to at least one first identifier, and each first identifier can only be bound to one second identifier.

6. A robot comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method for automatic robot registration and server connection according to any one of claims 1 to 2 is implemented.

7. A server comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method for automatic robot registration and server connection according to claim 3 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method for automatic robot registration and server connection according to any one of claims 1 to 3 is implemented.

Images