Robot unique identification representation method and device, electronic equipment and storage medium

Abstract

The present disclosure discloses a robot unique identification representation method, device, electronic equipment and storage medium. Wherein, the method comprises: obtaining the inherent code of the robot, and generating a universally unique identifier according to the inherent code; a mapping record including the mapping relationship between the inherent code and the universally unique identifier is established, and the universally unique identifier in the mapping record is taken as the unique identification of the robot in the background management equipment. In the present disclosure scheme, since the universally unique identifier is a meaningless identification code, it is taken as the unique identification of the robot in the background equipment, so that the unique identification of the robot will not be changed due to the replacement of the robot components or the robot business, that is, the generated universally unique identifier is always taken as the unique identification of the robot in the background management equipment, thereby avoiding the problem of changing the unique identification of the robot, and providing convenience for subsequent robot data management.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of robots, and in particular, to a robot unique identification representation method and device, an electronic device, and a storage medium. BACKGROUND

[0002] With the development of robot technology and communication technology, robots are increasingly applied in various industries, such as emergency rescue, firefighting, logistics distribution, and some large space application scenarios.

[0003] Currently, in the background management device of a robot, how to mark a robot with a unique identification is a relatively troublesome matter. A commonly used method is to use the unique serial number of a certain hardware of the robot as its unique identification in the background management device of the robot. However, since the hardware of the robot is sometimes damaged and replaced, the unique identification of the robot in the background management system is often changed, which in turn seriously affects the management of the business data of the robot. SUMMARY

[0004] The present disclosure provides a robot unique identification representation method, device, electronic device, and storage medium to solve the problem that the unique identification of a robot in a background management device is changed due to replacement of a component of the robot.

[0005] According to an aspect of the present disclosure, a robot unique identification representation method, device, electronic device, and storage medium are provided, comprising:

[0006] obtaining an inherent code of a robot, and generating a universally unique identifier according to the inherent code;

[0007] establishing a mapping record comprising a mapping relationship between the inherent code and the universally unique identifier, and using the universally unique identifier in the mapping record as the unique identification of the robot in a background management device.

[0008] According to another aspect of the present disclosure, a robot unique identification representation device is provided, comprising:

[0009] a code obtaining and generating module configured to obtain an inherent code of a robot, and generate a universally unique identifier according to the inherent code;

[0010] a mapping module configured to establish a mapping record comprising a mapping relationship between the inherent code and the universally unique identifier, and use the universally unique identifier in the mapping record as the unique identification of the robot in a background management device.

[0011] According to another aspect of the present disclosure, an electronic device is provided, comprising:

[0012] at least one processor; and

[0013] a memory connected with the at least one processor in communication; wherein,

[0014] 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 unique identification representation method according to the embodiments of the present disclosure.

[0015] According to another aspect of the present disclosure, a computer readable storage medium is provided, which stores computer instructions for enabling a processor to implement the robot unique identification representation method according to the embodiments of the present disclosure when executed.

[0016] The technical solution of the embodiments of the present disclosure, since the universally unique identifier is a meaningless identification code, taking it as the unique identification of the robot in the background device, makes the unique identification of the robot not change due to the replacement of the components of the robot and the influence of the robot business, that is, the universally unique identifier generated is always taken as the unique identification of the robot in the background management device, thereby avoiding the problem of changing the unique identification of the robot, and providing convenience for subsequent robot data management.

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

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following will briefly introduce the drawings needed to be used in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present disclosure, and other drawings can also be obtained by those skilled in the art without creative labor.

[0019] Figure 1 is a flowchart of a robot unique identification representation method according to an embodiment of the present disclosure;

[0020] Figure 2 is a flowchart of a robot unique identification representation method according to an embodiment of the present disclosure;

[0021] Figure 3 is a flowchart of a robot unique identification representation method according to an embodiment of the present disclosure;

[0022] Figure 4is a flow chart of a robot unique identification representation method according to an embodiment four of the present disclosure;

[0023] Figure 5 is a structural schematic diagram of a robot unique identification representation device according to an embodiment five of the present disclosure;

[0024] Figure 6 is a structural schematic diagram of an electronic device implementing a robot unique identification representation method of the present disclosure. DETAILED DESCRIPTION

[0025] In order to enable persons skilled in the art to better understand the present disclosure scheme, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, not all. Based on the embodiments in the present disclosure, all other embodiments obtained by persons skilled in the art without creative labor should be within the scope of protection of the present disclosure.

[0026] Embodiment one

[0027] Figure 1 A flow chart of a robot unique identification representation method is provided for the first embodiment of the present disclosure. The present embodiment can be applied to the scenario of generating a unique identification for a robot in a background management device. The method can be executed by a robot unique identification representation device, which can be implemented in the form of hardware and / or software. The robot unique identification representation device can be configured in an electronic device, such as a robot background management device. As shown in the figure, the method comprises: Figure 1

[0028] S101, obtaining the inherent coding of the robot, and generating a universally unique identification code according to the inherent coding.

[0029] In the embodiments of the present disclosure, the inherent coding of the robot can be the coding that the robot itself carries to represent the robot, for example, it can be the serial number of any component of the robot. The background management device obtains the inherent coding of the robot in the following manner: the robot actively reads the inherent coding and uploads it to the background management device; or, the inherent coding of the robot is first obtained through a collection device (such as a code scanning gun), and then the inherent coding is uploaded to the background management device through the collection device. That is, the background management device can directly obtain the inherent coding from the robot, or indirectly obtain the inherent coding through the collection device. The specific manner is not limited here.

[0030] ​After obtaining the inherent code of the robot, the inherent code of the robot is converted into a corresponding universally unique identifier by using a UUID (Universally Unique Identifier) generation algorithm. It should be noted that the generated universally unique identifier is a meaningless identification code, which is neither affected by replacement of constituent parts of the robot nor affected by the business of the robot.

[0031] In S102, a mapping record including a mapping relationship between the inherent code and the universally unique identifier is established, and the universally unique identifier in the mapping record is taken as the unique identification of the robot in the background management device.

[0032] In the embodiment of the present disclosure, the universally unique identifier and the inherent code of the robot are mapped, and the purpose is to uniquely represent the robot by using the meaningless universally unique identifier in the background management device. In the background management device, in order to record this mapping relationship, a mapping table can be constructed in advance, and then a mapping record including a mapping relationship between the inherent code and the universally unique identifier is added to the mapping table, and the universally unique identifier in the mapping record is taken as the unique identification of the robot in the background management device.

[0033] It should be noted that the inherent code of the robot is not taken as the unique identification of the robot in the background management device because the constituent parts of the robot are sometimes damaged and replaced, resulting in a change in the inherent code of the robot, and then the unique identification of the robot in the background management device is also changed, finally resulting in the background system needing to spend a lot of work to modify the original uploaded data of the robot, resulting in low efficiency of the background system in managing the data uploaded by the robot. In the present disclosure, when the constituent parts of the robot are replaced and the inherent code of the robot is changed, the universally unique identifier in the background management device is not affected, that is, after the universally unique identifier in the mapping record is taken as the unique identification of the robot in the background management device, no matter how the inherent code of the robot changes, the unique identification of the robot in the background management device is fixed. That is, the universally unique identifier as the unique identification of the robot in the background management device does not change with the change of the inherent code of the robot, so that the background management device efficiently manages the business data of the robot by using the fixed unique identification of the robot.

[0034] The technical scheme of the embodiment of the present disclosure, since the universally unique identifier is a meaningless identification code, taking it as the unique identification of the robot in the background device makes the unique identification of the robot not change due to replacement of the component parts of the robot or the business of the robot, that is, the universally unique identifier generated is always taken as the unique identification of the robot in the background management device, thereby avoiding the problem of change of the unique identification of the robot and providing convenience for subsequent management of the robot data.

[0035] Embodiment two

[0036] Figure 2 A flowchart of a robot unique identification representation method provided by the second embodiment of the present disclosure. In the embodiment of the present disclosure, the inherent coding of the robot includes two-dimensional coding data, which can optionally include the device coding of any component part in the robot and the business coding of the business scenario in which the robot is located.

[0037] On this basis, the method flow includes the following steps:

[0038] S201, obtaining the device coding and / or business coding of the robot, and generating a universally unique identifier according to the device coding and / or business coding.

[0039] In the embodiment of the present disclosure, the device coding is optionally the address coding of the robot network card; the business coding refers to the unique number of the robot in the business, for example, the business coding is exemplarily the production number of the robot; when obtaining the production number of the robot, the production number can be optionally read from the robot nameplate by a collection device; for example, the production number is collected by a collection device (such as a code scanning gun), and the collected production number is input into a middle platform system and then synchronized to a background management device. After obtaining the device coding and / or business coding, a universally unique identifier can be generated according to the device coding or the business coding in combination with a UUID generation algorithm. In addition, the device coding and the business coding can also be used to generate a universally unique identifier in combination with a UUID generation algorithm.

[0040] S202, establishing a mapping record including the mapping relationship between the device coding, the business coding and the universally unique identifier, and taking the universally unique identifier in the mapping record as the unique identification of the robot in the background management device.

[0041] In the embodiment of the present disclosure, a mapping table can be established in advance, and then on the basis of S201, a mapping record including the mapping relationship between the device coding, the business coding and the universally unique identifier is directly added in the mapping table. Exemplarily, MFG_CODE represents the business coding, CODE represents the universally unique identifier, and SN represents the device coding. The mapping table constructed is as follows.

[0042] Mapping table 1

[0043]

[0044] Take the first mapping record "MFG_CODE-A, CODE-A, SN-A, 2021-11-25 00:00:00.000" as an example. Its meaning is: the background management device creates a mapping record including the mapping relationship between the device code SN-A of robot A, the business code MFG_CODE-A of robot A, and the universally unique identifier CODE-A of robot A on November 25, 2021, at 0 o'clock; and then the universally unique identifier CODE-A in the mapping record is used as the unique identifier of robot A in the background management device. In this way, the background management device can realize the representation of the unique identifier of multiple robots by establishing multiple mapping records. It should be noted that in each mapping record, in addition to using the universally unique identifier as the unique identifier of the robot in the background management device, the business code in the mapping record can also be used as the unique identifier of the robot from the perspective of the user, so that in the case of device code change, the user can manage the business data of the robot according to the business code; the device code can be used as the unique identifier of the robot from the perspective of the user.

[0045] In the embodiment of the present disclosure, after establishing the mapping relationship between the device code, the business code and the universally unique identifier, the device code, the business code and the universally unique identifier are respectively used as the unique identifier of the robot from different perspectives, which provides guarantee for managing the business data of the robot.

[0046] Embodiment three

[0047] Figure 3 A flowchart of a robot unique identifier representation method provided in the third embodiment of the present disclosure is shown in FIG. 3. As shown in FIG. 3, the method comprises the following steps. Figure 3

[0048] S301, obtaining the device code and / or business code of the robot, and generating a universally unique identifier according to the device code and / or business code.

[0049] S302, establishing a mapping record including the mapping relationship between the device code, the business code and the universally unique identifier, and using the universally unique identifier in the mapping record as the unique identifier of the robot in the background management device.

[0050] S303, managing the business data of the robot according to the mapping relationship in the mapping record.

[0051] ​In the embodiments of the present disclosure, the management of the business data of the robot mainly includes two cases. The first case is to mark the business data uploaded by the robot, and the second case is to respond to the search of the user for the business data of the robot and feed back the corresponding business data to the user.

[0052] For the first case, the business data of the robot is managed according to the mapping relationship in the mapping record, including the following process: the background management device receives the device code and the business data uploaded by the robot, and determines the universal unique identifier corresponding to the device code according to the mapping relationship in the mapping record to which the device code belongs; and the business data is marked by using the universal unique identifier. Taking Table 1 as an example, after generating the business data, the robot A uploads the business data and the read device code SN-A to the background management device. The background management device determines that the mapping record to which the device code SN-A belongs is “MFG_CODE-A, CODE-A, SN-A, 2021-11-25 00:00:00.000” by querying the mapping table. Thus, the background management device determines that the unique identifier of the robot A is the universal unique identifier CODE-A, and then marks the data uploaded by the robot A by using the CODE-A, so as to query the business data of the robot A according to the CODE-A in the subsequent process. For example, the marking result can be referred to Table 2.

[0053] Table 2: Business data record

[0054] Universal Unique Identifier (CODE) Business Data Field Creation Time CODE-A XXX 2021-11-25 00:00:00.000 CODE-B XXX 2021-11-25 00:00:00.000 CODE-C XXX 2021-11-25 00:00:00.000

[0055] For the second case, the business data of the robot is managed according to the mapping relationship in the mapping record, including: receiving a user's business data query request, wherein the business data query request includes the business code of the robot; determining the universal unique identifier corresponding to the business code according to the mapping relationship in the mapping record to which the business code belongs; querying the relevant business data according to the universal unique identifier and feeding back to the user. Taking Table 1 as an example, when the user wants to query the business data of robot A, the data query request including the business code MFG_CODE-A is transmitted to the background management device, and the background management device determines that the mapping record to which the business code MFG_CODE-A belongs is "MFG_CODE-A, CODE-A, SN-A, 2021-11-25 00:00:00.000" by querying the mapping table. Thus, the background management device determines that the unique identifier of robot A is the universal unique identifier CODE-A, and then queries the business data of robot A according to CODE-A. It should be noted that the user selects the business code when querying the business data of the robot because the business code is simpler and easier for the user to remember than the device code. Moreover, the device code may be changed sometimes, and if the user does not update the mapping record according to the changed device code when performing retrieval query in the background management device, accurate business data may not be obtained.

[0056] In the embodiments of the present disclosure, by establishing the mapping record including the mapping relationship between the device code, the business code and the universal unique identifier, and taking the universal unique identifier in the mapping record as the unique identifier of the robot in the background management device, the efficient management of the business data of the robot is guaranteed.

[0057] Embodiment Four

[0058] Figure 4 A flowchart of a method for representing the unique identifier of a robot according to Embodiment Four of the present disclosure is shown in FIG. 4. As shown in FIG. 4, the method includes: Figure 4

[0059] S401, obtaining the device code and / or the business code of the robot, and generating a universal unique identifier according to the device code and / or the business code.

[0060] S402, establishing a mapping record including the mapping relationship between the device code, the business code and the universal unique identifier, and taking the universal unique identifier in the mapping record as the unique identifier of the robot in the background management device.

[0061] ​In this implementation, the device code is the network card address code and the robot component is the motherboard including the network card. When the motherboard where the network card of robot A is located fails, causing the device code to be unobtainable, the motherboard needs to be replaced. There are three main situations for replacing the motherboard: (1) Use a brand new motherboard to install on robot A; (2) Remove and install the motherboard of a robot that is not currently in use (e.g., robot B) on robot A; (3) Use a motherboard that has been repaired and previously used on another robot (e.g., robot C) to install on robot A. Among these, robot C may not have been scrapped yet and is still in the background.

[0062] For the first case, the mapping record can be updated according to steps S403-S404.

[0063] S403. In response to an event where the equipment code changes due to the replacement of a component, obtain the new equipment code and business code uploaded by the robot after the change.

[0064] S404. Update the mapping records, including the service code, according to the new device code.

[0065] Optionally, the processes of S403-S404 are described in combination with Table 1. After robot A detects that the mainboard is replaced, robot A reads the network card address in the new mainboard as the new device code of robot A (for example, SN-D), and at the same time obtains the business code MFG_CODE-A, and then uploads SN-D and MFG_CODE-A to the background management device. When the background management device updates the mapping record including the business code according to the new device code, the process is as follows: searching the mapping table, determining that the mapping record to which MFG_CODE-A belongs is "MFG_CODE-A, CODE-A, SN-A, 2021-11-25 00:00:00.000", replacing SN-A in the mapping record with SN-D to obtain a new mapping record "MFG_CODE-A, CODE-A, SN-D, 2021-11-25 00:00:00.000", thereby realizing the update of the mapping record, and the updated mapping record includes the mapping relationship among MFG_CODE-A, CODE-A and SN-D. After updating the mapping record, robot A uploads the business data carrying the new device code SN-D, and the background management device marks the business data according to the robot unique identifier CODE-A associated with SN-D. After updating the mapping record, when the user uses SN-D or MFG_CODE-A to query business data, the background management device can determine the robot unique identifier CODE-A corresponding to SN-D or MFG_CODE-A according to the updated mapping record, and then query the business data before the robot replaces the mainboard according to CODE-A.

[0066] The second case and the third case are similar. For any of the two cases, the mapping record can be updated according to the steps of S405-S408.

[0067] S405, in response to an event that the device code is changed due to the replacement of the component, obtaining the new device code and the business code uploaded by the robot after the change.

[0068] In the embodiments of the present disclosure, the second case is taken as an example and the content of Table 1 is described. After the mainboard of robot B is installed on robot A, robot A reads the network card address in the new mainboard as the new device code (for example, SN-B), and at the same time obtains the business code MFG_CODE-A, and then uploads SN-B and MFG_CODE-A to the background management device. The background management device receives SN-B and MFG_CODE-A uploaded by robot A, and performs the steps of S406-S407.

[0069] S406, detecting whether there is a target mapping record including the new device code.

[0070] S407. Update the target mapping record so that the updated target mapping record only includes the mapping relationship between the business code and the universally unique identifier.

[0071] In the embodiments of the present disclosure, it is detected whether there is a target mapping record including the new device code, that is, whether there is a mapping relationship between the new device code SN-B and the universally unique identifier CODE-B of the robot B. For example, if it is found through detection of the mapping table that there is a target mapping record "MFG_CODE-B, CODE-B, SN-B, 2021-11-25 00:00:00.000", at this time, the target mapping table needs to be updated to remove the mapping relationship between the new device code SN-B and the universally unique identifier CODE-B of the robot B, so that the updated target mapping record only includes the mapping relationship between the business code MFG_CODE-B and the universally unique identifier CODE-B, that is, the updated target mapping record is "MFG_CODE-B, CODE-B, 2021-11-25 00:00:00.000".

[0072] It should be noted that since the target mapping record retains the mapping relationship between the business code MFG_CODE-B and the universally unique identifier CODE-B, the user can view the historical business data of the robot B by inputting the business code MFG_CODE-B, avoiding the business data of the robot B becoming orphan data. This is exactly the advantage of introducing the business code in the mapping record of the present disclosure.

[0073] S408. Update the mapping record including the business code according to the new device code.

[0074] When updating the mapping record including the business code, the process is as follows: retrieving the mapping table, determining that the mapping record to which MFG_CODE-A belongs is "MFG_CODE-A, CODE-A, SN-A, 2021-11-25 00:00:00.000", replacing SN-A in the mapping record with SN-B to obtain a new mapping record "MFG_CODE-A, CODE-A, SN-B, 2021-11-25 00:00:00.000", thereby realizing updating of the mapping record, and the updated mapping record including the mapping relationship between MFG_CODE-A, CODE-A, and SN-B. Based on updating of the mapping record, after robot A uploads the business data carrying the new device code SN-B, the background management device marks the business data according to the robot unique identifier CODE-A associated with SN-B. After updating the mapping record, when the user uses SN-B or MFG_CODE-A to query the business data, the corresponding robot unique identifier CODE-A of SN-B or MFG_CODE-A can be determined according to the updated mapping record, and the business data before the robot replaces the mainboard can be queried according to CODE-A.

[0075] It should be noted that the reason for removing the mapping relationship between the new device code SN-B and the universally unique identifier CODE-B of robot B is that the mapping relationship between SN-B and CODE-A is established in step S408. If the mapping relationship between SN-B and CODE-B is not removed, when robot A sends the business data carrying the new device code SN-B to the background management device, since SN-B is associated with both CODE-A and CODE-B, the background management device cannot determine which universally unique identifier to use for data marking. If both CODE-A and CODE-B are used for marking, data confusion will inevitably occur.

[0076] In the embodiments of the present disclosure, when the device code changes due to component replacement, the mapping record in the background management device is updated in a timely manner, so as to efficiently manage the robot business data according to the updated mapping record.

[0077] Embodiment Five

[0078] Figure 5 A structural schematic diagram of a robot unique identifier representation device provided in Embodiment Five of the present disclosure is shown in FIG. 5. As shown in FIG. 5, the device includes: Figure 5

[0079] The code acquisition and generation module 501 is configured to acquire the inherent code of the robot and generate a universally unique identifier according to the inherent code.

[0080] ​The mapping module 502 is configured to establish a mapping record including a mapping relationship between the inherent code and the universally unique identifier, and use the universally unique identifier in the mapping record as the unique identifier of the robot in the background management device.

[0081] On the basis of the above-mentioned embodiments, optionally, the inherent code includes a device code of any component part in the robot and a business code of a business scenario in which the robot is located.

[0082] Correspondingly, the code obtaining and generating module includes:

[0083] The generating unit is configured to generate the universally unique identifier according to the device code and / or the business code.

[0084] The mapping module includes:

[0085] The mapping unit is configured to establish a mapping record including a mapping relationship between the device code, the business code and the universally unique identifier.

[0086] On the basis of the above-mentioned embodiments, optionally, the method further includes:

[0087] The data obtaining module is configured to, in response to an event that the device code is changed due to replacement of the component part, obtain new device code and business code uploaded by the robot after the change.

[0088] The mapping record updating module is configured to update the mapping record including the business code according to the new device code.

[0089] On the basis of the above-mentioned embodiments, optionally, the method further includes:

[0090] The detecting module is configured to, before updating the mapping record including the business code according to the new device code, detect whether there is a target mapping record including the new device code.

[0091] The updating module is configured to, if the detection result is that there is the target mapping record, update the target mapping record, so that the updated target mapping record only includes a mapping relationship between the business code and the universally unique identifier.

[0092] On the basis of the above-mentioned embodiments, optionally, the method further includes:

[0093] The data management module is configured to manage business data of the robot according to the mapping relationship in the mapping record.

[0094] On the basis of the above-mentioned embodiments, optionally, the data management module includes:

[0095] The first identification code confirmation unit is configured to receive the equipment code and the service data uploaded by the robot, and determine the universal unique identification code corresponding to the equipment code according to the mapping relationship in the mapping record to which the equipment code belongs.

[0096] The marking unit is configured to mark the service data by using the universal unique identification code.

[0097] On the basis of the above-mentioned embodiments, the data management module can optionally include:

[0098] The receiving unit is configured to receive the service data query request of the user, wherein the service data query request includes the service code of the robot.

[0099] The second identification code confirmation unit is configured to determine the universal unique identification code corresponding to the service code according to the mapping relationship in the mapping record to which the service code belongs.

[0100] The query unit is configured to query the related service data according to the universal unique identification code, and feed back to the user.

[0101] The robot unique identification representation device provided in the embodiments of the present disclosure can execute the robot unique identification representation method provided in any of the embodiments of the present disclosure, and has the corresponding function modules and beneficial effects of the execution method.

[0102] Embodiment six

[0103] Figure 6 A structural schematic diagram of an electronic device 10 that can be used to implement embodiments of the present disclosure 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 herein, their connections and relationships, and their functions, are meant to be examples only, and are not intended to limit the implementations of the present disclosure described and / or claimed in this document.

[0104] As Figure 6As shown, the electronic device 10 includes at least one processor 11, and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., communicatively connected to the at least one processor 11, where the memory stores a computer program executable by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or loaded into the random access memory (RAM) 13 from the storage unit 18. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0105] Various components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc., an output unit 17, such as various types of displays, a speaker, etc., a storage unit 18, such as a magnetic disk, an optical disk, etc., and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network, such as the Internet, and / or various telecommunication networks.

[0106] The processor 11 can be various general and / or special purpose processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose 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 11 performs various methods and processes described above, such as performing the robot unique identity representation method.

[0107] In some embodiments, the robot unique identity representation method can be implemented as a computer program tangibly embodied in a computer readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the robot unique identity representation method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the robot unique identity representation method by any other appropriate means, such as by means of firmware.

[0108] The various embodiments of the systems and techniques described above can be implemented 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 complex programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments 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.

[0109] Computer programs used to implement the methods of the present disclosure 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, such that the computer program, when executed, can cause instructions defined in the flow charts and / or block diagrams to be implemented. The computer program can be executed entirely on a machine, partially on a machine, partially on a machine as part of a standalone software package, or entirely on a remote machine or server.

[0110] In the context of the present disclosure, a computer-readable storage medium can be a tangible medium that can contain or store computer programs for use by or in connection with an instruction execution system, apparatus, or device. The 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, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0111] 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.

[0112] 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), a blockchain network, and the Internet.

[0113] 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 is generally established using computer programs running on the respective computers and having a client-server relationship to each other. A 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.

[0114] It should be understood that the various forms of flow shown above can be re-ordered, added to, or deleted from without departing from the scope of the present disclosure. For example, the steps recited in the present disclosure can be performed in parallel, in series, or in a different order, without departing from the desired results of the technical solutions of the present disclosure, which are not limited herein.

[0115] The above detailed description does not constitute a limitation on the protection scope of the present disclosure. 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 disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A method for representing a unique identifier for a robot, characterized in that, include: Obtain the robot's inherent code; wherein, the inherent code includes the device code of any component of the robot and the business code of the business scenario in which the robot is located; the business code serves as a unique identifier for the robot from the user's perspective; A universally unique identifier is generated based on the device code and the service code; Establish a mapping record that includes the mapping relationship between the device code, the business code and the universally unique identifier, and use the universally unique identifier in the mapping record as the unique identifier of the robot in the background management device; In response to an event where the device code changes due to the replacement of a component of the robot, the new device code and service code uploaded by the robot are obtained; The mapping record, including the service code, is updated based on the new device code.

2. The method according to claim 1, characterized in that, Before updating the mapping record including the service code according to the new device code, the method further includes: Detect whether a target mapping record containing the new device code exists; If it exists, the target mapping record is updated so that the updated target mapping record only includes the mapping relationship between the business code and the universal unique identifier.

3. The method according to claim 1, characterized in that, Also includes: The robot's business data is managed based on the mapping relationships in the mapping records.

4. The method according to claim 3, characterized in that, Based on the mapping relationships in the mapping records, the robot's business data is managed, including: The system receives the device code and business data uploaded by the robot, and determines the universally unique identifier corresponding to the device code based on the mapping relationship in the mapping record to which the device code belongs. The business data is marked using the universally unique identifier.

5. The method according to claim 3, characterized in that, Based on the mapping relationships in the mapping records, the robot's business data is managed, including: Receive a user's business data query request, wherein the business data query request includes the robot's business code; Based on the mapping relationship in the mapping record to which the service code belongs, determine the universally unique identifier corresponding to the service code; The relevant business data is queried based on the universally unique identifier and then fed back to the user.

6. A robot unique identifier device, characterized in that, include: The encoding acquisition and generation module is used to acquire the robot's inherent encoding; wherein, the inherent encoding includes the device encoding of any component of the robot and the business encoding of the business scenario in which the robot is located; the business encoding serves as a unique identifier for the robot from the user's perspective; a universally unique identification code is generated based on the device encoding and the business encoding; The mapping module is used to establish a mapping record that includes the mapping relationship between the device code, the business code and the universal unique identifier, and to use the universal unique identifier in the mapping record as the unique identifier of the robot in the background management device; The data acquisition module is used to acquire the new device code and business code uploaded by the robot in response to an event in which the device code is changed due to the replacement of a component of the robot. The mapping record update module is used to update the mapping record, including the service code, according to the new device code.

7. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that is executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the method of any one of claims 1-5.

Images