KR102615501B1 - Apparatus for Integrating and Managing Robots for Realization of Hyperrobot and Driving Method Thereof - Google Patents

Abstract

The present invention relates to a robot integrated management device for implementing a hyperrobot and a method of driving the device. The robot integrated management device for implementing a hyperrobot according to an embodiment of the present invention communicates with heterogeneous robots installed in an arbitrary space. A communication interface unit and an administrator code (F-Code) for integrated management of heterogeneous robots are installed on each of the heterogeneous robots, and the heterogeneous robots are authenticated based on the code information of the administrator code, and the data of the successfully authenticated robot is collected. It may include a control unit that collects and analyzes.

Description

Robot integrated management device and driving method for realizing hyperrobot {Apparatus for Integrating and Managing Robots for Realization of Hyperrobot and Driving Method Thereof}

The present invention relates to a robot integrated management device and a method of driving the device for implementing a hyperrobot, and more specifically, to implement a hyperrobot that integrates control of heterogeneous multi-robots and mobility and has an integrated authentication system for remote control. It relates to a robot integrated management device and a method of operating the device.

Commonly used peripheral devices of smart devices include storage devices (e.g., memory, disk, etc.), input devices (e.g., keyboard, mouse, etc.), and output devices (e.g., monitor, speaker, printer, etc.). Smart devices and peripheral devices communicate data using wired (e.g. USB) or wireless (e.g. Bluetooth) connections. Meanwhile, looking at the driving methods of robots for various purposes such as home or industrial use, it was common to make complex decisions and perform control using their own central computing unit. However, recently, it has become common for the public to use complex computing-based services using smart devices such as mobile phones and tablet PCs.

Rather than equipping the robot with expensive hardware inside the robot, utilizing the computing power of an external smart device is being explored as an alternative. In order to realize this method, the robot must be registered as a peripheral device of the smart device and be able to receive and execute commands from the smart device based on data communication using a connection method such as USB or Bluetooth. In a control environment where a robot operates as a peripheral device under the control of a smart device, control software produced by the robot manufacturer must be installed on the smart device to control the robot.

However, in industrial settings and general consumers, there are many cases where different types of robots are purchased and used depending on the price, robot performance, and timing of robot purchase. As a result, there is a lot of hassle in managing the heterogeneous robots. There is.

For example, the number of robots is gradually increasing and the number of robots is also increasing, which increases work productivity in terms of replacing humans, but the resulting increase in work complexity and time for management is also a problem. Therefore, there is a demand for the development of a system that can integrate and control the tasks of managing various heterogeneous robots.

Korean Patent Publication No. 10-1253561 (2013.04.05) Korean Patent Publication No. 10-1331852 (2013.11.15) Korean Patent Publication No. 10-2067770 (2020.01.13) Korean Patent Publication No. 10-2015-0074375 (2015.07.02) Korean Patent Publication No. 10-2015-0059713 (2015.06.02)

The purpose of the embodiment of the present invention is to provide a robot integrated management device for implementing a hyperrobot and a method of driving the device, which integrates control of heterogeneous multi-robots and mobility and includes an integrated authentication system for remote control.

The robot integrated management device for implementing hyperrobots according to an embodiment of the present invention includes a communication interface unit for communicating with heterogeneous robots provided in an arbitrary space, and an administrator code (F-Code) for integrated management of the heterogeneous robots. is installed on each of the heterogeneous robots, and includes a control unit that authenticates the heterogeneous robots based on the code information of the administrator code and collects and analyzes data from robots that have successfully been authenticated.

The control unit may designate a group for the heterogeneous robots in the same space and provide a service based on the designated group.

The control unit may simultaneously perform an update operation of the manager code for the heterogeneous robots for which the group is designated.

The control unit may provide analysis results of big data related to the heterogeneous robot when requested by a manufacturer manufacturing the heterogeneous robot.

The control unit includes manufacturer information, model information, function code information that distinguishes the peculiarities of each robot model specification and function, registration classification information indicating the version and registration date of the robot, robot service, and Classification information indicating the allocation code and sequence number for the schedule can be used.

In addition, a method of driving a robot integrated management device for implementing a hyperrobot according to an embodiment of the present invention includes the steps of a communication interface unit communicating with heterogeneous robots provided in an arbitrary space, and a control unit for integrated management of the heterogeneous robots. Installing an administrator code (F-Code) on each of the heterogeneous robots, authenticating the heterogeneous robots based on the code information of the administrator code, and collecting and analyzing data from robots that have successfully authenticated.

The driving method may further include the step of the control unit designating a group for the heterogeneous robots in the same space and providing a service based on the designated group.

The step of providing the service may simultaneously perform an update operation of the manager code for the heterogeneous robots for which the group is designated.

The driving method may further include providing an analysis result of big data related to the heterogeneous robot when the control unit requests a manufacturer manufacturing the heterogeneous robot.

The collecting and analyzing step includes manufacturer information included in the data format of the manager code, model information, function code information that distinguishes the unique features of each robot model specification and function, registration classification information indicating the version and registration date of the robot, and Classification information indicating allocation codes and sequence numbers for robot services and schedules can be used.

According to an embodiment of the present invention, systems such as the MINE system and MAC Address, which have been verified in existing mobile devices and network systems, are called, and a separate identification and authentication system for integrated services of the robot system is implemented based on this. While improving security, it will be possible to secure an authentication and registration system optimized for device operation and service in the robot field.

In addition, the embodiment of the present invention provides a rapid robot commercialization environment to developers and robot companies through a technical support site, and at the same time supports the verification and commercialization of robot datasets through service registration at the development board stage, starting from the development stage. After launch, it will be able to support the entire robot commercialization cycle, including operation, management, and updates of multi-robots.

1 is a diagram showing the structure of a robot integrated management system according to an embodiment of the present invention;
Figure 2 is a diagram schematically showing the driving process of the system of Figure 1;
3 to 5 are diagrams for explaining a security authentication system according to an embodiment of the present invention;
Figure 6 is a block diagram illustrating the detailed structure of the robot integrated management device of Figure 1, and
Figure 7 is a flowchart showing the driving process of the integrated robot management device of Figure 1.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

Figure 1 is a diagram showing the structure of an integrated robot management system according to an embodiment of the present invention, Figure 2 is a diagram schematically showing the driving process of the system of Figure 1, and Figures 3 to 5 are diagrams according to an embodiment of the present invention. This is a diagram to explain the security authentication system.

As shown in Figure 1, the robot integrated management system 90 according to an embodiment of the present invention includes heterogeneous robot devices 100, a communication network 110, a robot integrated management device 120, and a third-party device 130. Includes part or all of.

Here, “including part or all” means that the robot integrated management system 90 is configured by omitting some components such as the third-party device 130, or that the robot integrated management system 90 is comprised of the components constituting the robot integrated management device 120. It means that some or all of it can be integrated into a network device (e.g., wireless switching device, etc.) constituting the communication network 110, and is explained as being entirely included to facilitate a sufficient understanding of the invention.

The robotic device 100 according to an embodiment of the present invention includes heterogeneous robots. Robots are manufactured by various manufacturers and distributed on the market. There are various models and specifications, and there are low-cost and very expensive high-tech robots. Low-priced robots may have low-specification hardware (H/W) or software (S/W), while high-priced robots may include high-specification hardware and software. Low specifications and high specifications can be considered to correspond to the performance of the robot. In this way, robots of different types in terms of model or specifications can be referred to as heterogeneous robots.

The robot according to an embodiment of the present invention, that is, the robot device 100, includes various types of robots that use IMEI (International Mobile Equipment Identity), MAC address, and SIM (Subscriber Identity Module) used in mobile communication, as well as the corresponding IMEI and MAC. It can also include robots without an address or SIM. In the case of robots for which mobile communication is not possible, communication may be possible after installing an administrator code, that is, a code called F-Code, which is distributed through service connection of the integrated robot management device 120 of FIG. 1. Of course, in the case of a robot that has an IMEI, MAC address, and SIM, it is also possible to install a separate F-Code for authentication or registration of the robot for integrated management in the robot integrated management device 120 of Figure 1. In the embodiments of the present invention, there will be no particular limitation to any one form. Regarding the authentication system for authentication and registration of robots, the IMEI, MAC address, SIM, and F-Code can be compared as shown in <Table 1>.

For example, the robot device 100 according to an embodiment of the present invention connects to the robot integrated management device 120 of FIG. 1 through a MAC address, but of course, in the process, the robot device 100 is connected to the operation or surrounding situation. Data can be collected and transmitted, and linkage with other types of robots is possible through the F-Code system. For example, when heterogeneous robots work in the same space, communication may be achieved after registering identification information with each other to ensure smooth work.

The communication network 110 includes both wired and wireless communication networks. For example, a wired or wireless Internet network may be used or linked as the communication network 110. Here, the wired network includes Internet networks such as cable networks and public switched telephone networks (PSTN), and the wireless communication network includes CDMA, WCDMA, GSM, EPC (Evolved Packet Core), LTE (Long Term Evolution), and Wibro networks. It means including. Of course, the communication network 110 according to an embodiment of the present invention is not limited to this, and can be used as an access network for a next-generation mobile communication system to be implemented in the future, for example, a cloud computing network in a cloud computing environment, a 5G network, etc. For example, if the communication network 110 is a wired communication network, the access point within the communication network 110 can connect to the telephone company's exchange office, etc., but if it is a wireless communication network, it can connect to the SGSN or GGSN (Gateway GPRS Support Node) operated by the communication company to receive data. Data can be processed by connecting to various repeaters such as BTS (Base Transceiver Station), NodeB, and e-NodeB.

Communication network 110 may include an access point. Access points include small base stations such as femto or pico base stations that are often installed in buildings. Here, femto or pico base stations are classified according to the maximum number of heterogeneous robot devices 100, etc., which can be connected in the classification of small base stations. Of course, the access point includes a short-distance communication module for performing short-range communication such as ZigBee and Wi-Fi with heterogeneous robot devices 100. Access points can use TCP/IP or RTSP (Real-Time Streaming Protocol) for wireless communication. Here, in addition to Wi-Fi, short-range communication can be performed using various standards such as Bluetooth, Zigbee, infrared (IrDA), RF (Radio Frequency) such as UHF (Ultra High Frequency) and VHF (Very High Frequency), and ultra-wideband communication (UWB). You can. Accordingly, the access point can extract the location of the data packet, designate the best communication path for the extracted location, and forward the data packet to the next device, such as the integrated robot management device 120, along the designated communication path. Access points can share multiple lines in a typical network environment and include, for example, routers, repeaters, and repeaters.

The robot integrated management device 120 provides integrated control of heterogeneous multi-robots and mobility, and has an integrated authentication system for remote control. For example, the robot integrated management device 120 according to an embodiment of the present invention allows heterogeneous robots with different standards, functions, and specifications to be bundled into a single service and provide mutual services after heterogeneous robots exchange and interconnect data with each other. It can be seen as having a system. The robot integrated management device 120 must know through basic robot authentication whether the robot is truly an available robot and what type of robot it is, so that it can transmit and receive data if I give it to the robot. Therefore, determining the identity of the robot (through identification information, etc.) is authentication and registration, and for this purpose, the robot integrated management device 120 can be considered to perform related operations.

In order to perform the above operation, the robot integrated management device 120 may use various methods, but since there are various types of robots and specifications, and there are low-priced robots and very high-tech robots, even low-cost robots must be able to register and authenticate. Since even expensive robots must be able to authenticate, in the embodiment of the present invention, the IMEI, MAC ADDRESS, and SIM used in existing mobile communications are used, and existing robots and other robots use the IMEI, MAC ADDRESS, and SIM. For robots that do not have this, a separate administrator code called F-Code is created, and through this code, the robot is registered, the model is managed, and functions and specifications are separated. Any robot can use the integrated authentication system to use the robot. We will have a system in place to enable this.

Figure 2 schematically shows the driving process of the system of Figure 1. Through technical support from the robot integrated management device 120 of FIG. 1, a rapid robot commercialization environment is provided to developers and robot companies included in the category of the third-party device 130 of FIG. 1, and at the same time, at the development board stage (flying By supporting all stages of verification and commercialization of robot data sets through registration of Let's service, it is possible to support the entire robot commercialization cycle from the development stage to the operation, management, and update of multi-robots after launch. In other words, when the robot integrated management device 120 integrates, operates and manages multiple types of robots, it can generate big data through data collected from multiple types of robots, and the developer can analyze the big data. I will be able to derive various analysis results needed by robot companies. By providing these analysis results, it becomes possible to manage the robot from the development stage even after its release.

The robot integrated management system 90 or robot integrated management device 120 of FIG. 1 according to an embodiment of the present invention prepares for network blackouts at robot sites and different network environments, controls devices such as robots from the user's perspective, and In order to implement integrated services by implementing a single system of robots with different functions and specifications required by various robot manufacturers, the service must be ported, and the authentication system of existing mobile communication devices cannot respond. Therefore, the robotics platform, or service, provided by the robot integrated management device 120 in FIG. 1 calls the MINE system and MAC address systems verified in existing mobile devices and network systems, but requires a separate service for the integrated service of the robot system. An identification authentication system will be implemented, and based on this, security will be improved and an authentication and registration system optimized for device operation and service at the robot site will be secured.

Figure 3 is a diagram to explain the structure and function of a security agent, or SW module, called Flying Let. FlyingLet®SecureAgent, built into the robot integrated management device 120 of Figure 1, which operates as a robotics platform, calls the IMEI, MAC, SIM, and MIN information built into the platform and combines the specialized F-Code system to create an improved authentication system. will be built. In addition, FlyingLet®SecureAgent, which is equipped to secure an authentication system even in the majority of robot systems that do not have an authentication system according to specific functions and specifications, provides interconnection and compatibility between robots and robot services even in general robot systems equipped with it. For this purpose, it is possible to provide minimized certification requirements.

Figure 4 is a diagram to explain the F-Code authentication system for robot integrated services. In FlyingLet®, a control and control management cloud for integrated services of multiple robots, a separate F-Code can be created to manage robot devices and data sets and establish an effective authentication system to control services. The robot manager with the authority certified by FlyingLet® may, of course, be based on the authentication information provided when signing up for the service of the robot integrated management device 120 of FIG. 1, and the robot manager may be the manufacturer of the robot device, When you set and register the model, function, and service, an F-Code is created and activated in the system. It is sent to the Flyinglet ® Secure Agent mounted on the robot device and stored in the robot's firmware file system, and can be reset by an administrator with authorized authority. Until then, it can be seen as being used as a minimum system for device authentication and service operation. As seen in Figure 4, F-Code is a system that defines and distinguishes robot devices, specifications, and services, and security can be improved through the encoding for encryption of Flyinglet ® SecureAgent and the encryption key system for authentication. However, separate data integrity and data security may not be guaranteed.

Figure 5 is a diagram to explain the response plan of the authentication system according to robot specifications. For example, the FlyingLet® Secure Agent built into the AirPath® robotics platform can provide authentication by calling the IMEI, MAC, SIM, and MIN information built into the robot and combining it with a specialized F-Code system. In other words, in the case of the robot device 100 of FIG. 1, when requesting authentication, F-Code information can be extracted and authentication can be requested. And the authentication operation for this authentication can be provided by the robot integrated management device 120 of FIG. 1. Alternatively, authentication can be performed using an authentication module mounted inside the robot integrated management device 120, such as a flying let. The robot integrated management device 120 in FIG. 1 is compatible with the interconnection of robots and robot services when equipped with FlyingLet®Secure Agent, even in robot systems that do not have an authentication system according to specific functions and specifications, minimizing authentication requirements. It will be provided.

As can be seen in FIG. 2, the third-party device 130 in FIG. 1 is used by manufacturers, schools/research centers, developers who manufacture, develop, and research heterogeneous robot devices 100, and who operate robots or collect robot-related data. It may include various types of devices, such as computers or servers owned by operators who share it. To be more precise, it can include not only PC-based terminal devices such as desktop computers and laptop computers, but also mobile-based terminal devices such as tablet PCs and smartphones. Of course, it can also include smart TVs and servers. In the case of a server, the third-party device 130 may be operated in conjunction with the integrated robot management device 120 of FIG. 1 through API (Application Programming Interface).

Manufacturer officials or developers using the third-party device 130 can perform user authentication after signing up for the service of the robot integrated management device 120 of FIG. 1. Of course, such registration and user authentication may be possible from the robot development stage, and through this, it may be possible to perform robot development using data related to countless different types of robots. For example, when there is development of a board to be mounted within the robot device 100, it may be possible to register a development board, and various operations such as registering a robot product and performing authentication can be performed. Through this process, robot remote control and control services will be available. It may also be possible to use it for robot data sharing or artificial intelligence (AI) data commerce.

In addition to the above, the robot device 100, robot integrated management device 120, and third-party device 130 of FIG. 1 can perform various operations, and other details may be discussed later. I would like to replace it with .

Figure 6 is a block diagram illustrating the detailed structure of the integrated robot management device of Figure 1.

As shown in Figure 6, the robot integrated management device 120 according to an embodiment of the present invention is a part or part of the communication interface unit 600, the control unit 610, the robot integrated management unit 620, and the storage unit 630. includes everything.

Here, “including part or all” means that the robot integrated management device 120 is configured by omitting some components such as the storage unit 630, or that some components such as the robot integrated management unit 620 are configured by the control unit ( 610), it means that it can be integrated and configured with other components such as

The communication interface unit 600 may communicate with the robot device 100 of FIG. 1 to perform an operation to install a SW module of a security agent to perform an operation according to an embodiment of the present invention. Of course, the security agent may include the F-Code described previously. For example, operations can be performed in various forms to install source code such as a security agent program or F-Code according to an embodiment of the present invention. The manufacturer of the robot device 100 in FIG. 1 or the operator who purchases and operates the robot device 100 connects to the robot integrated management device 120, performs administrator authentication, and then selects the model or type of the robot device 100. After registering information related to specifications, you can perform the corresponding operation. For example, if the robot device 100 is capable of wireless communication, programs or source code can be installed remotely. On the other hand, in cases where communication is not possible, it may be possible for the administrator to download and store the relevant program on a storage medium such as a USB or computer, and then install it on the robot device 100. For example, a card such as a USB can be inserted, and it may also be possible to connect a computer and install it in the form of an EEPROM. The communication interface unit 600 may be involved in these operations.

Once this installation process is completed, the communication interface unit 600 can perform authentication and registration operations for various heterogeneous robots, that is, for the robot device 100. Of course, such robot authentication may be performed whenever data is transmitted from the robot device 100, or authentication may be performed only when the power is turned on/off. For example, it may be possible to perform an authentication operation when the power is turned on while the robot device 100 is turned off after completing a task. Since this authentication operation can be performed in various ways depending on the service policy of the service provider providing the service according to the embodiment of the present invention, it will not be specifically limited to any one type. Of course, encryption/decryption may occur during this authentication process, and the communication interface unit 600 may also participate in such encryption/decryption operations.

In addition, the communication interface unit 600 may periodically collect data related to the operation of the robot from the robot device 100 and provide it to the control unit 610, or the collected data may be collected as shown in FIG. 1 under the control of the control unit 610. It may be transmitted to the DB 120a and systematically classified and stored based on the identification information of the robot device 100.

The control unit 610 is responsible for the overall control operation of the communication interface unit 600, robot integrated management unit 620, and storage unit 630 of FIG. 6. For example, the control unit 610 operates the robot integrated management unit 620 when there is a request to install an F-Code according to an embodiment of the present invention in the robot device 100 from the third party device 130 of FIG. 1. You can control and perform operations related to this. In addition, the control unit 610 can control the communication interface unit 600 to remotely control or control the operation of the robot device 100 when the installation of the security agent program on the robot device 100 is completed, and the robot device ( If there is an authentication request in 100), the authentication data can be temporarily stored in the storage unit 630 and then retrieved and provided to the robot integrated management unit 620 to receive the authentication result. Of course, the authentication result can be provided to the robot device 100, and then the data collected from the robot device 100 can be stored and managed in the DB 120a of FIG. 1. Of course, the data collected by the robot device 100 may be of various types, and the control unit 610 may be able to provide the data to the robot integrated management unit 620 for data processing.

The robot integrated management unit 620 can perform operations for integrated management of a plurality of heterogeneous robot devices 100. To this end, the robot integrated management unit 620 can pre-install a program for integrated management with the robot device 100, and based on this, it analyzes the data collected from the heterogeneous robot device 100 to manage the heterogeneous robot device 100. It can operate so that interconnection between devices is possible. For example, let's assume that different types of robots are used in a random space, such as a restaurant or factory. In this case, managers may have a lot of hassle managing the heterogeneous robots. Therefore, it may be possible to combine and operate these heterogeneous robots into a single service. Of course, a single service here can be a group, or an area of arbitrary space or identification information. Accordingly, when heterogeneous robots are bundled into a single service, operations such as simultaneous updates when an update of a program, etc. is required, may be possible. Alternatively, updates can be made to have performance specialized for arbitrary spaces. Furthermore, it becomes possible to exchange data and interoperate between robots. For example, when tied to a single service or set as a group, one robot can pre-register information about other heterogeneous robots, so communication or data transmission can be possible based on this.

For example, let's assume that a specific robot in a random space is not equipped with a communication module to transmit data to the robot integrated management device 120 of FIG. 1. In this case, it may be impossible to provide data collected from the robot to the robot integrated management device 120 of FIG. 1. In this case, data may be transmitted to the robot device 100, that is, a robot currently in an idle state in the same space, and a request may be made to transmit the data to the robot integrated management device 120. Accordingly, the robot integrated management unit 620 may be able to perform data analysis operations by integrating the robot devices 100 set to a single service group, etc. Accordingly, the manager of any space can receive various analysis results using heterogeneous robots, and through this, results related to the efficient operation of the robot devices 100 or, in the case of a restaurant or factory, the operation and management of the restaurant or factory. It may be possible to receive it as much as possible.

The storage unit 630 can temporarily store various types of data processed under the control of the control unit 610. For example, the storage unit 630 can temporarily store data provided from a plurality of heterogeneous robot devices 100 under the control of the control unit 610, and retrieve the temporarily stored data and provide it to the robot integrated management unit 620. can do. In addition, the storage unit 630 can temporarily store data stored in the DB 120a of FIG. 1 under the control of the control unit 610, and provide the data to the robot integrated management unit 620 for data analysis. There will be.

In addition to the above, the communication interface unit 600, control unit 610, robot integrated management unit 620, and storage unit 630 of FIG. 6 can perform various operations, and other details have been sufficiently explained previously. I want to replace it with fields.

The communication interface unit 600, control unit 610, robot integrated management unit 620, and storage unit 630 of FIG. 6 according to an embodiment of the present invention are composed of hardware modules that are physically separated from each other, but each module has an internal It will be possible to store software to perform the above operations and execute it. However, the software is a set of software modules, and each module can be formed of hardware, so there will be no particular limitation on the configuration of software or hardware. For example, the storage unit 630 may be hardware, such as storage or memory. However, since it is possible to store information through software (repository), the above content will not be specifically limited.

Meanwhile, as another embodiment of the present invention, the control unit 610 may include a CPU and memory, and may be formed as a single chip. The CPU includes a control circuit, an arithmetic unit (ALU), an instruction interpretation unit, and a registry, and the memory may include RAM. The control circuit performs control operations, the operation unit performs operations on binary bit information, and the command interpretation unit includes an interpreter or compiler, which can convert high-level language into machine language and machine language into high-level language. , the registry may be involved in software data storage. According to the above configuration, for example, at the beginning of the operation of the robot integrated management device 120, the data operation processing speed is increased by copying the program stored in the robot integrated management unit 620, loading it into memory, that is, RAM, and then executing it. It can be increased quickly. In the case of deep learning models, they can be loaded into GPU memory rather than RAM and executed by accelerating the execution speed using GPU.

Figure 7 is a flowchart showing the driving process of the integrated robot management device of Figure 1.

For convenience of explanation, referring to FIG. 7 together with FIG. 1, the robot integrated management device 120 according to an embodiment of the present invention communicates with heterogeneous robots provided in a random space (S700). Here, communication may mean communication by remote control, but may also include communication made through a wired cable connected to a robot and a connector, or through direct communication such as Bluetooth.

In addition, the robot integrated management device 120 installs an administrator code (F-Code) for integrated management of heterogeneous robots on each heterogeneous robot, and authenticates the heterogeneous robots based on the code information of the administrator code to enable authentication. Data from successful robots can be collected and analyzed (S710). For example, big data related to heterogeneous robots can be analyzed using artificial intelligence (AI) deep learning programs and the analysis results can be provided to manufacturers or research institutes that develop robots. Through this, it is possible to improve the hardware or software of already developed robots, and it may also be possible to apply analysis results to the development board from the robot development stage. For example, as a result of analyzing heterogeneous robots used in a specific space, when problems related to the design, function, or performance of the robot are discovered, the robot can be developed or improved by taking this into consideration.

In addition to the above, the robot device 100 and the robot integrated management device 120 of FIG. 1 can perform various operations, and other details have been sufficiently explained previously, so these will be replaced.

Meanwhile, even though all the components constituting the embodiment of the present invention are described as being combined or operating in combination, the present invention is not necessarily limited to this embodiment. That is, as long as it is within the scope of the purpose of the present invention, all of the components may be operated by selectively combining one or more of them. In addition, although all of the components may be implemented as a single independent hardware, a program module in which some or all of the components are selectively combined to perform some or all of the combined functions in one or more pieces of hardware. It may also be implemented as a computer program having. The codes and code segments that make up the computer program can be easily deduced by a person skilled in the art of the present invention. Such computer programs can be stored in non-transitory computer readable media and read and executed by a computer, thereby implementing embodiments of the present invention.

Here, a non-transitory readable recording medium refers to a medium that stores data semi-permanently and can be read by a device, rather than a medium that stores data for a short period of time, such as a register, cache, or memory. . Specifically, the above-described programs may be stored and provided on non-transitory readable recording media such as CD, DVD, hard disk, Blu-ray disk, USB, memory card, ROM, etc.

In the above, preferred embodiments of the present invention have been shown and described, but the present invention is not limited to the specific embodiments described above, and may be used in the technical field to which the invention pertains without departing from the gist of the invention as claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be understood individually from the technical idea or perspective of the present invention.

100: Robotic device (or robot) 110: Communication network
120: Robot integrated management device 130: Third party device
600: Communication interface unit 610: Control unit
620: Robot integrated management unit 630: Storage unit

Claims (10)

A communication interface unit that communicates with heterogeneous robots provided in a random space; and
An administrator code (F-Code) for integrated management of the heterogeneous robots is installed on each of the heterogeneous robots, and the heterogeneous robots are authenticated based on the code information of the administrator code to collect data on robots that have successfully been authenticated. And a control unit to analyze;
The control unit designates groups for the heterogeneous robots in the same space and provides services based on the designated groups,
The control unit simultaneously performs an update operation of the manager code for the heterogeneous robots for which the group is designated,
The control unit provides analysis results of big data related to the heterogeneous robot when requested by a manufacturer manufacturing the heterogeneous robot,
The control unit includes manufacturer information, model information, function code information that distinguishes the specifications and features of each robot model, registration classification information that indicates the version and registration date of the robot, and robot service included in the data format of the manager code. and a robot integrated management device for implementing hyperrobots, using classification information representing allocation codes and sequence numbers for schedules. delete delete delete delete A communication interface unit communicating with heterogeneous robots provided in a random space; and
The control unit installs an administrator code (F-Code) for integrated management of the heterogeneous robots on each of the heterogeneous robots, authenticates the heterogeneous robots based on the code information of the administrator code, and identifies the robot that has successfully been authenticated. Including collecting and analyzing data,
It further includes a step of the control unit designating a group for the heterogeneous robots in the same space and providing a service based on the designated group,
The steps for providing the above service are:
Simultaneously perform an update operation of the manager code for the heterogeneous robots for which the group is designated,
It further includes providing, by the control unit, an analysis result of big data related to the heterogeneous robot when there is a request from a manufacturer manufacturing the heterogeneous robot,
The collection and analysis steps include:
Included in the data format of the manager code are manufacturer information, model information, function code information that distinguishes the specifications and features of each robot model, registration classification information that indicates the version and registration date of the robot, and allocation for robot services and schedules. A method of driving a robot integrated management device for implementing a hyperrobot using classification information indicating code and sequence number. delete delete delete delete