A unified platform management method, device, equipment and medium

Abstract

This application relates to the field of software engineering, and in particular to a unified platform management method, apparatus, device, and medium. The method includes: In this embodiment, parameter data from the SDK interface corresponding to the robot is obtained, and the obtained parameter data is standardized to obtain standard parameter data corresponding to the robot. The obtained standard parameter data is then encapsulated with the SDK to obtain the standard SDK corresponding to the robot. The standard SDK is then connected to a target platform, and the target platform uniformly controls all standard SDKs to achieve control of all robots corresponding to the standard SDKs. In other words, by standardizing the SDK parameter data, a single platform can manage all standard SDKs, replacing the method of using separate management platforms from different manufacturers to manage SDKs separately. This simplifies the robot application process and improves the user experience.

Description

Technical Field

[0001] This application relates to the field of software engineering technology, and in particular to a unified platform management method, apparatus, equipment and medium. Background Technology

[0002] Intelligent robots are the product of the evolution of industrial robots from non-intelligent to intelligent, and from low-intelligence to high-intelligence. Existing service robots possess functions such as facial recognition, localization, obstacle avoidance, touchscreen interaction, speech-to-text conversion, semantic understanding, knowledge base, and text-to-speech. When developing robots, manufacturers utilize their own technologies to implement these functions, employing different methods, but the resulting effects are similar.

[0003] Generally, robot manufacturers provide a Software Development Kit (SDK). This SDK is a toolkit for developing robot applications and includes the interfaces for calling the aforementioned functions. Technicians can use this SDK to develop various combinations of robot functions, thus realizing the development of robot applications.

[0004] However, because the technologies of each robot manufacturer are not interoperable, the SDKs they provide are completely different. In service robot applications, there are often scenarios where multiple robots need to work together. These robots may come from different manufacturers. In this case, it is necessary to develop separately using the SDKs of each robot manufacturer and manage them separately using the management platforms of different manufacturers, which makes the application process of robots quite cumbersome. Summary of the Invention

[0005] To address the cumbersome process of robot application, this application provides a unified platform management method, apparatus, equipment, and medium.

[0006] Firstly, this application provides a unified platform management method, which adopts the following technical solution:

[0007] Acquire multiple parameter data, wherein the parameter data is data of the SDK interface corresponding to the robot, and the SDK interface is the interface of the SDK required for the robot to implement its functions;

[0008] The parameter data corresponding to each robot is normalized to obtain the standard parameter data corresponding to each robot. The format of the standard parameter data is a preset standard format.

[0009] Based on the standard parameter data corresponding to each robot and the SDK corresponding to each robot, the data is encapsulated to obtain the standard SDK corresponding to each robot;

[0010] Each standard SDK is connected to a target platform via an interface. The target platform is used to manage robots that meet preset conditions, namely, the parameter data of the interface between the robot and the target platform is in a preset standard format.

[0011] By adopting the above technical solution, the parameter data of the corresponding SDK interface of the robot is obtained and standardized to obtain the standard parameter data of the robot. The obtained standard parameter data is then encapsulated with the SDK to obtain the standard SDK of the robot. The standard SDK is then connected to the target platform, and the target platform controls all standard SDKs in a unified manner to control all robots corresponding to the standard SDK. In other words, by standardizing the parameter data of the SDK, a single platform can be used to manage all standard SDKs, replacing the method of using different manufacturers' management platforms to manage SDKs separately. This simplifies the application process of robots and improves the user experience.

[0012] In conjunction with the first aspect, in some embodiments, the normalization processing of the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot includes:

[0013] Based on the parameter data corresponding to each robot, determine the function corresponding to each robot, and the function parameter data corresponding to each function;

[0014] The function parameter data corresponding to each function is normalized and transformed to obtain the first parameter data;

[0015] Based on the function corresponding to each robot and the function category to which each function belongs, determine the target function category corresponding to each robot, obtain the target standard parameter data corresponding to the target function category, and determine the second parameter data based on the target standard parameter data. The function category includes at least one function, and the function corresponding to each robot does not include any function included in the target function category.

[0016] Based on the first parameter data and the second parameter data, the standard parameter data corresponding to each robot is determined.

[0017] By adopting the above technical solution, the data that needs to be standardized is divided into two categories according to the robot's functions and the corresponding functional parameter data. The first parameter data and the second parameter data are standardized respectively. Then, standard parameter data is obtained based on the first parameter data and the second parameter data. This realizes that the format of the SDK's parameter data is converted into a preset standard format, so that the target platform can manage each robot in a unified manner.

[0018] In conjunction with the first aspect, in some embodiments, the normalization and transformation of the functional parameter data corresponding to each function to obtain the first parameter data includes:

[0019] Based on the function category to which each function belongs, a first function category and a second function category are determined. Each function included in the first function category belongs to the function corresponding to each robot. The function corresponding to the second function category includes the first function and the second function. The first function belongs to the function corresponding to each robot, and the second function does not belong to the function corresponding to each robot.

[0020] Obtain the first standard function parameter data corresponding to each function included in the first function category;

[0021] Obtain the second standard function parameter data corresponding to the first function, and determine the third standard function parameter data based on the second standard function parameter data and the second function. The third standard function parameter data is parameter data that can realize the first function and the second function.

[0022] The first parameter data is determined based on the first standard functional parameter data and the third standard functional parameter data.

[0023] By adopting the above technical solution, and by standardizing the functional categories and some of the functional categories included in the robot, the first parameter data that can realize all the functions in the functional categories and some of the functional categories included in the robot is obtained. This achieves the standardization of all functions in the first functional category and the second functional category, that is, the comprehensiveness of functional standardization is achieved. Furthermore, it enables unified management of all robots.

[0024] In conjunction with the first aspect, in some embodiments, determining the third standard function parameter data based on the second standard function parameter data and the second function includes:

[0025] When the second function category is a text processing category, determine whether the second function includes a paragraph processing function and whether the first function includes a short sentence processing function;

[0026] If the second function includes a paragraph processing function, and the first function includes a short sentence processing function, then based on the second standard function parameter data corresponding to the short sentence processing function and the loop function, the third standard parameter data corresponding to the text processing category is determined.

[0027] By adopting the above technical solution, the paragraph processing function is realized through the short sentence processing function and the loop function. At this time, the function parameters of the short sentence processing function and the loop function are the standard function parameter data corresponding to the paragraph processing function, realizing the standardized processing of the short sentence processing function, and completing the collection of the third standard data.

[0028] In conjunction with the first aspect, in some embodiments, obtaining target standard parameter data corresponding to the target functional category, and determining second parameter data based on the target standard parameter data, includes:

[0029] Determine whether the target function category includes software functions, where the software functions are functions that do not need to be implemented through external interfaces;

[0030] If the target function category includes software functions, then the standard function parameter data corresponding to each software function is obtained, and the target standard parameter data is determined based on the standard function parameter data corresponding to each software function.

[0031] Based on the standard parameter data corresponding to each software function, the second parameter data corresponding to each robot is determined.

[0032] By adopting the above technical solution, and by standardizing the software functions in the functional categories that are not present in the robot, the robot can realize the above software functions, thereby achieving the standardization of functions not included in the robot, and further, achieving unified management of all robots.

[0033] In conjunction with the first aspect, in some embodiments, the method further includes:

[0034] Determine whether the target function category includes hardware functions, where hardware functions are those that require external interfaces to implement. If the target function category includes hardware functions, determine the external interface for those hardware functions. Specifically, based on the standard parameter data corresponding to each robot and the SDK corresponding to each robot, encapsulation is performed to obtain the standard SDK corresponding to each robot, including:

[0035] Based on the external interfaces corresponding to the hardware functions, the standard parameter data corresponding to each robot, and the SDK corresponding to each robot, the standard SDK corresponding to each robot is encapsulated to obtain the standard SDK corresponding to each robot.

[0036] By adopting the above technical solution, and by reserving external interfaces for hardware functions in functional categories that do not exist in the robot, the robot can realize the above hardware functions. Furthermore, the external interfaces, standard parameter data, and the corresponding SDK of the robot are encapsulated to obtain a standard SDK, thereby realizing unified management of various robots.

[0037] In conjunction with the first aspect, in some embodiments, the step of connecting each standard SDK to the target platform via an interface further includes:

[0038] The target platform is developed based on a preset operating environment, which is an operating environment that can operate across operating systems.

[0039] Based on the developed target platform, the robot connected to the target platform is managed.

[0040] By adopting the above technical solution, unified management is achieved through the target platform. The target platform is developed in an operating system environment. Based on the developed target platform, electronic devices realize cross-operating system control of the target platform to manage robots.

[0041] Secondly, this application provides a unified platform management device, which adopts the following technical solution:

[0042] A unified platform management device includes: an acquisition module for acquiring multiple parameter data, wherein the parameter data is data of an SDK interface corresponding to a robot, and the SDK interface is the interface of the SDK required for the robot to implement its functions;

[0043] The standardization module is used to standardize the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot. The format of the standard parameter data is a preset standard format.

[0044] The encapsulation module is used to encapsulate the standard parameter data corresponding to each robot and the SDK corresponding to each robot to obtain the standard SDK corresponding to each robot.

[0045] The connection module is used to connect each standard SDK to the target platform through an interface. The target platform is used to manage robots that meet preset conditions, namely, the parameter data of the interface between the robot and the target platform is in a preset standard format.

[0046] Thirdly, this application provides an electronic device that adopts the following technical solution:

[0047] An electronic device comprising:

[0048] At least one processor;

[0049] Memory;

[0050] At least one application, wherein the at least one application is stored in memory and configured to be executed by at least one processor, said at least one application is configured to: perform the unified platform management method described above.

[0051] Fourthly, this application provides a computer-readable storage medium, which adopts the following technical solution:

[0052] A computer-readable storage medium includes: storing information that can be loaded by a processor and executed using the aforementioned unified platform management method.

[0053] In summary, this application has the following beneficial technical effects: The embodiments of this application obtain parameter data from the SDK interface corresponding to the robot, and standardize the obtained parameter data to obtain standard parameter data corresponding to the robot. The obtained standard parameter data is then encapsulated with the SDK to obtain the standard SDK corresponding to the robot. The standard SDK is then connected to the target platform, and the target platform uniformly controls all standard SDKs to achieve control of all robots corresponding to the standard SDK. In other words, by standardizing the SDK parameter data, a single platform can manage all standard SDKs, replacing the method of using different manufacturers' respective management platforms to manage SDKs separately. This simplifies the robot application process and improves the user experience. Attached Figure Description

[0054] Figure 1 This is a flowchart illustrating a unified platform management method provided in an embodiment of this application;

[0055] Figure 2 This is a schematic diagram of a method for sending a calling instruction provided in an embodiment of this application;

[0056] Figure 3 This is a flowchart illustrating another unified platform management method provided in an embodiment of this application;

[0057] Figure 4 This is a flowchart illustrating the process of determining robot functions provided in an embodiment of this application;

[0058] Figure 5 This is a block diagram of a unified platform management device provided in an embodiment of this application;

[0059] Figure 6 This is a schematic diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0060] The following is in conjunction with the appendix Figure 1-6 This application will be described in further detail.

[0061] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0062] To facilitate understanding of the technical solutions proposed in this application, several elements that will be introduced in the description of this application are first presented here. It should be understood that the following description is only for the purpose of understanding these elements and the content of the embodiments of this application, and does not necessarily cover all possible situations.

[0063] Intelligent robots are the product of the development of industrial robots from no intelligence to intelligence, and from low intelligence to high intelligence. The functions that existing service robots can achieve include: facial recognition, positioning, obstacle avoidance, touch screen interaction, speech-to-text, semantic understanding, text-to-speech, and knowledge query and storage.

[0064] When developing robots, manufacturers need to develop corresponding management platforms and SDK interfaces to perform a series of operations such as robot development and management. However, each manufacturer develops its own management platform and SDK interface based on its own technology, and the technologies used in different manufacturers' management platforms and SDK interfaces are not interoperable. This means that when users simultaneously use robots from multiple manufacturers, they need to utilize multiple management platforms, learn the technologies of multiple manufacturers, and develop and manage each robot separately, resulting in low development and management efficiency.

[0065] Based on the above-mentioned technical problems, this application provides a unified platform management method, referring to... Figure 1 The unified platform management method is executed by electronic devices, and the method includes:

[0066] In step S101, multiple parameter data are acquired.

[0067] The parameter data refers to the data from the SDK interface corresponding to the robot, which may include programming language data and / or function call data, where the programming language data is the program code.

[0068] Among them, the SDK interface is the interface of the SDK required for the robot to implement its functions.

[0069] Specifically, SDK stands for Software Development Kit. The Software Development Kit is used to implement a certain function of robot software. The software development kit can be a toolkit containing many function packages. In addition, the toolkit can also contain complex hardware for embedded system communication, program code, supporting technical annotations, and supporting documentation. The supporting documentation is used as basic reference material to clarify doubts.

[0070] More specifically, the SDK forms the foundation for platform management and robot development; that is, the platform needs to develop and manage robots through the SDK. More specifically, the platform and the robot connect through the SDK interface. The platform can send instructions to the SDK through the SDK interface, and after receiving the instructions, the SDK uses the instructions and parameter data from the SDK interface to develop and manage the robot.

[0071] Each robot corresponds to a set of parameter data. Due to technological barriers between manufacturers, the development logic of the platform and SDK differs for robots from different manufacturers, resulting in different parameter data formats in the SDK interface. Therefore, it is necessary to use a platform from the same manufacturer for managing and developing robots from that manufacturer. Thus, users who want to manage all robots uniformly need to convert the robot's parameter data to a unified format, enabling the development and management of all robots using a single platform.

[0072] In step S102, the parameter data corresponding to each robot is normalized to obtain the standard parameter data corresponding to each robot.

[0073] The standard parameter data is in a preset standard format, meaning it is parameter data that has undergone normalization processing. The preset standard format is a parameter data format that can be accessed by the target platform. Specifically, the target platform is used to manage robots that meet preset conditions. The target platform can be installed on a terminal, electronic device, or server, and the preset standard format is a pre-defined format.

[0074] Specifically, since the parameter data for each robot is different, and a platform can only manage the corresponding robot, it is necessary to standardize the parameter data for each robot so that the standardized SDKs can all connect to the same platform, thereby enabling unified management of each robot.

[0075] More specifically, the standard program code corresponding to the standard parameter data is obtained. The standard program code is in a preset standard format. Further, for each robot, the program code corresponding to the parameter data is obtained, and the differences between the standard code and the program code corresponding to the parameter data are identified. Based on the differences between the standard program code and the program code corresponding to the parameter data, the program code corresponding to the parameter data is converted into the standard program code, so that the format of the robot's parameter data is converted into the preset standard format, thus completing the standardization process of the robot's parameter data.

[0076] In step S103, based on the standard parameter data corresponding to each robot and the SDK corresponding to each robot, the data is encapsulated to obtain the standard SDK corresponding to each robot.

[0077] Specifically, since robots can only be developed using the SDK configured by the manufacturer, in order to ensure that the robot can be developed, the standard parameter data corresponding to the generated robot needs to be integrated into the corresponding SDK of the robot, and then the integrated SDK is packaged to obtain the standard SDK.

[0078] More specifically, for each robot, the standard parameter data corresponding to the robot can be compiled, the compiled standard parameter data can be integrated into the corresponding SDK of the robot, and then the integrated SDK can be encapsulated to obtain the standard SDK corresponding to the robot.

[0079] In step S104, each standard SDK is connected to the target platform via an interface.

[0080] Among them, the preset condition is that the parameter data of the interface between the robot and the target platform is in a preset standard format.

[0081] Specifically, when the target platform receives a user input instruction, it generates a call instruction based on the instruction and sends the call instruction to the standard SDK connected to the target platform. This controls the robot developed by the standard SDK and drives the robot to perform actions according to the call instruction. The target platform can only manage robots that meet preset conditions. Therefore, only robots that meet preset conditions can be uniformly connected to the target platform and managed uniformly.

[0082] Furthermore, the target platform can not only perform unified development on all robots that meet the preset conditions, thus improving development efficiency, but also perform unified management on all robots that meet the preset conditions, thus improving management efficiency. The preset conditions can be automatically set by the system according to a preset standard format or set manually. This application embodiment does not limit the specific settings.

[0083] Further, see Figure 2When the target platform receives a user-input command, it generates a call command based on the command and sends it to the various standard SDKs connected to the target platform. The call command is then converted into corresponding preset commands by each standard SDK, and these preset commands are sent to their respective SDKs. This controls the SDK to develop the robot and drive it to perform actions according to the corresponding preset commands. More specifically, the target platform connects to the SDKs via standard SDKs. The target platform can send commands to the SDKs through the standard SDKs. After receiving the commands, the SDKs control the robot to develop and drive it to perform actions according to the corresponding preset commands. The target platform is installed on an electronic device, while the standard SDKs and the SDKs are both installed on the robot. It is worth noting that... Figure 2 The content in this document is for illustrative purposes only and is not intended to limit the embodiments of this application.

[0084] This application embodiment obtains the parameter data of the SDK interface corresponding to the robot, and performs normalization processing on the obtained parameter data to obtain the standard parameter data corresponding to the robot. The obtained standard parameter data is then encapsulated with the SDK to obtain the standard SDK corresponding to the robot. The standard SDK is then connected to the target platform, and the target platform uniformly controls all standard SDKs to achieve control of all robots corresponding to the standard SDK. In other words, by normalizing the parameter data of the SDK, it is possible to use a single platform to develop and manage all standard SDKs, replacing the method of using different manufacturers' respective management platforms to develop and manage SDKs separately. This simplifies the robot application process and improves development and management efficiency.

[0085] One possible implementation of this application embodiment involves, in step S102, normalizing the parameter data corresponding to each robot to obtain standard parameter data for each robot. (See [link to relevant documentation]). Figure 3 This can be achieved through steps S1021, S1022, S1023, and S1024, wherein:

[0086] Step S1021: Based on the parameter data corresponding to each robot, determine the function corresponding to each robot and the function parameter data corresponding to each function.

[0087] Among them, the function parameter data is the program code that implements the function in the parameter number, and one function corresponds to one function parameter data.

[0088] Specifically, based on the parameter data corresponding to the robot, the functions that the parameter data can achieve are determined, that is, the functions corresponding to the robot. For each function, the program code corresponding to the function is obtained, and the program code is determined as the function parameter data corresponding to the function.

[0089] Furthermore, since each robot has a different purpose, the functions included in each robot may also differ. For example, the first robot's functions include a1, a2, and b2; the second robot's functions include b1 and b2; and the third robot's functions include a1, b1, and c1. When the functions of the robots differ, some robots may only be able to accept fixed instruction information, making it impossible to control all robots to perform the same action uniformly based on a single instruction. For example, the first robot may only receive voice instructions, the second robot may only receive text instructions, and the third robot may receive both voice and text instructions. In this case, if the instruction is a voice instruction, only the first and third robots can be controlled, but the second robot cannot be controlled. To enable multiple robots to perform the same action based on the same instruction, it is necessary to perform planning and processing on each parameter data according to standard parameter data.

[0090] Step S1022: Standardize and transform the functional parameter data corresponding to each function to obtain the first parameter data.

[0091] The first parameter data consists of the standard functional parameter data corresponding to the robot, which is the functional parameter data corresponding to the robot after normalization.

[0092] Specifically, when the format of the robot's corresponding functional parameter data is a preset standard format, this functional parameter data is the standard functional parameter data corresponding to that function. When the format of the robot's corresponding functional parameter data is different from the preset standard format, the functional parameter data is normalized to obtain the standard functional parameter data corresponding to that function. All the obtained standard functional parameter data are combined as the first parameter data. The specific combination method can be to set up each set of standard functional parameter data or to merge each set of standard functional parameter data. This application does not limit the specific method.

[0093] More specifically, taking any single functional parameter data as an example, the standardization process of this arbitrary functional parameter data yields the corresponding standard functional parameter data. This can be achieved by converting the format of the arbitrary functional parameter data into a preset standard format. It's worth noting that the standardization process for each functional parameter data is the same as for this arbitrary functional parameter data, and will not be elaborated upon here.

[0094] Step S1023: Based on the function corresponding to each robot and the function category to which each function belongs, determine the target function category corresponding to each robot, obtain the target standard parameter data corresponding to the target function category, and determine the second parameter data based on the target standard parameter data.

[0095] Specifically, the functions corresponding to the standard parameter data are classified to obtain multiple function categories. Each function belongs to a function category, and each function category includes at least one function. When the function categories corresponding to the standard parameter data include function category A, function category B, function category C, and function category D, the functions included in the specific function categories are shown in Table 1 below.

[0096] Table 1:

[0097]

[0098] According to Table 1 above, function category A includes function A1, function A2, function A3 and function A4. Similarly, function category B, function category C and the function applied for in function category C can be obtained.

[0099] Specifically, since the functions included in each robot may differ, after standardizing the functions corresponding to the robots, it is also necessary to standardize the functions not included in the robots to achieve unified management of multiple robots. More specifically, based on the functions corresponding to the robots, the function category to which each function belongs is determined. When there is a function category that includes functions completely different from the functions corresponding to the robots, that function category is the target function category, meaning that the functions corresponding to each robot do not include the functions included in the target function category. For example, when the functions corresponding to robot X1 include functions A1, A2, A3, A4, B1, and B2, referring to Table 1 above, the functions corresponding to the robot do not include the functions included in function categories C and D. Therefore, the target function categories corresponding to this robot are function categories C and D.

[0100] More specifically, after determining the target function category, the target standard parameter data corresponding to the target function category is obtained. At this point, the target standard parameter data is the second parameter data. For example, the target function categories corresponding to the robot X1 mentioned above are function category C and function category D. The standard function parameter data corresponding to each function included in function category C and function category D are combined as the target standard parameter data. The format of the target standard parameter data is a preset standard format.

[0101] Step S1024: Based on the first parameter data and the second parameter data, determine the standard parameter data corresponding to each robot.

[0102] Specifically, for each robot, the first parameter data and the second parameter data form a parameter data group, which is the standard parameter data corresponding to the robot.

[0103] One possible implementation of this application embodiment includes step S1022, where the functional parameter data corresponding to each function is normalized and converted to obtain the first parameter data. Specifically, this may include: determining a first functional category and a second functional category based on the functional category to which each function belongs; wherein each function included in the first functional category belongs to the function corresponding to each robot; and the functions corresponding to the second functional category include both the first and second functions; the first function belongs to the function corresponding to each robot, while the second function does not belong to the function corresponding to each robot. Then, first standard functional parameter data corresponding to each function included in the first functional category is obtained. Second standard functional parameter data corresponding to the first function is obtained. Third standard functional parameter data is determined based on the second standard functional parameter data and the second function; and the first parameter data is determined based on the first and third standard functional parameter data. The third standard functional parameter data is parameter data capable of implementing both the first and second functions.

[0104] Specifically, when a function category includes functions that belong to the robot, that function category is the first function category. When a function category includes functions that partially belong to the robot, that function category is the second function category. In this case, the functions belonging to the robot in the second function category are the first functions, and the functions not belonging to the robot are the second functions. For example, robot X1 includes functions A1, A2, A3, A4, B1, and B2. Referring to the data in Table 1 above, the first function category for robot X1 is function category A, and the second function category is function category B. The first function includes functions B1 and B2, and the second function includes functions B3 and B4.

[0105] More specifically, for the first functional category, the robot possesses all the functions of the first functional category. Therefore, it can directly obtain the first standard functional parameter data corresponding to each function in the first functional category as the standardized parameter data. The format of this first standard functional parameter data is a preset standard format. For example, among the functions corresponding to robot X1 above, the preset standard format functional parameter data corresponding to function A1 is the first standard functional parameter data. Functions A2, A3, and A4 are the same as function A1 above, and will not be described in detail here.

[0106] More specifically, for the second functional category, some functions within this category belong to the robot (i.e., the first function), while others do not (i.e., the second function). During standardization, the third standard functional parameter data can be determined based on the second standard functional parameter data corresponding to the first function and the second function itself. Standardizing the second functional category also allows obtaining the standard functional parameter data corresponding to the second function, and combining this data with the standard parameter data corresponding to the second function yields the third standard functional parameter data. For example, regarding the functions corresponding to robot X1, referring to the data in Table 1 above, the second functional category is functional category B. The first function includes functions B1 and B2, and the second function includes functions B3 and B4. In this case, the standard functional parameter data corresponding to function B3 and function B4 are obtained. The second standard functional parameter data corresponding to functions B1 and B2, and the standard functional parameter data corresponding to functions B3 and B4 are then combined to obtain the third standard functional parameter data.

[0107] Furthermore, the first standard functional parameter data and the third standard functional parameter data are combined to form the first parameter data.

[0108] One possible implementation of this application embodiment is as follows: In the above embodiment, the third standard function parameter data is determined based on the second standard parameter data and the second function. Specifically, it may include: when the second function category is a text processing category, determining whether the second function includes a paragraph processing function and whether the first function includes a short sentence processing function; if the second function includes a paragraph processing function and the first function includes a short sentence processing function, then the third standard parameter data corresponding to the text processing category is determined based on the second standard function parameter data corresponding to the short sentence processing function and the loop function.

[0109] The text processing category includes functions that can process textual information. Specifically, the text processing category includes paragraph processing functions and short sentence processing functions. The paragraph processing function is the function that can process paragraphs in the text, and the short sentence processing function is the ability to process short sentences in the text.

[0110] Specifically, when the robot's function only includes short sentence processing, it means that the robot cannot process long text instructions or perform long text processing. In this case, in order to achieve unified management of multiple robots, the short sentence processing function needs to be standardized so that the robot can process paragraphs and long texts.

[0111] More specifically, a loop function can be added to the standard function parameter data corresponding to the short sentence processing function. Based on the loop function and the short sentence processing function, the robot can process short sentences in the paragraph in a loop to realize the paragraph processing function. At this time, the standard function parameter data and the loop function corresponding to the short sentence processing function constitute the third standard parameter data corresponding to the text processing category.

[0112] More specifically, when the first function does not include sentence processing capabilities, and the second function includes paragraph processing capabilities, the standardization of the text processing function category is similar to the standardization of the target function category, and will not be elaborated here. Furthermore, when the first function includes both sentence and paragraph processing capabilities, and the second function does not include paragraph processing capabilities, the standardization of the text processing function category is similar to the standardization of the first function category described above, and will not be elaborated here. Even further, when the first function includes paragraph processing capabilities, and the second function includes sentence processing capabilities, the standard function parameter data corresponding to the sentence processing capability is obtained, and the function parameter data corresponding to the paragraph processing capability in the first function is replaced with the standard function parameter data corresponding to the sentence processing capability. In this case, the standard function parameter data corresponding to the sentence processing capability is the third standard function parameter data, thus completing the standardization of the text processing function category.

[0113] One possible implementation of this application embodiment involves obtaining target standard parameter data corresponding to the target function category in step S1023, and determining second parameter data based on the target standard parameter data. Specifically, this may include: determining whether the target function category includes software functions; if the target function category includes software functions, obtaining standard function parameter data corresponding to each software function, determining target standard parameter data based on the standard function parameter data corresponding to each software function, and determining second parameter data corresponding to each robot based on the target standard parameter data corresponding to each software function. Here, software functions are functions that do not require external interfaces to implement.

[0114] Specifically, for each robot, since the functions corresponding to the robot may differ, the functions not included in the target function category may include hardware functions, software functions, or both. When the target function category includes software functions, the standard function parameter data corresponding to each software function is obtained, and the obtained standard function parameter data corresponding to each software function is combined into a parameter data group. This parameter data group is the target standard parameter data, which is the second parameter data corresponding to the robot.

[0115] For example, with parameters as shown in Table 1 above, when the functions corresponding to robot X1 include functions A1, A2, A3, A4, B1, and B2, and the functions included in function category C are software functions, the standard function parameter data corresponding to each of functions C, C2, C3, and C4 are obtained respectively, and then the parameter data group composed of each corresponding standard function parameter data is obtained, that is, the parameter data corresponding to function category C. At this time, the parameter data corresponding to function category C is the target standard parameter data, which is the second parameter data corresponding to the robot.

[0116] For example, when the target function category is the Track & Trace system (TTS) category, and the functions included in the TTS category are software functions, the software functions are obtained, including speech-to-text, text-to-speech, and speech synthesis functions. The standard function parameter data corresponding to each of the speech-to-text, text-to-speech, and speech synthesis functions are obtained respectively. Then, the parameter data group composed of the standard function parameter data corresponding to each function is obtained, which is the parameter data corresponding to the TTS category. At this time, the parameter data corresponding to the TTS category is the target standard parameter data, which is also the second parameter data corresponding to the robot.

[0117] One possible implementation of this application includes a method that further comprises: determining whether the target function category includes hardware functions; if the target function category includes hardware functions, then determining the external interface of the hardware functions based on the hardware functions. Here, the hardware function is the function that needs to be implemented through an external interface.

[0118] Specifically, for each robot, when the robot does not include hardware functions in the target function category, it is impossible to implement the hardware functions by changing the parameter data. Therefore, it is necessary to reserve external interfaces for hardware functions to implement the corresponding hardware functions.

[0119] For example, when the hardware function included in the target function category is radio reception, an external radio interface (Medium Interface Connector, MIC) needs to be reserved to implement the radio reception function.

[0120] In step S103, the standard parameter data and SDK corresponding to each robot are encapsulated to obtain the standard SDK corresponding to each robot. Specifically, this may include encapsulating the external interface corresponding to the hardware function, the standard parameter data and SDK corresponding to each robot to obtain the standard SDK corresponding to each robot.

[0121] Specifically, for each robot, the generated standard parameter data of the robot is integrated into the corresponding SDK of the robot. Then, the integrated SDK and the reserved interface are encapsulated to obtain the standard SDK corresponding to each robot. The standard SDK can be connected to the target platform through the interface to realize the unified management of multiple robots through the target platform.

[0122] One possible implementation of this application embodiment, after connecting each standard SDK to the target platform through an interface in step S104, may further include: developing the target platform based on a preset operating environment, and managing the robot connected to the target platform based on the developed target platform. Here, the preset operating environment is an operating environment that allows operation across operating systems, meaning that the operating system can be switched at any time.

[0123] Specifically, the target platform is developed based on a cross-operating system, and the developed target platform can be controlled through any of the operating systems, namely Windows, Linux, and Mac.

[0124] The above embodiments describe a unified platform management method from a process flow perspective. An example is provided here to illustrate the flow of this method. Specifically, refer to... Figure 4 The TTS function category, as shown in the diagram, refers to the category of possessing TTS capabilities. Similarly, the other function categories are not elaborated upon. For each robot, parameter data is acquired. Based on the parameter data, it is determined whether the robot possesses TTS capabilities, i.e., whether the robot's corresponding function includes a TTS function category. If it does, the parameter data corresponding to the TTS function category is directly acquired, and the format of the parameter data corresponding to the TTS function category is converted to a preset standard format, completing the standardization processing of the TTS function category. If it does not, the standard parameter data corresponding to the TTS function category is directly acquired, and this standard parameter data is used as the second target parameter data, completing the standardization processing of the TTS function category. The TTS capability standardization conversion and the custom TTS method shown in the diagram are both examples of TTS function category standardization processing.

[0125] Based on the parameter data, determine whether the robot possesses MIC (Micro-Input Micro-Output) capabilities. This involves checking if the robot's functions include a MIC function category. If so, and the parameter data corresponding to this MIC function category requires standardization, directly obtain the corresponding parameter data and convert its format to a preset standard format, thus completing the standardization process. If the parameter data does not require standardization, use it as the standard parameter data for that MIC function category, completing the standardization process. If not, and an external interface needs to be reserved, reserve the external interface for the MIC function category, completing the standardization process. In the diagram, MIC start / stop standardization is converted to MIC function category standardization.

[0126] Based on the parameter data, determine whether the robot has speech recognition capability (Automatic Speech Recognition, ASR), that is, determine whether the robot's corresponding functions include the ASR function category. For the specific ASR function category standardization process, please refer to the TTS function category standardization process mentioned above.

[0127] Based on the parameter data, determine whether the robot has mobility capabilities, that is, determine whether the robot's corresponding functions include a mobility function category. For the specific process of standardizing mobility function categories, please refer to the above-mentioned MIC function category standardization process.

[0128] Based on the parameter data, determine whether the robot's corresponding functions include the ability to stop moving, that is, determine whether the robot's corresponding functions include the category of stopping moving. For the specific standardization process of the stopping moving function category, please refer to the above-mentioned MIC function category standardization process.

[0129] Based on the parameter data, determine whether the robot's corresponding functions include the ability to acquire battery status, that is, determine whether the robot's corresponding functions include the category of battery status acquisition function. For the specific standardization process of the battery status acquisition function category, please refer to the above-mentioned standardization process of TTS function categories.

[0130] The standardization of the above functions is merely illustrative and is not intended to limit the embodiments of this application. Furthermore, the functions corresponding to the robot include not only those described in the examples above.

[0131] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0132] See Figure 5 This application provides a unified platform management device 20, including: an acquisition module 210, a standardization module 220, an encapsulation module 230, and a connection module 240.

[0133] A unified platform management device 20, the device 20 comprising:

[0134] The acquisition module 210 can be used to acquire multiple parameter data, which are data from the SDK interface corresponding to the robot. The SDK interface is the interface of the SDK required for the robot to implement its functions.

[0135] The standardization module 220 can be used to standardize the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot. The format of the standard parameter data is a preset standard format.

[0136] The encapsulation module 230 can be used to encapsulate based on the standard parameter data and SDK corresponding to each robot to obtain the standard SDK corresponding to each robot.

[0137] The connection module 240 can be used to connect each standard SDK to the target platform through an interface. The target platform is used to manage robots that meet preset conditions. The preset conditions are that the parameter data of the interface between the robot and the target platform is in a preset standard format.

[0138] In one possible implementation of this application embodiment, when the normalization module 220 performs normalization processing on the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot, it can specifically be used for:

[0139] Based on the parameter data corresponding to each robot, determine the function corresponding to each robot, and the function parameter data corresponding to each function;

[0140] The function parameter data corresponding to each function is normalized and transformed to obtain the first parameter data;

[0141] Based on the function corresponding to each robot and the function category to which each function belongs, determine the target function category corresponding to each robot, obtain the target standard parameter data corresponding to the target function category, and determine the second parameter data based on the target standard parameter data. The function category includes at least one function, and the function corresponding to each robot does not include any functions included in the target function category.

[0142] Based on the first parameter data and the second parameter data, the standard parameter data corresponding to each robot is determined.

[0143] In one possible implementation of this application embodiment, when the normalization module 220 performs normalization processing on the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot, it can specifically be used for:

[0144] Based on the function category to which each function belongs, a first function category and a second function category are determined. Each function included in the first function category belongs to the function corresponding to each robot. The functions corresponding to the second function category include the first function and the second function. The first function belongs to the function corresponding to each robot, and the second function does not belong to the function corresponding to each robot.

[0145] Obtain the first standard function parameter data corresponding to each function included in the first function category;

[0146] Obtain the second standard function parameter data corresponding to the first function, and determine the third standard function parameter data based on the second standard function parameter data and the second function. The third standard function parameter data is the parameter data that can realize the first function and the second function.

[0147] The first parameter data is determined based on the first standard functional parameter data and the third standard functional parameter data.

[0148] In one possible implementation of this application embodiment, when the normalization module 220 performs normalization processing on the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot, it can specifically be used for:

[0149] When the second function category is text processing, determine whether the second function includes paragraph processing function and whether the first function includes short sentence processing function;

[0150] If the second function includes paragraph processing and the first function includes short sentence processing, then the third standard parameter data corresponding to the text processing category is determined based on the second standard function parameter data corresponding to the short sentence processing function and the loop function.

[0151] In one possible implementation of this application embodiment, when the normalization module 220 performs normalization processing on the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot, it can specifically be used for:

[0152] Determine whether the target function category includes software functions. Software functions are those that do not need to be implemented through external interfaces.

[0153] If the target function category includes software functions, then obtain the standard function parameter data corresponding to each software function, and determine the target standard parameter data based on the standard function parameter data corresponding to each software function.

[0154] Based on the target standard parameter data corresponding to each software function, determine the second parameter data corresponding to each robot.

[0155] In one possible implementation of this application embodiment, when the normalization module 220 performs normalization processing on the parameter data corresponding to each robot to obtain the standard parameter data corresponding to each robot, it can specifically be used for:

[0156] Determine whether the target function category includes hardware functions. Hardware functions are those that need to be implemented through external interfaces.

[0157] If the target function category includes hardware functions, then the external interface of the hardware functions is determined based on the hardware functions.

[0158] Specifically, when the encapsulation module 230 encapsulates data based on the standard parameter data and SDK corresponding to each robot to obtain the standard SDK corresponding to each robot, it can be used for:

[0159] Based on the external interfaces corresponding to the hardware functions, the standard parameter data corresponding to each robot, and the SDK corresponding to each robot, the standard SDK corresponding to each robot is encapsulated to obtain the standard SDK corresponding to each robot.

[0160] In one possible implementation of this application embodiment, the device 20 further includes:

[0161] The development module is used to develop for the target platform based on a preset runtime environment, which is a runtime environment that can operate across operating systems.

[0162] The management module is used to manage robots connected to the target platform based on the developed target platform.

[0163] This application also provides a terminal device, see [link to relevant documentation] Figure 6 The terminal 300 may include: at least one processor 310, a memory 320, and a computer program stored in the memory 320 and executable on the at least one processor 310. When the processor 310 executes the computer program, it implements the steps in any of the above method embodiments, for example... Figure 1 Steps S101 to S104 in the illustrated embodiment. Alternatively, when the processor 310 executes the computer program, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 5 The functions of modules 210 to 240 are shown.

[0164] For example, a computer program may be divided into one or more modules / units, one or more of which are stored in memory 320 and executed by processor 310 to complete this application. One or more modules / units may be a series of computer program segments capable of performing a specific function, which describe the execution process of the computer program in terminal device 300.

[0165] Those skilled in the art will understand that Figure 6 This is merely an example of a terminal device and does not constitute a limitation on the terminal device. It may include more or fewer components than shown, or combine certain components, or different components, such as input / output devices, network access devices, buses, etc.

[0166] The processor 310 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0167] The memory 320 can be an internal storage unit of the terminal device or an external storage device, such as a plug-in hard drive, a smart media card (SMC), a secure digital card (SD), or a flash card. The memory 320 is used to store computer programs and other programs and data required by the terminal device. The memory 320 can also be used to temporarily store data that has been output or will be output.

[0168] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0169] The unified platform management method provided in this application can be applied to terminal devices such as electronic devices, computers, wearable devices, in-vehicle devices, tablet computers, laptop computers, netbooks, personal digital assistants (PDAs), augmented reality (AR) / virtual reality (VR) devices, and mobile phones. This application does not impose any restrictions on the specific type of terminal device.

[0170] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various embodiments of the above methods.

[0171] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the various embodiments of the above methods.

[0172] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographic device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0173] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0175] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0176] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0177] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A unified platform management method, characterized in that, The method includes: Acquire multiple parameter data, wherein the parameter data is data of the SDK interface corresponding to the robot, and the SDK interface is the interface of the SDK required for the robot to implement its functions; The parameter data for each robot is standardized to obtain standard parameter data for each robot. This includes determining the function of each robot and the function parameter data for each function based on the parameter data. The function parameter data for each function is then standardized to obtain first parameter data. The confirmation of the first parameter data includes determining a first function category and a second function category based on the function category to which each function belongs. Each function in the first function category belongs to the function corresponding to each robot. The functions in the second function category include both a first function and a second function. The first function belongs to the function corresponding to each robot, and the second function does not belong to the function corresponding to each robot. First standard function parameter data is obtained for each function in the first function category. Second standard function parameter data is obtained for the first function. Third standard function parameter data is determined based on the second standard function parameter data and the second function. The third standard function parameter data is the parameter data that enables both the first and second functions. Finally, the first parameter data is determined based on the first standard function parameter data and the third standard function parameter data. Based on the function corresponding to each robot and the function category to which each function belongs, determine the target function category corresponding to each robot, obtain the target standard parameter data corresponding to the target function category, and determine the second parameter data based on the target standard parameter data. The function category includes at least one function, and the function corresponding to each robot does not include any function included in the target function category. Based on the first parameter data and the second parameter data, standard parameter data corresponding to each robot is determined, and the format of the standard parameter data is a preset standard format; Based on the standard parameter data corresponding to each robot and the SDK corresponding to each robot, the data is encapsulated to obtain the standard SDK corresponding to each robot; Each standard SDK is connected to the target platform via an interface. The target platform is used to manage robots that meet preset conditions, namely, the parameter data of the interface between the robot and the target platform is in a preset standard format.

2. The method according to claim 1, characterized in that, The step of determining the third standard function parameter data based on the second standard function parameter data and the second function includes: When the second function category is a text processing category, determine whether the second function includes a paragraph processing function and whether the first function includes a short sentence processing function; If the second function includes a paragraph processing function, and the first function includes a short sentence processing function, then based on the second standard function parameter data corresponding to the short sentence processing function and the loop function, the third standard parameter data corresponding to the text processing category is determined.

3. The method according to claim 1, characterized in that, The step of obtaining the target standard parameter data corresponding to the target function category, and determining the second parameter data based on the target standard parameter data, includes: Determine whether the target function category includes software functions, where the software functions are functions that do not need to be implemented through external interfaces; If the target function category includes software functions, then the standard function parameter data corresponding to each software function is obtained, and the target standard parameter data is determined based on the standard function parameter data corresponding to each software function. Based on the target standard parameter data corresponding to each software function, the second parameter data corresponding to each robot is determined.

4. The method according to claim 3, characterized in that, The method further includes: Determine whether the target function category includes hardware functions, where the hardware functions are functions that need to be implemented through external interfaces; If the target function category includes hardware functions, then the external interface of the hardware functions is determined based on the hardware functions. Specifically, based on the standard parameter data corresponding to each robot and the SDK corresponding to each robot, the standard SDK corresponding to each robot is encapsulated to obtain the standard SDK corresponding to each robot, including: Based on the external interfaces corresponding to the hardware functions, the standard parameter data corresponding to each robot, and the SDK corresponding to each robot, the standard SDK corresponding to each robot is encapsulated to obtain the standard SDK corresponding to each robot.

5. The method according to claim 1, characterized in that, The process of connecting each standard SDK to the target platform via an interface also includes: The target platform is developed based on a preset operating environment, which is an operating environment that can operate across operating systems. Based on the developed target platform, the robots connected to the target platform are managed.

6. A unified platform management device, characterized in that, The device includes: The acquisition module is used to acquire multiple parameter data, which are data from the SDK interface corresponding to the robot. The SDK interface is the interface of the SDK required for the robot to implement its functions. A normalization module is used to normalize the parameter data corresponding to each robot to obtain standard parameter data corresponding to each robot. This includes determining the function corresponding to each robot and the function parameter data corresponding to each function based on the parameter data corresponding to each robot; performing normalization transformation on the function parameter data corresponding to each function to obtain first parameter data, wherein the confirmation of the first parameter data includes determining a first function category and a second function category based on the function category to which each function belongs, wherein each function included in the first function category belongs to the function corresponding to each robot, and the functions corresponding to the second function category include a first function and a second function, wherein the first function belongs to the function corresponding to each robot, and the second function does not belong to the function corresponding to each robot; obtaining first standard function parameter data corresponding to each function included in the first function category; obtaining second standard function parameter data corresponding to the first function; determining third standard function parameter data based on the second standard function parameter data and the second function, wherein the third standard function parameter data is parameter data that can realize the first function and the second function; and determining the first parameter data based on the first standard function parameter data and the third standard function parameter data. Based on the function corresponding to each robot and the function category to which each function belongs, determine the target function category corresponding to each robot, obtain the target standard parameter data corresponding to the target function category, and determine the second parameter data based on the target standard parameter data. The function category includes at least one function, and the function corresponding to each robot does not include any function included in the target function category. Based on the first parameter data and the second parameter data, standard parameter data corresponding to each robot is determined, and the format of the standard parameter data is a preset standard format; The encapsulation module is used to encapsulate the standard parameter data corresponding to each robot and the SDK corresponding to each robot to obtain the standard SDK corresponding to each robot. The connection module is used to connect each standard SDK to the target platform through an interface. The target platform is used to manage robots that meet preset conditions, namely, the parameter data of the interface between the robot and the target platform is in a preset standard format.

7. An electronic device, characterized in that, The electronic device includes: At least one processor; Memory; At least one application, wherein the at least one application is stored in memory and configured to be executed by at least one processor, said at least one application being configured to: perform the unified platform management method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed in the computer, the computer is instructed to perform the unified platform management method according to any one of claims 1 to 5.

Images