Method, apparatus and medium for determining identification of robot

Abstract

The application discloses a kind of identification determination method of robot, comprising: according to the registration request of target robot, the equipment identification information of the target robot is determined;According to the equipment identification information, the current registration state of the target robot in current data center is determined, and the other registration state of the target robot in other data center is selectively determined;According to the current registration state, and / or, the other registration state, the identity identification information of the target robot is determined.The application realizes the effect of guaranteeing the identity identification information of robot has uniformity.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of robots, and in particular to a robot identification determination method, device, equipment and medium. BACKGROUND

[0002] With the development of robot technology, robots are increasingly widely used, and can be applied in multiple regions of a country or even multiple countries worldwide. Robot managers, such as robot manufacturers or large robot using enterprises, have a demand for unified management of robots. Different regions may have different requirements for the security compliance of robot data. In order to adapt to the security compliance requirements of different regions and meet the demand for managing robots, data centers can be established in each region. A robot can be legally used in a corresponding region only after it is registered in a data center.

[0003] In the robot registration process of the prior art, if a data center determines that a robot has not been registered locally, the data center generates exclusive identity information for the robot. However, there may be a case where a robot has been registered in other data centers, for example, a trial robot may be used in different regions in sequence. If a robot is registered in multiple data centers, multiple identity information of the robot will be generated, and the problem of non-uniformity of the identity information of the robot will occur. SUMMARY

[0004] The present application provides a robot identification determination method, device, equipment and medium to solve the problem of non-uniformity of the identity information of a robot caused by registration of the robot in multiple data centers in the prior art.

[0005] According to an aspect of the present application, a robot identification determination method is provided, comprising:

[0006] determining device identification information of a target robot according to a registration request of the target robot;

[0007] determining a current registration state of the target robot in a current data center and selectively determining other registration states of the target robot in other data centers according to the device identification information;

[0008] determining identity information of the robot according to the current registration state and / or the other registration states.

[0009] According to another aspect of the present application, a robot identification determination device is provided, comprising:

[0010] An identity information determination module is configured to determine device identification information of a target robot according to a registration request of the target robot;

[0011] a registration state determination module configured to determine a current registration state of the target robot in the current data center according to the device identification information, and selectively determine other registration states of the target robot in other data centers;

[0012] an identification information determination module configured to determine the identity identification information of the robot according to the current registration state, and / or the other registration states.

[0013] According to another aspect of the present application, an electronic device is provided, which comprises:

[0014] at least one processor; and

[0015] a memory connected to the at least one processor in communication; wherein,

[0016] the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to perform the robot identity determination method according to any one of the embodiments of the present application.

[0017] According to another aspect of the present application, a computer readable storage medium is provided, which stores computer instructions for enabling a processor to perform the robot identity determination method according to any one of the embodiments of the present application when executed by the processor.

[0018] The technical solution of the embodiments of the present application can accurately determine whether a target robot is registered according to the current registration state of the robot in the current data center and selectively obtain other registration states of the robot in other data centers, and further determine the identity identification information of the robot, thereby achieving the effect of ensuring the uniformity of the identity identification information of the robot, and avoiding the problem that the identity identification information of the robot is not uniform when the identity identification information of the robot is generated only according to the current registration state of the robot in the current data center.

[0019] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced as follows. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0021] Figure 1 A flow chart of a robot identification determining method is provided for the first embodiment of the present application;

[0022] Figure 2A A flow chart of a robot identification determining method is provided for the second embodiment of the present application;

[0023] Figure 2B A flow chart of a robot registration is provided for the second embodiment of the present application;

[0024] Figure 3 A structural schematic diagram of a robot identification determining device is provided for the third embodiment of the present application;

[0025] Figure 4 A structural schematic diagram of an electronic device implementing the robot identification determining method of the present application is provided. DETAILED DESCRIPTION

[0026] In order to make the personnel in the technical field better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all the other embodiments obtained by the personnel in the field without creative labor should belong to the protection scope of the present application.

[0027] It should be noted that the terms “current”, “other”, “history”, “first” and “second” and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms “include” and “have” and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily limit to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0028] In the robot registration process of the prior art, if the data center determines that the robot has not been registered locally, the data center generates a unique identity information for the robot, and in the data center, the identity information will be used to bind the robot data generated by the robot in the future.

[0029] However, if the robot registers in multiple data centers, multiple identity information will be generated, resulting in the problem of inconsistent identity information of the robot, and further resulting in the problem of difficulty in managing the robot data stored in each data center.

[0030] For example, it is assumed that the robot registers in data center A, and data center A generates identity information A for the robot. The robot data generated subsequently by the robot is stored in data center A in association with the identity information A. The robot also registers in data center B, and data center B generates new identity information B for the robot. The robot data generated subsequently by the robot is stored in data center B in association with the identity information B.

[0031] If the user requires the robot data stored in data center A to be migrated to data center B at this time, the robot data stored in the two data centers cannot be combined due to the difference between the identity information A and the identity information B.

[0032] Embodiment one

[0033] Figure 1 A flowchart of a robot identification determination method is provided for the first embodiment of the application. The present embodiment can be applied to avoid the situation that multiple different identity information is registered for the robot by the data center. The method can be executed by a robot identification determination device. The robot identification determination device can be realized in the form of hardware and / or software. The robot identification determination device can be configured in the data center. The data center can be used to register, manage and control the robot, and store and maintain the robot data of the registered robot, etc. The type of the data center can be a server, etc. As shown in the figure, the method comprises the following steps. Figure 1

[0034] S101, determining the device identity information of the target robot according to the registration request of the target robot.

[0035] The target robot refers to the robot that applies for registration to the current data center. The number of target robots can be one or multiple. The type of the target robot includes but is not limited to industrial robot, delivery robot, cleaning robot, disinfection robot, medical robot, etc. The device identity information refers to the identity information corresponding to the target robot uniquely. The type of the device identity information includes but is not limited to SN (Serial Number), device number, machine code or hardware identification code, etc. The device identity information is determined uniquely when the robot is manufactured.

[0036] ​In an embodiment, the target robot periodically determines the current position information of the target robot according to a positioning device carried by the target robot, such as a GPS (Global Positioning System), and determines the current data center associated with the position region to which the current position information belongs according to the pre-stored association relationship between the position region and the data center, so as to better manage the use of the robot across regions or changes in regions. Further, it is queried in the historical registration record whether the current data center has been applied for registration, and if not, a registration request carrying device identification information is generated and sent to the current data center through a communication connection between the target robot and the current data center, such as a wireless network connection, a Bluetooth connection, or a WiFi (Wireless Fidelity) connection.

[0037] In another embodiment, if the target robot cannot obtain its own identity information each time it is started, the target robot automatically sends a registration request to the current data center.

[0038] The current data center receives the registration request sent by the target robot and parses the registration request to obtain the device identification information of the target robot carried in the registration request.

[0039] By determining the device identification information of the target robot according to the registration request of the target robot, a data foundation is laid for subsequent determination of the current registration state and / or other registration states based on the device identification information.

[0040] S102, determining the current registration state of the target robot in the current data center according to the device identification information, and selectively determining other registration states of the target robot in other data centers.

[0041] Among them, the other data center represents all data centers except the current data center.

[0042] The current registration state includes a registered state and an unregistered state, and if the current registration state is the registered state, it indicates that the target robot has completed registration in the current data center at a historical time; if the current registration state is the unregistered state, it indicates that the target robot has not completed registration in the current data center.

[0043] The other registration state also includes a registered state and an unregistered state, and if the other registration state is the registered state, it indicates that the target robot has completed registration in the other data center at a historical time; if the other registration state is the unregistered state, it indicates that the target robot has not completed registration in the other data center.

[0044] In an embodiment, the current data center obtains the device identification information of the registered robot from the historical registration record, and searches the device identification information of the target robot as a keyword in the device identification information of the registered robot, and then determines the current registration state of the target robot in the current data center according to the search matching result.

[0045] In an embodiment, if the current registration state of the target robot in the current data center is an unregistered state, the current data center generates a registration state determination request carrying the device identification information of the target robot, and sends the registration state determination request to each other data center through the communication connection between the current data center and each other data center.

[0046] After receiving the registration state determination request, the other data center parses the registration state determination request to obtain the device identification information of the target robot, and obtains the device identification information of the registered robot from the historical registration record of the other data center, and then searches the device identification information of the target robot as a keyword in the device identification information of the registered robot in the other data center, and then determines the other registration state of the target robot in the other data center according to the search matching result. Finally, the other data center sends the determined other registration state to the current data center through the communication connection between the current data center and the other data center.

[0047] In another embodiment, the current data center backs up the registration records of the other data centers, and if the current registration state of the target robot in the current data center is an unregistered state, the registration records of the other data centers are queried to determine the registration state of the target robot in the other data centers. The registration records of the other data centers can be distributed to the current data center by the bus in the form of a global registration record snapshot. Backing up the registration records of the other data centers locally can reduce the communication query occupation of the communication bandwidth and processing of each data center, and is especially suitable for scenarios with a large number of data centers and a large number of robots. Optionally, the registration records of each data center are synchronized to a global data center, and then distributed synchronously after integration by the global data center. Specifically, an incremental synchronization mode can be used to reduce data transmission.

[0048] By determining the current registration state of the target robot in the current data center according to the device identification information, and selectively determining the other registration state of the target robot in the other data centers, unnecessary acquisition of the other registration state when the current registration state is a registered state is avoided, and the efficiency of the entire registration state determination process is improved.

[0049] S103, determining the identity information of the target robot according to the current registration state and / or the other registration state.

[0050] The identity information embodies the uniqueness of the target robot identity, such as a robot ID (Identity document) and the like. It can be understood that the device identification information can uniquely determine the corresponding robot, but is determined at the factory, and itself has disorder, chaos and difficulty in identification. The device identification information format and content of different manufacturers are more diverse. Therefore, the identity information can be re-encoded according to a predetermined rule to uniquely encode the robot, facilitating the management of the robot and its data.

[0051] In an embodiment, if the current registration state of the target robot in the current data center is a registered state, the current data center obtains the registered identity information of the target robot in the historical registration record, and generates a registration rejection instruction carrying the registered identity information, and then sends the registration rejection instruction to the target robot, to inform the target robot that it has completed registration in the current data center, and the assigned identity information is the registered identity information.

[0052] In another embodiment, if the current registration state of the target robot in the current data center is an unregistered state, and the other registration state of the target robot in other data centers is also an unregistered state, the current data center registers the target robot, and generates identity information for the target robot. Optionally, the way of generating the identity information includes but is not limited to: performing a hash calculation on the device identification information of the target robot, and taking the obtained hash value as the identity information. For example, the identity information can be generated according to a predetermined encoding rule, such as registration year-registration region code-registration sequence number.

[0053] In another embodiment, if the current registration state of the target robot in the current data center is an unregistered state, but the other registration state of the target robot in any other data center is a registered state, the current data center sends a request to the other data center, to obtain the registered identity information of the target robot from the other data center. Alternatively, the registered identity information of the target robot is obtained from the registration record of the other data center stored in the current data center. The current data center further registers the target robot, and issues the registered identity information to the target robot, to facilitate the subsequent communication between the target robot and the current data center.

[0054] The technical scheme of the embodiment of the present application can selectively acquire other registration states of the robot in other data centers according to the current registration state of the robot in the current data center, and jointly determine the identity information of the robot, thereby achieving the effect of ensuring the identity information of the robot to be uniform, avoiding the problem that the identity information of the robot is not uniform due to the generation of the identity information of the robot according to only the current registration state of the robot in the current data center; and further ensuring that the robot data of the same robot between different data centers can be successfully merged.

[0055] Embodiment two

[0056] Figure 2A A flowchart of a robot identification determination method provided by the second embodiment of the present application, the present embodiment further optimizes and extends the above-mentioned first embodiment, and can be combined with the above-mentioned various optional embodiments. As shown in the figure, the method comprises: Figure 2A

[0057] S201, determining the device identity information of the target robot according to the registration request of the target robot.

[0058] S202, acquiring the first registered identity information stored locally in the current data center, matching the device identity information with the first registered identity information, and determining the current registration state of the target robot in the current data center according to the matching result.

[0059] Among them, the first registered identity information is the identity information of the registered robot in the current data center.

[0060] In an embodiment, the current data center acquires the first registered identity information from the historical registration records stored locally, and respectively matches the device identity information with each first registered identity information.

[0061] If any first registered identity information matches the device identity information of the target device, it is determined that the current registration state of the target robot in the current data center is a registered state. If any first registered identity information does not match the device identity information of the target device, it is determined that the current registration state of the target robot in the current data center is an unregistered state.

[0062] S203, in the case where the current registration state is an unregistered state, determining the other registration state of the target robot in other data centers according to the device identity information.

[0063] ​In an implementation, when the current registration state is the unregistered state, the current data center acquires second registered identification information of the robot registered in other data centers, and determines the other registration state of the target robot in the other data centers according to the second registered identification information and the device identification information of the target robot.

[0064] By determining the other registration state of the target robot in the other data centers according to the device identification information when the current registration state is the unregistered state, since the data amount of the first registered identification information is far less than that of the second registered identification information, by first matching the device identification information with the first registered identification information, if it is determined that the current registration state is the unregistered state, the other registration state is determined according to the device identification information and the second registered identification information, the useless determination of the other registration state when the current registration state is the registered state is avoided, the data processing amount of the entire registration state determination process is reduced, and the efficiency of the entire registration state determination process is improved.

[0065] Optionally, S203 comprises:

[0066] The second registered identification information is acquired, which is locally stored in the current data center, and is collected from other data centers by the bus server and distributed to the current data center for local storage; the device identification information is matched with the second registered identification information, and the other registration state of the target robot in the other data centers is determined according to the matching result.

[0067] The bus server can also be referred to as a global data center, which is in communication connection with each data center, and whenever any data center generates the identity identification information of any robot, the bus server will distribute the device identification information of the robot as the second registered identification information to other data centers except the data center for local storage together with the identity identification information.

[0068] In an implementation, the current data center acquires the second registered identification information locally stored, and respectively matches the device identification information with each second registered identification information.

[0069] If any second registered identification information matches the device identification information of the target device, it is determined that the other registration state of the target robot in the other data centers is the registered state. If all second registered identification information does not match the device identification information of the target device, it is determined that the other registration state of the target robot in the other data centers is the unregistered state.

[0070] The first registered identification information stored locally in the current data center is acquired, the device identification information is matched with the first registered identification information, and the current registration state of the target robot in the current data center is determined according to a matching result; and the second registered identification information stored locally in the current data center is acquired; wherein the second registered identification information is collected from other data centers by the bus server and distributed to the current data center for local storage, the device identification information is matched with the second registered identification information, and other registration states of the target robot in other data centers are determined according to a matching result. Since the first registered identification information and the second registered identification information to be matched are both stored locally in the current data center, the first registered identification information and the second registered identification information do not need to be temporarily acquired from outside the current data center in the identification information matching process, the efficiency of identification information matching is improved, and the time required for identification information matching is saved.

[0071] S204, if the current registration state and the other registration states are both unregistered states, S205 is performed; if the current registration state is an unregistered state and the other registration state of the target robot in at least one other data center is a registered state, S206 is performed.

[0072] S205, the target robot is registered in the current data center, and identity identification information of the target robot is generated.

[0073] In an embodiment, if the current registration state and the other registration states are both unregistered states, the current data center registers the target robot. Specifically, a preset hash function, such as a SHA function or an MD5 function, can be used to perform hash calculation on the device identification information of the target robot, and the obtained hash value can be used as the identity identification information.

[0074] If the current registration state and the other registration states are both unregistered states, the target robot is registered in the current data center, and the identity identification information of the target robot is generated, which avoids the problem that the identity identification information of the target robot is not unified due to repeated generation of the identity identification information of the target robot.

[0075] S206, at least one other data center is determined as a historical data center, a historical user of the target robot registered in the historical data center is determined, a current user of the target robot is determined according to the registration request, and the identity identification information of the target robot is determined according to the historical user and the current user.

[0076] The historical user represents the user corresponding to the target robot registered in the historical data center. The current user represents the user corresponding to the target robot registered in the current data center.

[0077] In an implementation, if the current registration state is the unregistered state and the other registration state of the target robot in at least one other data center is the registered state, the at least one other data center is taken as a historical data center. The current data center obtains, from the historical data center, a historical user of the target robot registered in the historical data center, and parses a current user of the target robot from the registration request, and then compares the historical user and the current user, and determines the identity information of the target robot according to a comparison result.

[0078] By verifying the current user and the historical user of the target robot, the problem of robot data leakage or mismatch between the identity information of the target robot and the user is avoided.

[0079] Optionally, S206 includes the following two steps A and B:

[0080] A. In the case that the historical user is the same as the current user, the target robot is registered in the current data center, and historical identity information of the target robot in the historical data center is obtained as the identity information of the robot; robot data of the target robot is obtained from the historical data center, and the robot data is locally stored in the current data center.

[0081] The robot data includes but is not limited to running data, basic data and relationship data of the robot, the running data includes but is not limited to mileage data, power data and fault record data, the basic data includes but is not limited to robot model and robot component parameters (such as obstacle avoidance distance and stereo vision installation height), and the relationship data includes but is not limited to binding relationship between the robot and the data center, and corresponding relationship between the robot and the store, for example, the source store of the previous running data of the robot.

[0082] In an implementation, in the case that the historical user is the same as the current user, for example, the target robot is a sold robot, but the user adjusts the use area of the robot, at this time, the current data center registers the target robot, but does not generate the identity information for the target robot, but obtains the historical identity information of the target robot in the historical data center pre-stored in the local end as the identity information of the robot.

[0083] Further, the current data center obtains robot data locally stored in the historical data center from the historical data center, and locally stores the robot data in the current data center, and associates and binds the robot data with the historical identity information.

[0084] In the case that the historical user is the same as the current user, the target robot is registered in the current data center, and the historical identity information of the target robot in the historical data center is obtained as the identity information of the robot, so as to avoid the problem that the identity information of the target robot is repeatedly generated, and the identity information of the target robot is not unified; the robot data of the target robot is obtained from the historical data center, and the robot data is locally stored in the current data center, so as to realize the effect that the robot data is shared between the data centers, and the current data center is facilitated to manage the target robot according to the robot data of the target robot.

[0085] B. In the case that the historical user is different from the current user, the target robot is registered in the current data center, and the identity information of the target robot is generated; the identity information change request is sent to the bus server, so that the bus server changes the historical identity information of the target robot in the historical data center to the identity information according to the identity information change request.

[0086] In an embodiment, in the case that the historical user is different from the current user, for example, the target robot is a rented robot, a trial robot, etc., at this time, the current data center registers the target robot, and generates the identity information of the target robot. Further, the current data center generates the identity information change request and sends it to the bus server. The bus server responds to the identity information change request to control the historical data center to clear the historical identity information of the target robot, and change it to the identity information generated by the current data center. At the same time, the historical identity information and the corresponding robot data can be encrypted and stored, without data sharing.

[0087] In the case that the historical user is different from the current user, the target robot is registered in the current data center, and the identity information of the target robot is generated; the identity information change request is sent to the bus server, so that the bus server changes the historical identity information of the target robot in the historical data center to the identity information according to the identity information change request, so as to realize the effect that the identity information of the target robot is matched with the user, and at this time, the robot data is not shared, so as to avoid the problems of robot data leakage or robot data confusion, and improve the security and reliability of the robot data.

[0088] Optionally, after S205, the method further comprises:

[0089] The identity information is sent to the bus server, so that the bus server distributes the identity information to other data centers for local storage.

[0090] In an implementation, after the current data center generates the identity information for the target robot, the identity information and the device identification information of the target robot are sent to the bus server together. After receiving the identity information and the device identification information, the bus server distributes the identity information and the device identification information to other data centers except the current data center for local storage.

[0091] In the process of distributing the identity information and the device identification information, the bus server determines the distribution state to each other data center in real time. If it is determined that the state of any other data center is distribution failure, the distribution to the other data center is performed again until the state of the other data center is distribution success or the distribution times reaches the upper limit of the distribution times. If the distribution times reaches the upper limit of the distribution times, the bus server sends alarm information to the technician in a timely manner to prompt the technician to distribute the identity information and the device identification information to the other data center in an artificial manner.

[0092] Figure 2B A flowchart of a robot registration provided by the second embodiment of the present application is shown in Figure 2B

[0093] The robot A sends a registration request to the data center A, and the data center A determines the device identification information of the robot A according to the registration request of the robot A.

[0094] The data center A matches the device identification information with the first registered identification information, and determines the current registration state of the robot A in the current data center according to the matching result.

[0095] In the case that the current registration state is the registered state, the registration process is ended, and the corresponding identity information is issued.

[0096] In the case that the current registration state is the unregistered state, the data center A determines the other registration state of the robot A in other data centers according to the device identification information.

[0097] If the current registration state and the other registration state are both unregistered states, the robot A is registered in the current data center, and the identity information of the robot A is generated. The identity information is sent to the bus server, so that the bus server distributes the identity information to other data centers for local storage.

[0098] If the current registration state is the unregistered state, and the other registration state of the robot A in at least one other data center is the registered state, it is determined whether the historical user and the current user are the same.

[0099] ​In the case that the historical user is the same as the current user, the historical identity information of the robot A in the historical data center is acquired as the identity information of the robot.

[0100] In the case that the historical user is different from the current user, the robot A is registered in the current data center, and the identity information of the robot A is generated. The identity information change request is sent to the bus server, so that the bus server changes the historical identity information of the robot A in the historical data center to the identity information according to the identity information change request.

[0101] The specific implementation of each step can refer to the description in the above embodiment, and will not be repeated here.

[0102] Embodiment three

[0103] Figure 3 A structural schematic diagram of a robot identity determination apparatus provided for the third embodiment of the present application is shown in FIG. 3. As shown in the figure, the apparatus comprises: Figure 3

[0104] The first identity information determination module 31 is configured to determine the device identity information of the target robot according to the registration request of the target robot.

[0105] The registration state determination module 32 is configured to determine the current registration state of the target robot in the current data center according to the device identity information, and selectively determine other registration states of the target robot in other data centers.

[0106] The second identity information determination module 33 is configured to determine the identity information of the target robot according to the current registration state and / or the other registration states.

[0107] Optionally, the registration state determination module 32 is specifically configured to:

[0108] In the case that the current registration state is the unregistered state, determine the other registration states of the target robot in other data centers according to the device identity information.

[0109] Optionally, the registration state determination module 32 is further configured to:

[0110] Acquire the first registered identity information stored locally in the current data center;

[0111] Match the device identity information with the first registered identity information, and determine the current registration state of the target robot in the current data center according to the matching result;

[0112] In the case that the current registration state is the unregistered state, the registration state determination module 32 is further configured to:

[0113] ​acquire second registered identification information stored locally by the current data center; wherein the second registered identification information is collected from other data centers by the bus server and distributed to the current data center for local storage;

[0114] match the device identification information with the second registered identification information, and determine the other registration state of the target robot in other data centers according to the matching result.

[0115] Optionally, the second identification information determination module 33 is specifically configured to:

[0116] if the current registration state and the other registration state are both unregistered states, register the target robot in the current data center and generate identity identification information for the target robot.

[0117] Optionally, the second identification information determination module 33 is specifically further configured to:

[0118] if the current registration state is an unregistered state and the other registration state of the target robot in at least one other data center is a registered state, take the at least one other data center as a historical data center;

[0119] determine a historical user of the target robot registered in the historical data center, and determine a current user of the target robot according to the registration request;

[0120] determine the identity identification information of the target robot according to the historical user and the current user.

[0121] Optionally, the second identification information determination module 33 is specifically further configured to:

[0122] in the case that the historical user and the current user are the same, register the target robot in the current data center, and acquire the historical identity identification information of the target robot in the historical data center as the identity identification information of the robot;

[0123] acquire robot data of the target robot from the historical data center and store the robot data locally in the current data center.

[0124] Optionally, the second identification information determination module 33 is specifically further configured to:

[0125] in the case that the historical user and the current user are different, register the target robot in the current data center and generate the identity identification information of the target robot;

[0126] send an identity information change request to the bus server, so that the bus server changes the historical identity identification information of the target robot in the historical data center to the identity identification information according to the identity information change request.

[0127] The robot identification determination apparatus provided by the embodiments of the present application can execute the robot identification determination method provided by any of the embodiments of the present application, and has the corresponding function modules and beneficial effects of the execution method.

[0128] Embodiment Four

[0129] Figure 4 A structural schematic diagram of an electronic device 40 that can be used to implement embodiments of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices (e.g., headsets, glasses, watches, etc.), and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not intended to limit the implementations of the present application described and / or claimed in this document.

[0130] As shown in Figure 4 The electronic device 40 includes at least one processor 41, and a memory, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., which is communicatively connected to the at least one processor 41, wherein the memory stores a computer program that can be executed by the at least one processor. The processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 42 or the computer program loaded from the storage unit 48 into the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other through a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0131] A plurality of components in the electronic device 40 are connected to the I / O interface 45, including: an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, a speaker, etc.; a storage unit 48, such as a magnetic disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0132] The processor 41 can be various general and / or special purpose processing components having processing and computing capabilities. Some examples of the processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 executes various methods and processes described above, such as the identification determination method of the robot.

[0133] In some embodiments, the identification determination method of the robot can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 48. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 40 via the ROM 42 and / or the communication unit 49. When the computer program is loaded onto the RAM 43 and executed by the processor 41, one or more steps of the identification determination method of the robot described above can be performed. Alternatively, in other embodiments, the processor 41 can be configured as the identification determination method of the robot by any other appropriate means, such as by means of firmware.

[0134] Various implementations of the systems and techniques described above can be realized in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a programmable logic device (PLD), a computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0135] Computer programs used to implement the methods of the present application can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer program, when executed by the processor of the machine, implements the functions / acts specified in the flowcharts and / or block diagrams. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine as a stand-alone software package, and partially on a machine or a remote machine or a server.

[0136] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of a machine-readable storage medium will include one or more lines of a program of instructions in a transitory signal, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0137] To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0138] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a user computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), blockchain network, and the Internet.

[0139] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0140] It should be understood that the various forms of flow shown above can be reordered, added to, or have steps deleted. For example, the steps described in the present application can be performed in parallel, in series, or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, and this is not limited herein.

[0141] The above detailed description does not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements, and improvements made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method of identifying a robot, characterized by, The method comprises: determining device identification information of the target robot according to a registration request of the target robot; determining a current registration state of the target robot in a current data center and selectively determining other registration states of the target robot in other data centers according to the device identification information; determining identity identification information of the target robot according to the current registration state and the other registration states; wherein the determining of the identity identification information of the target robot according to the current registration state and the other registration states comprises: if the current registration state is an unregistered state and the other registration state of the target robot in at least one other data center is a registered state, taking the at least one other data center as a historical data center; determining a historical user of the target robot registered in the historical data center and a current user of the target robot according to the registration request; determining the identity identification information of the target robot according to the historical user and the current user; wherein the determining of the identity identification information of the target robot according to the historical user and the current user comprises: in the case that the historical user is different from the current user, registering the target robot in the current data center and generating the identity identification information of the target robot; sending an identity information change request to a bus server, so that the bus server changes historical identity identification information of the target robot in the historical data center to the identity identification information according to the identity information change request.

2. The method of claim 1, wherein, The selective determination of the other registration states of the target robot in the other data centers comprises: in the case that the current registration state is an unregistered state, determining the other registration states of the target robot in the other data centers according to the device identification information.

3. The method of claim 2, wherein, The determining of the current registration state of the target robot in the current data center according to the device identification information comprises: obtaining first registered identification information stored locally in the current data center; matching the device identification information with the first registered identification information and determining the current registration state of the target robot in the current data center according to a matching result; in the case that the current registration state is an unregistered state, the determining of the other registration states of the target robot in the other data centers according to the device identification information comprises: obtaining second registered identification information stored locally in the current data center; wherein the second registered identification information is collected from the other data centers by a bus server and distributed to the current data center for local storage; matching the device identification information with the second registered identification information and determining the other registration states of the target robot in the other data centers according to a matching result.

4. The method of claim 1, wherein, The determining of the identity identification information of the target robot according to the current registration state and the other registration states comprises: If the current registration state and the other registration states are all unregistered states, the target robot is registered in the current data center, and identity information of the target robot is generated.

5. The method of claim 1, wherein, The identity information of the target robot is determined according to the historical user and the current user, including: If the historical user and the current user are the same, the target robot is registered in the current data center, and the historical identity information of the target robot in the historical data center is obtained as the identity information of the robot; The robot data of the target robot is obtained from the historical data center, and the robot data is locally stored in the current data center.

6. An identification determining apparatus of a robot characterized by comprising: Including: The first identity information determination module is configured to determine the device identity information of the target robot according to a registration request of the target robot; The registration state determination module is configured to determine the current registration state of the target robot in the current data center according to the device identity information, and selectively determine the other registration states of the target robot in other data centers; The second identity information determination module is configured to determine the identity information of the target robot according to the current registration state and the other registration states; The second identity information determination module is specifically configured to: If the current registration state is an unregistered state, and the other registration states of the target robot in at least one other data center are registered states, the at least one other data center is taken as a historical data center; Determine the historical user of the target robot registered in the historical data center, and determine the current user of the target robot according to the registration request; Determine the identity information of the target robot according to the historical user and the current user; The second identity information determination module is specifically configured to: In the case that the historical user is different from the current user, the target robot is registered in the current data center, and the identity information of the target robot is generated; Send an identity information change request to a bus server, so that the bus server changes the historical identity information of the target robot in the historical data center to the identity information according to the identity information change request.

7. An electronic device, comprising: The electronic device includes: At least one processor; and The memory is in communication connection with the at least one processor; wherein The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the robot identity determination method in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are used to enable the processor to implement the robot identity determination method in any one of claims 1-5 when executed.

Images