WO2022198512A1 - 错误码管理方法、故障提示方法、设备、系统及存储介质 - Google Patents

错误码管理方法、故障提示方法、设备、系统及存储介质 Download PDF

Info

Publication number
WO2022198512A1
WO2022198512A1 PCT/CN2021/082789 CN2021082789W WO2022198512A1 WO 2022198512 A1 WO2022198512 A1 WO 2022198512A1 CN 2021082789 W CN2021082789 W CN 2021082789W WO 2022198512 A1 WO2022198512 A1 WO 2022198512A1
Authority
WO
WIPO (PCT)
Prior art keywords
error code
user account
information
authorization information
sdk
Prior art date
Application number
PCT/CN2021/082789
Other languages
English (en)
French (fr)
Inventor
黄昌彬
陈超彬
Original Assignee
深圳市大疆创新科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市大疆创新科技有限公司 filed Critical 深圳市大疆创新科技有限公司
Priority to PCT/CN2021/082789 priority Critical patent/WO2022198512A1/zh
Publication of WO2022198512A1 publication Critical patent/WO2022198512A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
    • G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data

Definitions

  • the present application relates to the field of unmanned aerial vehicles, and in particular, to an error code management method, a fault prompting method, equipment, system and storage medium.
  • the health monitoring of each module inside the drone is mainly realized through its own health management system, and third-party developers who want to monitor the health of SDK devices with their own developed applications need to redesign a A set of health management system and supporting development of an interactive system for healthy interaction.
  • third-party developers it is necessary to pay attention to the health management system of the SDK device and the health management system of the drone. The development is difficult and the workload is large, and the user Bad experience.
  • the embodiments of the present application provide an error code management method, a fault prompting method, a device, a system, and a storage medium, which aim to reduce the difficulty of developing a health management system for SDK devices.
  • an embodiment of the present application provides an error code management method, including:
  • the error code application request includes the user account, version number, the first application number of error codes, and the first fault prompt information list;
  • the error code management method by obtaining an error code application request including a user account, the number of applied error codes, a list of fault prompt information, and a version number, and according to the number of applied error codes from the drone-based
  • the error code is allocated to the user account in the error code pool determined by the health management system, and then the error code authorization information of the user account is generated based on the assigned error code, the list of the fault prompt information and the version number, and finally to the terminal device corresponding to the user account.
  • the embodiment of the present application also provides a fault prompting method, including:
  • the SDK device is mounted on the drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone;
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and the second version number, and the error code pool determined according to the health management system of the drone includes all the error code in the matching table;
  • the current error code is located in the matching relationship table, and the first version number is the same as the second version number, the current error code is sent to the terminal device paired with the SDK device for all The terminal device displays fault prompt information corresponding to the current error code.
  • the current error code output by the fault monitoring component in the SDK device is obtained, the first version number of the current error code and the user account to which the current error code belongs, and then the user account of the user account is obtained.
  • Error code authorization information if the first version number is the same as the second version number in the error authorization information, and the current error code is in the matching relationship table in the error authorization information, then send the current error code to the terminal device paired with the SDK device, Make the terminal device display the fault prompt information corresponding to the current error code, thereby prompting the user that the SDK device is faulty, because the error code authorization information includes the authorized error code, and the authorized error code is located in the health management system of the drone.
  • the error code pool does not need to redesign and develop the health management system of the SDK device, which greatly reduces the development difficulty of the health management system of the SDK device.
  • the embodiment of the present application also provides a fault prompting method, including:
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and the second version number, and the error code pool determined according to the health management system of the drone includes all the error code in the matching table;
  • the fault prompt information corresponding to the current error code is obtained from the error code authorization information, And display the fault prompt information.
  • the fault prompt method obtaineds the current error code, the first version number and the user account sent by the SDK device, and obtains the error code authorization information of the user account, and then in the first version number and the error authorization information
  • the second version number is the same, and the current error code is located in the matching relationship table in the error authorization information, then the fault prompt information corresponding to the current error code is obtained from the error code authorization information, and the fault prompt information is displayed, thereby prompting the user.
  • the SDK device fails. Since the error code authorization information includes the authorized error code, and the authorized error code is located in the error code pool determined according to the health management system of the drone, there is no need to redesign and develop the health management system of the SDK device. , which greatly reduces the development difficulty of the health management system of the SDK device.
  • the embodiments of the present application further provide a server, where the server is used to communicate and connect with a terminal device, the terminal device is used for pairing with an SDK device, the SDK device is mounted on the drone, and the terminal device is used for pairing.
  • the SDK device is installed with an application program developed based on the SDK framework of the drone, and the server includes a memory and a processor;
  • the memory is used to store computer programs
  • the processor is configured to execute the computer program and implement the following steps when executing the computer program:
  • the error code application request includes the user account, version number, the first application number of error codes, and the first fault prompt information list;
  • the embodiments of the present application also provide an SDK device, the SDK device is mounted on a drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone, the The SDK device is used for pairing with a terminal device, and the terminal device is used for communication and connection with the server, and the SDK device includes a memory and a processor;
  • the memory is used to store computer programs
  • the processor is configured to execute the computer program and implement the following steps when executing the computer program:
  • the SDK device is mounted on the drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone;
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and the second version number, and the error code pool determined according to the health management system of the drone includes all the error code in the matching table;
  • the current error code is located in the matching relationship table, and the first version number is the same as the second version number, the current error code is sent to the terminal device paired with the SDK device for all The terminal device displays fault prompt information corresponding to the current error code.
  • the embodiments of the present application further provide a terminal device, the terminal device is used for communication and connection with the server and for pairing with an SDK device, the SDK device is mounted on a drone, and the SDK device is An application program developed based on the SDK framework of the drone is installed, and the terminal device includes a memory, a processor and a display device;
  • the memory is used to store computer programs
  • the processor is configured to execute the computer program and implement the following steps when executing the computer program:
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and the second version number, and the error code pool determined according to the health management system of the drone includes all the error code in the matching table;
  • the fault prompt information corresponding to the current error code is obtained from the error code authorization information, and displaying the fault prompt information through the display device.
  • the embodiments of the present application also provide an error code management system
  • the error code management system includes the above-mentioned server, the above-mentioned SDK device, and the above-mentioned terminal device, the server and The SDK device is communicatively connected, the SDK device is mounted on the drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone, and the SDK device is paired with the terminal device.
  • an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the above-mentioned Error code management method or fault prompt method.
  • FIG. 1 is a schematic diagram of a scenario for implementing an error code management method provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of steps of an error code management method provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of data interaction among a display device, a server, a terminal device, and an SDK device in an embodiment of the present application;
  • FIG. 4 is a schematic flowchart of steps of a fault prompting method provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of data interaction between a server, a terminal device, and an SDK device in an embodiment of the present application
  • FIG. 6 is a schematic diagram of data interaction between the SDK device, the terminal device, and the server in the embodiment of the present application;
  • FIG. 7 is a schematic diagram of data interaction among SDK devices, terminal devices, servers, and drones in an embodiment of the present application;
  • FIG. 8 is a schematic flowchart of steps of another fault prompting method provided by an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of the structure of a server provided by an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of the structure of a SDK device provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural block diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of the structure of an error code management system provided by an embodiment of the present application.
  • the embodiment of the present application provides an error code management method.
  • the number of error codes is allocated to the user account from the error code pool determined by the drone-based health management system, and then based on the assigned error code, the list of the fault prompt information and the version number, the error code authorization information of the user account is generated, and finally Send the generated error code authorization information to the terminal device corresponding to the user account, so that the terminal device stores the error code authorization information, and sends the error code authorization information to the SDK device paired with the terminal device, so that the SDK device can be configured based on the error code authorization information.
  • Error code the SDK device can be connected to the health management system of the drone, and there is no need to redesign and develop the health management system of the SDK device, which greatly reduces the development difficulty of the health management system of the SDK device.
  • FIG. 1 is a schematic diagram of a scenario for implementing the error code management method provided by the embodiment of the present application.
  • the scene includes a server 100, a terminal device 200, a drone 300, and an SDK device 400.
  • the server 100 is connected to the terminal device 200 in communication
  • the SDK device 400 is mounted on the drone 300
  • the SDK device 400 is connected to the terminal device 200.
  • the terminal device 200 is paired and connected to realize data exchange
  • the SDK device 400 is installed with an application program developed based on the SDK framework of the drone, so that the SDK device 400 can be adapted to the drone 300 .
  • the SDK device 400 is a third-party camera installed with an application program developed based on the SDK framework of the drone.
  • the UAV 300 includes a body 310 , a power system 320 and a control system (not shown in FIG. 1 ) disposed on the body 310 , and the power system 320 is used to provide moving power for the UAV 300 .
  • the UAV 300 may include a rotary-wing UAV, such as a single-rotor UAV, a dual-rotor UAV, a quad-rotor UAV, a hexa-rotor UAV, an octa-rotor UAV, or a fixed-wing UAV.
  • the unmanned aerial vehicle can also be a combination of a rotary-wing type and a fixed-wing unmanned aerial vehicle, which is not limited here.
  • the UAV 300 includes a health management system, which is used to monitor the health of the internal components or modules of the UAV 300 during the entire life cycle of the UAV 300 being started.
  • the component or module registers the error code through internal registration, and pushes the corresponding error code to the terminal device 200 in a specific scenario (failure), and the terminal device 200 stores the error code registered by the internal components or modules of the drone 300 and the corresponding fault prompt information. Therefore, when the terminal device 200 receives the error code pushed by the drone 300, it obtains the fault prompt information corresponding to the error code from the memory, and displays the fault prompt information.
  • the power system 320 may include one or more propellers 321 , one or more motors 322 corresponding to the one or more propellers, and one or more electronic governors (referred to as ESCs for short).
  • the motor 322 is connected between the electronic governor and the propeller 321, and the motor 322 and the propeller 321 are arranged on the body 310 of the UAV 300; the electronic governor is used to receive the driving signal generated by the control system, and provide according to the driving signal Driving current is supplied to the motor 322 to control the rotational speed of the motor 322 .
  • the motor 322 is used to drive the propeller 321 to rotate, thereby providing power for the movement of the UAV 300, and the power enables the UAV 300 to realize the movement of one or more degrees of freedom.
  • the drone 300 may rotate about one or more axes of rotation.
  • the above-mentioned rotation axes may include a roll axis, a yaw axis, and a pitch axis.
  • the motor 322 may be a DC motor or an AC motor.
  • the motor 322 may be a brushless motor or a brushed motor.
  • the control system may include a processor and a sensing system.
  • the sensing system is used to measure the attitude information of the UAV 300, that is, the position information and state information of the UAV 300 in space, such as three-dimensional position, three-dimensional angle, three-dimensional velocity, three-dimensional acceleration, and three-dimensional angular velocity.
  • the sensing system may include at least one of a gyroscope, an ultrasonic sensor, an electronic compass, an inertial measurement unit (Inertial Measurement Unit, IMU), a visual sensor, a global navigation satellite system, a barometer, and other sensors.
  • the global navigation satellite system may be the Global Positioning System (GPS).
  • the processor is used to control the movement of the unmanned aerial vehicle 300, for example, the movement of the unmanned aerial vehicle 300 can be controlled according to the attitude information measured by the sensing system. It should be understood that the processor can control the drone 300 according to pre-programmed instructions.
  • the server 100 obtains an error code application request, and the error code application request includes the user account, the version number, the first application number of the error code, and the first fault prompt information list;
  • the error code is assigned to the user account in the error code pool, and the error code in the preset error code pool is determined according to the health management system of the drone; according to the first fault prompt information list, the error code assigned to the user account and the version number, generate the error code authorization information of the user account; send the error code authorization information to the terminal device 200 corresponding to the user account, the terminal device 200 stores the error code authorization information, and sends the error code authorization information to the SDK device 400,
  • the SDK device 400 stores the error code authorization information, and configures the error code according to the error code authorization information.
  • the SDK device 400 configures the error code of the fault monitoring component in the SDK device according to the error code authorization information, so that when the fault monitoring component detects a fault, it can output the corresponding error code of the configuration; the SDK device 400 obtains the fault monitoring The current error code output by the component, and obtain the first version number of the current error code and the user account to which the current error code belongs; obtain the error code authorization information of the user account, and the error authorization information includes the error code and the fault prompt information.
  • the matching relationship table and the second version number, the error code pool determined according to the health management system of the drone includes the error codes in the matching relationship table; if the current error code is located in the matching relationship table, and the first version number is the same as the second version number If the number is the same, the current error code is sent to the terminal device 200 paired with the SDK device.
  • the terminal device 200 obtains the fault prompt information corresponding to the current error code from the error code authorization information stored locally or in the cloud, and displays the obtained fault prompt. information.
  • the terminal device 200 may include but is not limited to: smart phone/mobile phone, tablet computer, personal digital assistant (PDA), desktop computer, media content player, video game station/system, virtual reality system, augmented reality system, wearable devices (eg, watches, glasses, gloves, headwear (eg, hats, helmets, virtual reality headsets, augmented reality headsets, head mounted devices (HMDs), headbands), pendants, armbands, leg loops, shoes, vest), gesture recognition device, microphone, any electronic device capable of providing or rendering image data, or any other type of device.
  • the terminal device 200 may be a handheld terminal, and the terminal device 200 may be portable.
  • the terminal device 200 may be carried by a human user. In some cases, the end device 200 may be remote from the human user, and the user may control the end device 200 using wireless and/or wired communications.
  • the error code management method provided by the embodiment of the present application will be described in detail with reference to the scenario in FIG. 1 .
  • the scenario in FIG. 1 is only used to explain the error code management method provided by the embodiment of the present application, but does not constitute a limitation on the application scenario of the error code management method provided by the embodiment of the present application.
  • FIG. 2 is a schematic flowchart of steps of an error code management method provided by an embodiment of the present application.
  • the error code management method can be applied to the server to reduce the development difficulty of the health management system of the SDK device.
  • the error code management method may include steps S101 to S104.
  • Step S101 obtaining an error code application request.
  • the error code application request includes the user account, the version number, the first application number of error codes, and the first fault prompt information list.
  • the display device displays the error code application page, and then obtains the first application number and the first fault prompt information list of the error codes entered by the user on the error code application page; in response to the user's error code application page
  • the trigger operation of the confirm application icon in the generates an error code application request according to the user account of the application error code, version number, the number of the first application and the first fault prompt information list, and then sends the error code application request to the server.
  • the number of pieces of fault prompt information in the first fault prompt information list is the same as the number of first applications for error codes, and the trigger operation includes a touch operation of the user's finger on the confirmation application icon, a mouse click operation, and the like.
  • the display device displays an error code application page, and then obtains the first application number of error codes entered by the user on the error code application page, the first fault prompt information list, and the language category of the fault prompt information;
  • the user triggers the operation of the confirmation application icon on the error code application page, and generates an error code application request according to the user account, version number, language category, number of the first application and the list of the first fault prompt information for the application error code, and then Send an error code request to the server.
  • the language category selected during registration of the user account applying for the error code is obtained, and according to User account, language category, number of first applications, and first fault prompt information list, generate an error code application request, and then send an error code application request to the server.
  • the error code application page includes an icon for establishing a matching relationship between the error code and the fault prompt information
  • the display device displays a pop-up window for establishing a matching relationship in response to a user triggering an operation on the established icon, and the matching relationship is established.
  • the pop-up window displays part or all of the error codes opened by the health management system of the drone; obtains the error codes and fault prompt information entered by the user in the matching relationship establishment pop-up window; responds to the confirmation icon in the user matching relationship establishment pop-up window
  • the triggering operation based on the input error code and fault prompt information, generates a first fault prompt information list.
  • the matching relationship establishment pop-up window includes matching relationship input boxes, and the number of matching relationship input boxes is the same as the number of the first application for the error code input by the user, that is, one error code corresponds to one fault prompt message.
  • a user account before applying for an error code to the server, a user account needs to be registered.
  • the display device displays the account registration page, and obtains the user account and identity information to be registered entered by the user on the account registration page; account and identity information, generate an account registration request, and send the account registration request to the server; the server obtains the account registration request, and real-names the user account to be registered in the account registration request according to the identity information in the account registration request Authentication; if the user account to be registered has passed the real-name authentication, the user account to be registered will be written into the account database to complete the account registration; the identity information and authority information of the registered user account will be generated.
  • the identity information is used to uniquely identify the registered user account, and the identity information may include app-id, app-key, and app_level, and the authority information is used to describe the authority of the registered user account, including that the registered user account may
  • the number of error codes applied for and the language types supported by the fault prompt information, the number of error codes that can be applied for and the language types supported by the fault prompt information corresponding to different permission levels are different.
  • the display device displays a permission elevation application page, and obtains the user account, password information and target permission level of the permission to be elevated entered by the user on the permission elevation application page; in response to the user's confirmation icon on the permission elevation application page
  • the triggering operation according to the user account, password information and target permission level to be elevated, generate a permission elevation request, and send the permission elevation request to the server.
  • the server obtains a permission elevation application request, and verifies the user account and password information to be elevated in the permission elevation application request;
  • the current privilege level of the elevated user account is elevated to the target privilege level.
  • Level 1 For example, there are 5 permission levels in total, which are Level 1, Level 2, Level 3, Level 4, and Level 5. Level 1 is the highest and Level 5 is the lowest.
  • the current permission level of the user account to be upgraded is Level 4. If it is upgraded to Level 2, that is, the target permission level is Level 2, when the user account and password information of the user account to be upgraded is verified, the current permission level of the user account to be upgraded will be upgraded from Level 4 to Level 2.
  • the current authority level of the user account whose authority is to be upgraded is obtained; when the difference between the target authority level and the current authority level is less than or equal to a preset threshold , upgrade the current authority level of the user account whose authority is to be upgraded to the target authority level; if the difference between the target authority level and the current authority level is greater than the preset threshold, the current authority level of the user account whose authority is to be upgraded is upgraded by two permissions grade.
  • the preset threshold may be set based on the actual situation, which is not specifically limited in this embodiment of the present application. For example, the preset threshold is 2.
  • Step S102 Allocate an error code to the user account from a preset error code pool according to the first number of applications.
  • the error codes in the preset error code pool are determined according to the health management system of the drone, and the preset error code pool includes part or all of the error codes opened by the health management system of the drone.
  • the health management system is used for The health monitoring of the internal components or modules of the drone is performed during the entire life cycle of the drone.
  • the internal components or modules of the drone register error codes through internal registration, and in a specific scenario (failure)
  • the corresponding error code is pushed down to the terminal device.
  • the terminal device stores the error codes registered by the internal components or modules of the drone and the corresponding fault prompt information. Therefore, when the terminal device receives the error code pushed by the drone, Obtain the fault prompt information corresponding to the error code from the memory, and display the fault prompt information.
  • the permission information of the user account is obtained, and the number of error codes corresponding to the permission information is obtained; if the number of the first application is less than or equal to the number of error codes, the user account is allocated from the preset error code pool.
  • the error code of the first application number if the number of the first application is greater than the number of error codes, it will push a permission promotion prompt message to the display device, informing the user that the number of error codes applied by the user does not meet the permission level of the user account and needs to be upgraded
  • the number of error codes corresponding to the permission information is the number of error codes that can be applied for under the current permission level of the user account.
  • allocating the error codes of the first application number to the user account from the preset error code pool may include: randomly selecting non-repeated error codes from the preset error code pool, and assigning the selected error codes to the user account. Allocated to the user account until the number of allocated error codes reaches the first application number. Or, sort each error code in the preset error code pool according to the order of the size of the error code to obtain an error code sorting queue, and then start from the first error code in the error code sorting queue, and sequentially sort the error codes into the queue. The error codes in are allocated to the user account until the number of allocated error codes reaches the number of the first application.
  • Step S103 Generate error code authorization information for the user account according to the first fault prompt information list, the error code assigned to the user account, and the version number.
  • the error code authorization information of the user account includes the user account, the error code, the fault prompt information, the matching relationship table between the error code and the fault prompt information, the version number of the matching relationship table, and the language category of the fault prompt information.
  • the language category includes Chinese, English, German, French, Spanish, Korean, Japanese, Thai, Arabic, etc.
  • the assigned error codes are matched with the fault prompt information from the first fault prompt information list to generate a matching relationship table between the error codes and the fault prompt information; the version number of the matching relationship table is updated based on the version number , and determine the matching relationship table and the updated version number as the error code authorization information.
  • randomly select a piece of fault prompt information from the first fault prompt information list and randomly assign the selected fault prompt information to any error code, until each error code matches a piece of fault prompt information, and The fault prompt information matched by each error code is different.
  • the first fault prompt information list includes fault prompt information 1, fault prompt information 2, and fault prompt information 3, and the allocated error codes include error code A, error code B, and error code C, then the fault prompt information 1 is matched to the error Code B, match the fault prompt information 2 to the error code A, and match the fault prompt information 3 to the error code C, and obtain the matching relationship table between the error code and the fault prompt information.
  • the first fault prompt information list includes a matching relationship between error codes and fault prompt information. Therefore, the first fault prompt information list may be determined as a matching relationship table between error codes and fault prompt information , and generate the version number of the matching table.
  • Step S104 Send the error code authorization information to the terminal device corresponding to the user account for storage.
  • the server sends the error code authorization information to the terminal device corresponding to the user account.
  • the terminal device After receiving the error code authorization information, the terminal device stores the error code authorization information, and sends the error code authorization information to the SDK device that matches the terminal device.
  • the SDK device After receiving the error code authorization information, the SDK device configures the error code according to the error code authorization information, so that the SDK device can use the error code of the drone's health management system.
  • the user when the user wants to update the error code of the SDK device configuration, the user can re-apply for the error code from the server.
  • the display device displays the error code update page, and obtains the target user account of the error code to be updated and the error code update information entered by the user on the error code update page; Trigger the operation, generate an error code update request, and send the error code update request to the server, and the server will update the error code authorization information of the target user account based on the error code update request.
  • updating the error code authorization information includes at least one of adding, reducing or modifying the error code in the error code authorization information, and modifying the error prompt information in the error code authorization information.
  • the server obtains an error code update request, and the error code update request includes the target user account of the error code to be updated, the error code update information; the error code authorization information of the target user account is updated according to the error code update information; The updated error code authorization information is sent to the terminal device corresponding to the target user account, so that the terminal device can update the locally stored error code authorization information, and send the updated error code authorization information to the SDK device.
  • the SDK device is based on the updated error code authorization information. Error code authorization information, reconfigure the error code. Wherein, each time the error code authorization information is updated, the version number of the matching relationship table in the error code authorization information is updated.
  • the error code update information includes the third application number of error codes and the second fault prompt information list
  • the method of updating the error code authorization information of the target user account according to the error code update information may be: according to the third application The number of error codes is re-allocated to the user account from the preset error code pool; the error code authorization information of the target user account is updated according to the re-assigned error code and the second fault prompt information list.
  • the first fault prompt information list is different from the second fault prompt information list; or, if the number of the first application is greater than the third application number, the first fault prompt information list is the same as that of the second fault prompt information list.
  • the second fault prompt information list is the same; or, the number of first applications is equal to the number of third applications, and the first fault prompt information list is different from the second fault prompt information list.
  • the error code update information includes the target error code to be deleted, then the server deletes the target error code in the error code authorization information of the target user account and the fault prompt information corresponding to the target error code, and updates the matching relationship table. version number.
  • the error code update information includes the target error code to be added and the fault prompt information corresponding to the target error code, and the server writes the target error code and the fault prompt information corresponding to the target error code into the error code authorization information of the target user account, And update the version number of the matching table.
  • the error code update information includes the first error code before modification and the second error code after modification, and both the first error code and the second error code are located in the error code authorization information of the target user account, then the target The first error code and the second error code in the error code authorization information of the user account are exchanged, and the version number of the matching relationship table is updated.
  • the error code update information includes the first fault prompt information before modification and the modified second fault prompt information, then replace the first fault prompt information in the error code authorization information of the target user account with the second fault prompt information , and update the version number of the matching table.
  • the error code update information includes the first fault prompt information before modification and the modified second fault prompt information, and both the first fault prompt information and the second prompt information are located in the error code authorization information of the target user account, then The first fault prompt information and the second fault prompt information in the error code authorization information of the target user account are exchanged, and the version number of the matching relationship table is updated.
  • FIG. 3 is a schematic diagram of data interaction among the display device, the server, the terminal device, and the SDK device in the embodiment of the present application.
  • the display device sends an account registration request to the server, and the server registers based on the account. Request to generate the identity information and permission information of the user account, then the display device sends an error code application request to the server, the server generates error code authorization information based on the error code application request, and sends the error code authorization information to the terminal device, and the terminal device stores the error code Authorization information, and send the error code authorization information to the SDK device, and the SDK device configures the error code according to the error code authorization information.
  • FIG. 4 is a schematic flowchart of steps of a fault prompting method provided by an embodiment of the present application.
  • the fault prompt method can be applied to SDK devices.
  • the fault prompting method may include steps S201 to S204.
  • Step S201 Obtain the current error code output by the fault monitoring component in the SDK device.
  • the SDK device is mounted on the drone, and the SDK device is installed with an application developed based on the SDK framework of the drone.
  • the fault monitoring component is used to perform fault monitoring on each component or module in the SDK device or some components or modules in the drone during the entire life cycle of the SDK device being mounted on the drone and starting, that is, fault monitoring.
  • the component detects that each component or module in the SDK device or some components or modules in the drone is faulty, it will output the error code corresponding to the fault.
  • Step S202 Obtain the first version number of the current error code and the user account to which the current error code belongs.
  • the first version number of the current error code is previously configured by the SDK device based on the error code authorization information, and the user account to which the current error code belongs is also configured by the previous SDK device based on the error code authorization information.
  • Step S203 Acquire error code authorization information of the user account.
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and a second version number
  • the error code pool determined according to the health management system of the drone includes the error codes in the matching relationship table, and the error code pool Including part or all of the error codes opened by the health management system of the drone.
  • the error code authorization information is stored in the memory of the SDK device, and the error code authorization information of the user account can be obtained from the memory of the SDK device. Or, obtain the error code authorization information of the user account from the server. By storing the error code authorization information locally, the error code authorization information of the user account can be quickly obtained, and the latest error code authorization information of the user account can be obtained from the server.
  • an acquisition request for error code authorization information is sent to the terminal device paired with the SDK device, so that the terminal device forwards the acquisition request to the server, so that the server issues the corresponding error to the terminal device based on the user account in the acquisition request.
  • code authorization information obtain the error code authorization information sent by the terminal device.
  • an acquisition request for error code authorization information is sent to the drone, so that the drone can forward the acquisition request to the server, so that the server can issue the corresponding error code authorization to the drone based on the user account in the acquisition request. information; get the error code authorization information sent by the drone.
  • Step S204 if the current error code is located in the matching relationship table, and the first version number is the same as the second version number, send the current error code to the terminal device paired with the SDK device, For the terminal device to display the fault prompt information corresponding to the current error code.
  • the SDK device sends the current error code to the terminal device paired with the SDK device, and the terminal device receives the current error code.
  • the fault prompt information corresponding to the current error code is obtained from the error authorization information stored locally or in the cloud, and the fault prompt information corresponding to the current error code is displayed.
  • FIG. 5 is a schematic diagram of data interaction among a server, a terminal device, and an SDK device in an embodiment of the present application.
  • the display device sends an error code application request to the server.
  • the server generates error code authorization information based on the error code application request, and sends the error code authorization information to the terminal device.
  • the terminal device stores the error code authorization information and sends the error code authorization information to the SDK device.
  • Send the error code authorization information, the SDK device configures the error code according to the error code authorization information, and the SDK device intercepts the error code.
  • the matching relationship table in the authorization information sends an error code to the terminal device, and the terminal device obtains the fault prompt information corresponding to the error code from the error code authorization information, and displays the fault prompt information.
  • FIG. 6 is a schematic diagram of data interaction among the SDK device, the terminal device, and the server in the embodiment of the present application.
  • the SDK device intercepts the error code and sends an error code authorization information acquisition request to the terminal device, the terminal device forwards the error code authorization information acquisition request to the server, and the server sends the terminal device based on the error code authorization information acquisition request.
  • Send the error code authorization information the terminal device forwards the error code authorization information to the SDK device, and determines whether the version number of the intercepted error code is the same as the version number in the error code authorization information, and whether the intercepted error code is in the error code authorization information.
  • Relationship table if the version number of the intercepted error code is the same as the version number in the error code authorization information, and the intercepted error code is located in the matching relationship table in the error code authorization information, the error code is sent to the terminal device, and the terminal device displays The error message corresponding to the error code.
  • FIG. 7 is a schematic diagram of data interaction among SDK devices, terminal devices, servers, and drones in an embodiment of the present application.
  • the SDK device intercepts the error code and sends an error code authorization information acquisition request to the drone.
  • the drone forwards the error code authorization information acquisition request to the server.
  • the server Based on the error code authorization information acquisition request, the server sends the The drone sends the error code authorization information, the drone forwards the error code authorization information to the SDK device, and the SDK device determines whether the version number of the intercepted error code is the same as the version number in the error code authorization information, and whether the intercepted error code is located in the wrong code.
  • the terminal device displays the fault prompt information corresponding to the error code.
  • the fault prompting method provided by the above-mentioned embodiment, by obtaining the current error code output by the fault monitoring component in the SDK device, and obtaining the first version number of the current error code and the user account to which the current error code belongs, and then obtaining the error of the user account.
  • code authorization information if the first version number is the same as the second version number in the error authorization information, and the current error code is located in the matching relationship table in the error authorization information, the current error code is sent to the terminal device paired with the SDK device, so that The terminal device displays the fault prompt information corresponding to the current error code, thereby prompting the user that the SDK device is faulty.
  • the error code authorization information includes the authorized error code, and the authorized error code is located in the error determined according to the health management system of the drone
  • the code pool does not need to redesign and develop the health management system of the SDK device, which greatly reduces the development difficulty of the health management system of the SDK device.
  • FIG. 8 is a schematic flowchart of steps of another fault prompting method provided by an embodiment of the present application.
  • the fault prompting method may include steps S301 to S305.
  • Step S301 obtaining the current error code, first version number and user account sent by the SDK device;
  • Step S302 obtaining the error code authorization information of the user account, where the error authorization information includes a matching relationship table and a second version number between the error code and the fault prompt information;
  • Step S303 if the current error code is located in the matching relationship table, and the first version number is the same as the second version number, obtain the fault corresponding to the current error code from the error code authorization information prompt information, and display the fault prompt information.
  • the current error code is output by the fault monitoring component in the SDK device when the fault is detected.
  • Each component or module or some components or modules in the drone performs fault monitoring, that is, when the fault monitoring component detects that each component or module in the SDK device or some components or modules in the drone is faulty, the fault will be output. corresponding error code.
  • the SDK device obtains the current error code output by the fault monitoring component, and obtains the first version number of the current error code and the user account to which the current error code belongs, and then converts the current error code, the first version number and the user account. It is sent to the terminal device paired with the SDK device, and the terminal device obtains the current error code, first version number and user account sent by the SDK device.
  • the pairing method between the SDK device and the terminal device includes the direct connection pairing of the SDK device and the terminal device or the pairing of the SDK device and the terminal device with the drone respectively, so as to realize the indirect pairing between the SDK device and the terminal device.
  • the error code authorization information of the user account is obtained from the memory, or the error code authorization information of the user account is obtained from the server.
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and a second version number
  • the error code pool determined according to the health management system of the drone includes error codes in the matching relationship table, error codes
  • the pool includes some or all of the error codes opened by the drone's health management system.
  • the language category of the fault prompt information is acquired; the fault prompt information is processed according to the language category, and the processed fault prompt information is displayed.
  • the current language category of the fault prompt information is the same as the language category, the fault prompt information is not processed, and only the fault prompt information is displayed.
  • the method of acquiring the language category of the fault prompt information may be: acquiring the authority level of the user account from the error code authorization information; and acquiring at least one language category corresponding to the authority level of the user account.
  • a translation model corresponding to the language category is acquired, and the fault prompt information is input into the translation model for processing.
  • the translation model is a pre-trained neural network model.
  • the pre-trained neural network model can accurately translate the fault prompt information, and then display the translated fault prompt information.
  • a communication connection between the SDK device and the terminal device is established, so that the SDK device and the terminal device are paired.
  • the device sends an error code authorization information acquisition request to the terminal device.
  • the terminal device forwards the error code authorization information acquisition request to the server, and the server acquires the user account from the acquisition request and obtains the user account. corresponding error code authorization information, and then send the error code authorization information to the terminal device, the terminal device updates the error code authorization information stored in the memory according to the received error code authorization information, and sends the latest error code authorization information to the SDK device,
  • the SDK device encrypts and stores the received error code authorization information. If the terminal device is not connected to the Internet, the error code authorization information stored in the SDK device and the terminal device will not be updated.
  • the error code management method provided by the above embodiment, by obtaining the current error code, the first version number and the user account sent by the SDK device, and obtaining the error code authorization information of the user account, and then in the first version number and the error authorization information.
  • the second version number is the same, and the current error code is located in the matching relationship table in the error authorization information, then the fault prompt information corresponding to the current error code is obtained from the error code authorization information, and the fault prompt information is displayed, thereby prompting the user.
  • the SDK device fails. Since the error code authorization information includes the authorized error code, and the authorized error code is located in the error code pool determined according to the health management system of the drone, there is no need to redesign and develop the health management system of the SDK device. , which greatly reduces the development difficulty of the health management system of the SDK device.
  • FIG. 9 is a schematic structural block diagram of a server provided by an embodiment of the present application.
  • the server 500 includes a processor 510 and a memory 520, and the processor 510 and the memory 520 are connected through a bus 530, such as an I2C (Inter-integrated Circuit) bus.
  • the server 300 is used for communication and connection with the terminal device, the terminal device is used for pairing with the SDK device, the SDK device is mounted on the drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone.
  • the processor 510 may be a micro-controller unit (Micro-controller Unit, MCU), a central processing unit (Central Processing Unit, CPU), or a digital signal processor (Digital Signal Processor, DSP) or the like.
  • MCU Micro-controller Unit
  • CPU Central Processing Unit
  • DSP Digital Signal Processor
  • the memory 520 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, a mobile hard disk, and the like.
  • ROM Read-Only Memory
  • the memory 520 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, a mobile hard disk, and the like.
  • the processor 510 is configured to run the computer program stored in the memory 520, and implement the following steps when executing the computer program:
  • the error code application request includes the user account, version number, the first application number of error codes, and the first fault prompt information list;
  • the processor when the processor allocates an error code to the user account from a preset error code pool according to the first number of applications, the processor is configured to:
  • an error code of the number of the first applications is allocated to the user account from a preset error code pool.
  • the processor when the processor generates the error code authorization information of the user account according to the first fault prompt information list, the error code assigned to the user account, and the version number, use the error code authorization information for the user account.
  • the version number of the matching relationship table is updated based on the version number, and the matching relationship table and the updated version number are determined as the error code authorization information.
  • the processor is further configured to implement the following steps:
  • the account registration request includes the user account to be registered and identity information
  • the user account to be registered passes the real-name authentication, the user account to be registered is written into the account database to complete account registration;
  • the identity information and authority information of the registered user account are generated, where the identity information is used to uniquely identify the user account, and the authority information is used to describe the authority of the registered user account.
  • the processor is further configured to implement the following steps:
  • the permission elevation application request includes the user account, password information and target permission level of the permission to be elevated;
  • the current authority level of the user account whose authority is to be upgraded is upgraded to the target authority level.
  • the processor is further configured to implement the following steps:
  • the current authority level of the user account whose authority is to be upgraded is upgraded to the target authority level.
  • the processor is further configured to implement the following steps:
  • the error code update request includes the target user account of the error code to be updated and the error code update information
  • the updated error code authorization information is sent to the terminal device corresponding to the target user account, so that the terminal device can update the locally stored error code authorization information.
  • the error code update information includes a third application number of error codes and a second fault prompt information list, and the processor implements an error in updating the target user account according to the error code update information.
  • the code authorization information it is used to realize:
  • the error code authorization information of the target user account is updated according to the reassigned error code and the second fault prompt information list.
  • the number of the first application is less than the number of the third application, and the first fault prompt information list is different from the second fault prompt information list; or, the number of the first application is is greater than the third application number, the first fault prompt information list is the same as the second fault prompt information list; or, the first application number is equal to the third application number, the first fault prompt information list The fault prompt information list is different from the second fault prompt information list.
  • FIG. 10 is a schematic structural block diagram of an SDK device provided by an embodiment of the present application.
  • the SDK device 600 includes a processor 610 and a memory 620, and the processor 610 and the memory 620 are connected through a bus 630, such as an I2C (Inter-integrated Circuit) bus.
  • the SDK device 600 is mounted on the drone, and the SDK device 600 is installed with an application program developed based on the SDK framework of the drone.
  • the SDK device 600 is used for pairing with the terminal device, and the terminal device is used for communication and connection with the server.
  • the processor 610 may be a micro-controller unit (Micro-controller Unit, MCU), a central processing unit (Central Processing Unit, CPU) or a digital signal processor (Digital Signal Processor, DSP) or the like.
  • MCU Micro-controller Unit
  • CPU Central Processing Unit
  • DSP Digital Signal Processor
  • the memory 620 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, a mobile hard disk, and the like.
  • ROM Read-Only Memory
  • the memory 620 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, a mobile hard disk, and the like.
  • the processor 610 is configured to run the computer program stored in the memory 620, and implement the following steps when executing the computer program:
  • the SDK device is mounted on the drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone;
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and the second version number, and the error code pool determined according to the health management system of the drone includes all the error code in the matching table;
  • the current error code is located in the matching relationship table, and the first version number is the same as the second version number, the current error code is sent to the terminal device paired with the SDK device for all The terminal device displays fault prompt information corresponding to the current error code.
  • the processor When the processor obtains the error code authorization information of the user account, the processor is configured to:
  • the processor when the processor obtains the error code authorization information of the user account, the processor is configured to:
  • the processor when the processor acquires the error code authorization information of the user account from the server, the processor is configured to:
  • the processor when the processor acquires the error code authorization information of the user account from the server, the processor is configured to:
  • FIG. 11 is a schematic structural block diagram of a terminal device provided by an embodiment of the present application.
  • the terminal device 700 includes a processor 710, a memory 720, and a display device 730.
  • the processor 710, the memory 720, and the display device 730 are connected through a bus 740, such as an I2C (Inter-integrated Circuit) bus.
  • the terminal device 700 is used for communicating with the server and for pairing with the SDK device, the SDK device is mounted on the drone, and the SDK device is installed with an application program developed based on the SDK framework of the drone.
  • the processor 710 may be a micro-controller unit (Micro-controller Unit, MCU), a central processing unit (Central Processing Unit, CPU) or a digital signal processor (Digital Signal Processor, DSP) or the like.
  • MCU Micro-controller Unit
  • CPU Central Processing Unit
  • DSP Digital Signal Processor
  • the memory 720 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, or a removable hard disk, and the like.
  • ROM Read-Only Memory
  • the memory 720 may be a Flash chip, a read-only memory (ROM, Read-Only Memory) magnetic disk, an optical disk, a U disk, or a removable hard disk, and the like.
  • the processor 710 is configured to run the computer program stored in the memory 720, and implement the following steps when executing the computer program:
  • the error authorization information includes a matching relationship table between error codes and fault prompt information and the second version number, and the error code pool determined according to the health management system of the drone includes all the error code in the matching table;
  • the fault prompt information corresponding to the current error code is obtained from the error code authorization information, and displaying the fault prompt information through the display device.
  • the processor When the processor obtains the error code authorization information of the user account, the processor is configured to:
  • the processor when the processor obtains the error code authorization information of the user account, the processor is configured to:
  • the processor when the processor displays the fault prompt information through the display device, the processor is configured to:
  • the fault prompt information is processed according to the language category, and the processed fault prompt information is displayed by the display device.
  • the processor when the processor acquires the language category of the fault prompt information, the processor is configured to:
  • the processor when implementing the processing of the fault prompt information according to the language category, is configured to implement:
  • the fault prompt information is input into the translation model for processing.
  • FIG. 12 is a schematic structural block diagram of an error code management system provided by an embodiment of the present application.
  • the error code management system 800 includes a server 810, an SDK device 820 and a terminal device 830.
  • the server 810 is connected to the SDK device 820 in communication, the SDK device 820 is mounted on the drone, and the SDK device 820 is installed with an For applications developed by the human-machine SDK framework, the SDK device 820 is paired with the terminal device 830 .
  • the server 810 may be the server 500 in FIG. 9
  • the SDK device 820 may be the SDK device 600 in FIG. 10
  • the terminal device 830 may be the terminal device 700 in FIG. 11 .
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions, and the processor executes the program instructions to realize the provision of the above embodiments.
  • the steps of the error code management method or the fault prompt method are described in detail below.
  • the computer-readable storage medium may be an internal storage unit of the server, SDK device, or terminal device described in any of the foregoing embodiments, such as a hard disk or memory of the server, SDK device, or terminal device.
  • the computer-readable storage medium can also be the external storage device of the server, the SDK device or the terminal device, such as a plug-in hard disk equipped on the server, the SDK device or the terminal device, a smart memory card (Smart Media Card, SMC), Secure Digital (SD) card, Flash Card (Flash Card), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种错误码管理方法、故障提示方法、设备、系统及存储介质，该方法包括：获取错误码申请请求，错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表(S101)；根据第一申请个数从预设错误码池中给用户账号分配错误码(S102)；根据第一故障提示信息列表、给用户账号分配的错误码和版本号，生成用户账号的错误码授权信息(S103)；将错误码授权信息发送至用户账号对应的终端设备进行存储(S104)。该方法能够降低SDK设备的健康管理系统的开发难度。

Description

错误码管理方法、故障提示方法、设备、系统及存储介质 技术领域
本申请涉及无人机领域，尤其涉及一种错误码管理方法、故障提示方法、设备、系统及存储介质。
背景技术
随着无人机技术的发展和成本的降低，无人机已经在航拍、农业、测绘等行业有了很广泛的应用。通过无人机的软件开发工具包(Software Development Kit，SDK)框架和接口，第三方开发者可定制所需的功能，以实现满足需求的系统解决方案。
目前，对于无人机内部的各个模块的健康监测主要是通过自身的健康管理系统实现的，而第三方开发者想要对安装有自己开发的应用程序的SDK设备进行健康监测，需要重新设计一套健康管理系统，并配套开发一套交互系统进行健康交互，对第三方开发者而言，需要同时关注SDK设备的健康管理系统和无人机的健康管理系统，开发难度和工作量大，用户体验不好。
发明内容
基于此，本申请实施例提供了一种错误码管理方法、故障提示方法、设备、系统及存储介质，旨在降低SDK设备的健康管理系统的开发难度。
第一方面，本申请实施例提供了一种错误码管理方法，包括：
获取错误码申请请求，所述错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表；
根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码，所述预设错误码池中的错误码是根据无人机的健康管理系统确定的；
根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息；
将所述错误码授权信息发送至所述用户账号对应的终端设备进行存储，以供所述终端设备向与所述终端设备配对的SDK设备发送所述错误码授权信息，以供所述SDK设备根据所述错误码授权信息配置错误码。
本申请实施例提供的错误码管理方法，通过获取包括用户账号、申请的错 误码的数量、故障提示信息列表和版本号的错误码申请请求，并根据申请的错误码的数量从基于无人机的健康管理系统确定的错误码池中给用户账号分配错误码，然后基于分配的错误码、该故障提示信息列表和版本号，生成用户账号的错误码授权信息，最后向用户账号对应的终端设备发送生成的错误码授权信息，使得终端设备存储错误码授权信息，以及向与终端设备配对的SDK设备发送错误码授权信息，使得SDK设备能够基于该错误码授权信息配置错误码，实现SDK设备接入无人机的健康管理系统，不需要重新设计与开发SDK设备的健康管理系统，极大的降低SDK设备的健康管理系统的开发难度。
第二方面，本申请实施例还提供了一种故障提示方法，包括：
获取SDK设备中的故障监测组件输出的当前错误码，所述SDK设备挂载于无人机，且所述SDK设备安装有基于无人机的SDK框架开发的应用程序；
获取所述当前错误码的第一版本号和所述当前错误码所属的用户账号；
获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则向与所述SDK设备配对的终端设备发送所述当前错误码，以供所述终端设备显示所述当前错误码对应的故障提示信息。
本申请实施例提供的故障提示方法，通过获取SDK设备中的故障监测组件输出的当前错误码，并获取当前错误码的第一版本号和当前错误码所属的用户账号，然后获取该用户账号的错误码授权信息，若第一版本号与错误授权信息中的第二版本号相同，且当前错误码位于错误授权信息中的匹配关系表内，则向SDK设备配对的终端设备发送当前错误码，使得终端设备显示当前错误码对应的故障提示信息，从而提示用户SDK设备发生故障，由于错误码授权信息包括已授权的错误码，且已授权的错误码位于根据无人机的健康管理系统确定的错误码池，不需要重新设计与开发SDK设备的健康管理系统，极大的降低SDK设备的健康管理系统的开发难度。
第三方面，本申请实施例还提供了一种故障提示方法，包括：
获取SDK设备发送的当前错误码、第一版本号和用户账号，所述当前错误码是由所述SDK设备中的故障监测组件监测到故障时所输出的；
获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定 的错误码池包括所述匹配关系表中的错误码；
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则从所述错误码授权信息中获取所述当前错误码对应的故障提示信息，并显示所述故障提示信息。
本申请实施例提供的故障提示方法，通过获取SDK设备发送的当前错误码、第一版本号和用户账号，并获取该用户账号的错误码授权信息，然后在第一版本号与错误授权信息中的第二版本号相同，且当前错误码位于错误授权信息中的匹配关系表内，则从该错误码授权信息中获取当前错误码对应的故障提示信息，并显示该故障提示信息，从而提示用户SDK设备发生故障，由于错误码授权信息包括已授权的错误码，且已授权的错误码位于根据无人机的健康管理系统确定的错误码池，不需要重新设计与开发SDK设备的健康管理系统，极大的降低SDK设备的健康管理系统的开发难度。
第四方面，本申请实施例还提供了一种服务器，所述服务器用于与终端设备通信连接，所述终端设备用于与SDK设备配对，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述服务器包括存储器和处理器；
所述存储器用于存储计算机程序；
所述处理器，用于执行所述计算机程序并在执行所述计算机程序时，实现如下步骤：
获取错误码申请请求，所述错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表；
根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码，所述预设错误码池中的错误码是根据无人机的健康管理系统确定的；
根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息；
将所述错误码授权信息发送至所述用户账号对应的终端设备进行存储，以供所述终端设备向与所述终端设备配对的SDK设备发送所述错误码授权信息，以供所述SDK设备根据所述错误码授权信息配置错误码。
第五方面，本申请实施例还提供了一种SDK设备，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述SDK设备用于与终端设备配对，所述终端设备用于与服务器通信连接，所述SDK设备包括存储器和处理器；
所述存储器用于存储计算机程序；
所述处理器，用于执行所述计算机程序并在执行所述计算机程序时，实现如下步骤：
获取SDK设备中的故障监测组件输出的当前错误码，所述SDK设备挂载于无人机，且所述SDK设备安装有基于无人机的SDK框架开发的应用程序；
获取所述当前错误码的第一版本号和所述当前错误码所属的用户账号；
获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则向与所述SDK设备配对的终端设备发送所述当前错误码，以供所述终端设备显示所述当前错误码对应的故障提示信息。
第六方面，本申请实施例还提供了一种终端设备，所述终端设备用于与服务器通信连接和用于与SDK设备配对，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述终端设备包括存储器、处理器和显示装置；
所述存储器用于存储计算机程序；
所述处理器，用于执行所述计算机程序并在执行所述计算机程序时，实现如下步骤：
获取SDK设备发送的当前错误码、第一版本号和用户账号，所述当前错误码是由所述SDK设备中的故障监测组件监测到故障时所输出的；
获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则从所述错误码授权信息中获取所述当前错误码对应的故障提示信息，并通过所述显示装置显示所述故障提示信息。
第七方面，本申请实施例还提供了一种错误码管理系统，所述错误码管理系统包括如上所述的服务器、如上所述的SDK设备以及与如上所述的终端设备，所述服务器与SDK设备通信连接，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述SDK设备与所述终端设备配对。
第八方面，本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时使所述处理器实现如上所述的错误码管理方法或故障提示方法。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
为了更清楚地说明本申请实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是实施本申请实施例提供的错误码管理方法的一场景示意图；
图2是本申请实施例提供的一种错误码管理方法的步骤示意流程图；
图3是本申请实施例中的显示设备、服务器、终端设备与SDK设备之间的数据交互示意图；
图4是本申请实施例提供的一种故障提示方法的步骤示意流程图；
图5是本申请实施例中的服务器、终端设备与SDK设备之间的数据交互示意图；
图6是本申请实施例中的SDK设备、终端设备与服务器之间的数据交互示意图；
图7是本申请实施例中的SDK设备、终端设备、服务器、无人机之间的数据交互示意图；
图8是本申请实施例提供的又一种故障提示方法的步骤示意流程图；
图9是本申请实施例提供的一种服务器的结构示意性框图；
图10是本申请实施例提供的一种SDK设备的结构示意性框图；
图11是本申请实施例提供的一种终端设备的结构示意性框图；
图12是本申请实施例提供的一种错误码管理系统的结构示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳 动前提下所获得的所有其他实施例，都属于本申请保护的范围。
附图中所示的流程图仅是示例说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解、组合或部分合并，因此实际执行的顺序有可能根据实际情况改变。
下面结合附图，对本申请的一些实施方式作详细说明。在不冲突的情况下，下述的实施例及实施例中的特征可以相互组合。
随着无人机技术的发展和成本的降低，无人机已经在航拍、农业、测绘等行业有了很广泛的应用。通过无人机的软件开发工具包(Software Development Kit，SDK)框架和接口，第三方开发者可定制所需的功能，以实现满足需求的系统解决方案。目前，对于无人机内部的各个模块的健康监测主要是通过自身的健康管理系统实现的，而第三方开发者想要对安装有自己开发的应用程序的SDK设备进行健康监测，需要重新设计一套健康管理系统，并配套开发一套交互系统进行健康交互，对第三方开发者而言，需要同时关注SDK设备的健康管理系统和无人机的健康管理系统，开发难度和工作量大，用户体验不好。
为解决上述问题，本申请实施例提供了一种错误码管理方法，通过获取包括用户账号、版本号、申请的错误码的数量和故障提示信息列表的错误码申请请求，并根据申请的错误码的数量从基于无人机的健康管理系统确定的错误码池中给用户账号分配错误码，然后基于分配的错误码、该故障提示信息列表和版本号，生成用户账号的错误码授权信息，最后向用户账号对应的终端设备发送生成的错误码授权信息，使得终端设备存储错误码授权信息，以及向与终端设备配对的SDK设备发送错误码授权信息，使得SDK设备能够基于该错误码授权信息配置错误码，实现SDK设备接入无人机的健康管理系统，不需要重新设计与开发SDK设备的健康管理系统，极大的降低SDK设备的健康管理系统的开发难度。
请参阅图1，图1是实施本申请实施例提供的错误码管理方法的一场景示意图。如图1所示，该场景包括服务器100、终端设备200、无人机300和SDK设备400，服务器100与终端设备200通信连接，SDK设备400挂载于无人机300上，SDK设备400与终端设备200配对连接，以实现数据交互，SDK设备400安装有基于无人机的SDK框架开发的应用程序，使得SDK设备400能够与无人机300适配。例如，SDK设备400为安装有基于无人机的SDK框架开发的应用程序的第三方相机。
在一实施例中，无人机300包括机体310、设于机体310上的动力系统320 和控制系统(图1中未示出)，动力系统320用于为无人机300提供移动动力。其中，无人机300可以包括旋翼型无人机，例如单旋翼无人机、双旋翼无人机、四旋翼无人机、六旋翼无人机、八旋翼无人机，也可以是固定翼无人机，还可以是旋翼型与固定翼无人机的组合，在此不做限定。
其中，无人机300包括健康管理系统，该健康管理系统用于在无人机300启动的全生命周期内对无人机300的内部各组件或模块进行健康监测，无人机300的内部各组件或模块通过内部注册的方式注册错误码，并在特定场景(出现故障)下向终端设备200推送对应的错误码，终端设备200存储有无人机300的内部各组件或模块注册的错误码以及对应的故障提示信息，因此，终端设备200在接收到无人机300推送的错误码时，从存储器中获取该错误码对应的故障提示信息，并显示该故障提示信息。
其中，动力系统320可以包括一个或多个螺旋桨321、与一个或多个螺旋桨相对应的一个或多个电机322、一个或多个电子调速器(简称为电调)。其中，电机322连接在电子调速器与螺旋桨321之间，电机322和螺旋桨321设置在无人机300的机体310上；电子调速器用于接收控制系统产生的驱动信号，并根据驱动信号提供驱动电流给电机322，以控制电机322的转速。电机322用于驱动螺旋桨321旋转，从而为无人机300的移动提供动力，该动力使得无人机300能够实现一个或多个自由度的运动。在某些实施例中，无人机300可以围绕一个或多个旋转轴旋转。例如，上述旋转轴可以包括横滚轴、偏航轴和俯仰轴。应理解，电机322可以是直流电机，也可以交流电机。另外，电机322可以是无刷电机，也可以是有刷电机。
其中，控制系统可以包括处理器和传感系统。传感系统用于测量无人机300的姿态信息，即无人机300在空间的位置信息和状态信息，例如，三维位置、三维角度、三维速度、三维加速度和三维角速度等。传感系统例如可以包括陀螺仪、超声传感器、电子罗盘、惯性测量单元(Inertial Measurement Unit，IMU)、视觉传感器、全球导航卫星系统和气压计等传感器中的至少一种。例如，全球导航卫星系统可以是全球定位系统(Global Positioning System，GPS)。处理器用于控制无人机300的移动，例如，可以根据传感系统测量的姿态信息控制无人机300的移动。应理解，处理器可以按照预先编好的程序指令对无人机300进行控制。
在一实施例中，服务器100获取错误码申请请求，该错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表；根据第 一申请个数从预设错误码池中给用户账号分配错误码，预设错误码池中的错误码是根据无人机的健康管理系统确定的；根据第一故障提示信息列表、给用户账号分配的错误码和该版本号，生成用户账号的错误码授权信息；将错误码授权信息发送至用户账号对应的终端设备200，终端设备200存储该错误码授权信息，并将该错误码授权信息发送至SDK设备400，SDK设备400存储该错误码授权信息，并根据该错误码授权信息配置错误码。
在一实施例中，SDK设备400根据错误码授权信息配置SDK设备中的故障监测组件的错误码，使得故障监测组件在监测到故障时，可以输出配置的对应错误码；SDK设备400获取故障监测组件输出的当前错误码，并获取当前错误码的第一版本号和当前错误码所属的用户账号；获取该用户账号的错误码授权信息，该错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括该匹配关系表中的错误码；若当前错误码位于匹配关系表，且第一版本号与第二版本号相同，则向与SDK设备配对的终端设备200发送当前错误码，终端设备200从本地存储或云端存储的错误码授权信息中获取当前错误码对应的故障提示信息，并显示获取到的故障提示信息。
其中，终端设备200可以包括但不限于：智能电话/手机、平板电脑、个人数字助理(PDA)、台式计算机、媒体内容播放器、视频游戏站/系统、虚拟现实系统、增强现实系统、可穿戴式装置(例如，手表、眼镜、手套、头饰(例如，帽子、头盔、虚拟现实头戴耳机、增强现实头戴耳机、头装式装置(HMD)、头带)、挂件、臂章、腿环、鞋子、马甲)、手势识别装置、麦克风、能够提供或渲染图像数据的任意电子装置、或者任何其他类型的装置。该终端设备200可以是手持终端，终端设备200可以是便携式的。该终端设备200可以由人类用户携带。在一些情况下，终端设备200可以远离人类用户，并且用户可以使用无线和/或有线通信来控制终端设备200。
以下，将结合图1中的场景对本申请的实施例提供的错误码管理方法进行详细介绍。需知，图1中的场景仅用于解释本申请实施例提供的错误码管理方法，但并不构成对本申请实施例提供的错误码管理方法应用场景的限定。
请参阅图2，图2是本申请实施例提供的一种错误码管理方法的步骤示意流程图。该错误码管理方法可以应用于服务器，以降低SDK设备的健康管理系统的开发难度。
如图2所示，该错误码管理方法可以包括步骤S101至步骤S104。
步骤S101、获取错误码申请请求。
其中，该错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表。
在一实施例中，显示设备显示错误码申请页面，然后获取用户在该错误码申请页面输入的错误码的第一申请个数和第一故障提示信息列表；响应于用户对该错误码申请页面中的确认申请图标的触发操作，根据申请错误码的用户账号、版本号、第一申请个数和第一故障提示信息列表，生成错误码申请请求，然后向服务器发送错误码申请请求。其中，第一故障提示信息列表中的故障提示信息的条数与错误码的第一申请个数相同，该触发操作包括用户手指对确认申请图标的触控操作、鼠标的点击操作等。
在一实施例中，显示设备显示错误码申请页面，然后获取用户在该错误码申请页面输入的错误码的第一申请个数、第一故障提示信息列表和故障提示信息的语言类别；响应于用户对该错误码申请页面中的确认申请图标的触发操作，根据申请错误码的用户账号、版本号、语言类别、第一申请个数和第一故障提示信息列表，生成错误码申请请求，然后向服务器发送错误码申请请求。其中，若用户没有输入故障提示信息的语言类别，则响应于用户对该错误码申请页面中的确认申请图标的触发操作，获取申请错误码的用户账号在注册时所选择的语言类别，并根据用户账号、语言类别、第一申请个数和第一故障提示信息列表，生成错误码申请请求，然后向服务器发送错误码申请请求。
在一实施例中，错误码申请页面包括错误码与故障提示信息之间的匹配关系的建立图标，显示设备响应于用户对该建立图标的触发操作，显示匹配关系建立弹窗，该匹配关系建立弹窗显示有无人机的健康管理系统开放的部分或者全部错误码；获取用户在该匹配关系建立弹窗内输入的错误码和故障提示信息；响应于用户匹配关系建立弹窗中的确认图标的触发操作，基于输入的错误码和故障提示信息，生成第一故障提示信息列表。其中，匹配关系建立弹窗包括匹配关系输入框，且匹配关系输入框的个数与用户输入的错误码的第一申请个数相同，也即一个错误码对应一条故障提示信息。
在一实施例中，在向服务器申请错误码之前，需要注册用户账号。示例性的，显示设备显示账号注册页面，并获取用户在该账号注册页面输入的待注册的用户账号和身份信息；响应于用户对账号注册页面中的注册图标的触发操作，根据用户输入的用户账号和身份信息，生成账号注册请求，并向服务器发送该账号注册请求；服务器获取该账号注册请求，并根据该账号注册请求中的身份 信息对该账号注册请求中的待注册的用户账号进行实名认证；若待注册的用户账号通过实名认证，则将待注册的用户账号写入账号数据库，以完成账号注册；生成完成注册的用户账号的身份标识信息和权限信息。
其中，该身份标识信息用于唯一标识注册的用户账号，该身份标识信息可以包括app-id、app-key、app_level，该权限信息用于描述注册的用户账号的权限，包括注册的用户账号可以申请的错误码的个数和故障提示信息可以支持的语言类别，不同权限等级对应的可以申请的错误码的个数和故障提示信息可以支持的语言类别不同，权限等级越高的用户账号，则可以申请的错误码的个数和故障提示信息可以支持的语言类别越多，而权限等级越低的用户账号，则可以申请的错误码个数和故障提示信息可以支持的语言类别越少。
在一实施例中，当用户在申请错误码时，发现自己的用户账号的权限等级对应的可以申请的错误码的个数不够，则可以向服务器申请提升用户账号的权限等级。示例性的，显示设备显示权限提升申请页面，并获取用户在该权限提升申请页面输入的待提升权限的用户账号、密码信息和目标权限等级；响应于用户对该权限提升申请页面中的确认图标的触发操作，根据待提升权限的用户账号、密码信息和目标权限等级，生成权限提升申请请求，并向服务器发送该权限提升申请请求。
在一实施例中，服务器获取权限提升申请请求，并对该权限提升申请请求中的待提升权限的用户账号和密码信息进行验证；若待提升权限的用户账号和密码信息通过验证，则将待提升权限的用户账号的当前权限等级提升为目标权限等级。通过提供权限等级提升功能，使得用户可以按需的提升自己账号的权限等级，便于用户开发SDK设备的健康管理系统。
例如，权限等级一共包括5个，分别为一级、二级、三级、四级和五级，一级最高，五级最低，待提升权限的用户账号的当前权限等级为四级，想要提升到二级，即目标权限等级为二级，则在待提升权限的用户账号和密码信息通过验证时，将待提升权限的用户账号的当前权限等级由四级提升为二级。
在一实施例中，若待提升权限的用户账号和密码信息通过验证，则获取待提升权限的用户账号的当前权限等级；在目标权限等级与当前权限等级的差值小于或等于预设阈值时，将待提升权限的用户账号的当前权限等级提升为目标权限等级；若目标权限等级与当前权限等级的差值大于预设阈值，则将待提升权限的用户账号的当前权限等级提升二个权限等级。其中，预设阈值可基于实际情况进行设置，本申请实施例对此不做具体限定。例如，预设阈值为2。
步骤S102、根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码。
其中，预设错误码池中的错误码是根据无人机的健康管理系统确定的，预设错误码池包括无人机的健康管理系统开放的部分或者全部错误码，该健康管理系统用于在无人机启动的全生命周期内对无人机的内部各组件或模块进行健康监测，无人机的内部各组件或模块通过内部注册的方式注册错误码，并在特定场景(出现故障)下向终端设备推送对应的错误码，终端设备存储有无人机的内部各组件或模块注册的错误码以及对应的故障提示信息，因此，终端设备在接收到无人机推送的错误码时，从存储器中获取该错误码对应的故障提示信息，并显示该故障提示信息。
在一实施例中，获取用户账号的权限信息，并获取权限信息对应的错误码个数；若第一申请个数小于或等于错误码个数，则从预设错误码池中给用户账号分配第一申请个数的错误码；若第一申请个数大于错误码个数，则向显示设备推送权限提升提示信息，告知用户申请的错误码的个数不符合用户账号的权限等级，需要提升用户账号的权限等级，以及如何提升用户账号的权限等级。其中，权限信息对应的错误码个数为用户账号的当前权限等级下可申请的错误码的个数。
在一实施例中，从预设错误码池中给用户账号分配第一申请个数的错误码可以包括：随机的从预设错误码池中选择不重复的错误码，并将选择的错误码分配给该用户账号，直至分配的错误码的个数达到第一申请个数。或者，按照错误码的大小顺序，对预设错误码池中的各错误码进行排序，得到错误码排序队列，然后从错误码排序队列中的首个错误码开始，依次的将错误码排序队列中的错误码分配给该用户账号，直至分配的错误码的个数达到第一申请个数。
步骤S103、根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息。
其中，用户账号的错误码授权信息包括用户账号、错误码、故障提示信息、错误码与故障提示信息之间的匹配关系表、匹配关系表的版本号、故障提示信息的语言类别，语言类别包括汉语、英语、德语、法语、西班牙语、韩语、日语、泰语、阿拉伯语等。
在一实施例中，从第一故障提示信息列表中给分配的错误码匹配故障提示信息，以生成错误码与故障提示信息之间的匹配关系表；基于该版本号更新匹配关系表的版本号，并将所述匹配关系表和更新后的版本号确定为所述错误码 授权信息。示例性的，随机的从第一故障提示信息列表选择一条故障提示信息，并将选择的故障提示信息随机的分配给任一个错误码，直到每个错误码均匹配到一条的故障提示信息，且每个错误码匹配到的故障提示信息不同。
例如，第一故障提示信息列表包括故障提示信息1、故障提示信息2、故障提示信息3，分配的错误码包括错误码A、错误码B和错误码C，则将故障提示信息1匹配给错误码B，将故障提示信息2匹配给错误码A，将故障提示信息3匹配给错误码C，得到错误码与故障提示信息之间的匹配关系表。在另一实施例中，第一故障提示信息列表包括错误码与故障提示信息之间的匹配关系，因此，可以将第一故障提示信息列表确定为错误码与故障提示信息之间的匹配关系表，并生成匹配关系表的版本号。
步骤S104、将所述错误码授权信息发送至所述用户账号对应的终端设备进行存储。
服务器将错误码授权信息发送给用户账号对应的终端设备，终端设备在接收到错误码授权信息后，存储该错误码授权信息，并将该错误码授权信息发送给与终端设备匹配的SDK设备，SDK设备在接收到错误码授权信息后，根据该错误码授权信息配置错误码，使得SDK设备可以使用无人机的健康管理系统的错误码。
在一实施例中，当用户想要更新SDK设备配置的错误码时，可以向服务器重新申请错误码。示例性的，显示设备显示错误码更新页面，并获取用户在该错误码更新页面输入的待更新错误码的目标用户账号和错误码更新信息；响应于用户对错误码更新页面中的确认图标的触发操作，生成错误码更新请求，并向服务器发送错误码更新请求，由服务器基于该错误码更新请求来更新目标用户账号的错误码授权信息。其中，更新错误码授权信息包括增加、减少或修改错误码授权信息中的错误码、修改错误码授权信息中的错误提示信息中的至少一项。
在一实施例中，服务器获取错误码更新请求，该错误码更新请求包括待更新错误码的目标用户账号、错误码更新信息；根据该错误码更新信息更新目标用户账号的错误码授权信息；将更新后的错误码授权信息发送至目标用户账号对应的终端设备，以供终端设备更新本地存储的错误码授权信息，并将更新后的错误码授权信息发送给SDK设备，SDK设备基于更新后的错误码授权信息，重新配置错误码。其中，每次更新错误码授权信息时，均会更新错误码授权信息中的匹配关系表的版本号。
在一实施例中，错误码更新信息包括错误码的第三申请个数和第二故障提示信息列表，根据错误码更新信息更新目标用户账号的错误码授权信息的方式可以为：根据第三申请个数从预设错误码池中重新给用户账号分配错误码；根据重新分配的错误码和第二故障提示信息列表，更新目标用户账号的错误码授权信息。其中，第一申请个数小于第三申请个数，第一故障提示信息列表与第二故障提示信息列表不同；或者，第一申请个数大于第三申请个数，第一故障提示信息列表与第二故障提示信息列表相同；或者，第一申请个数等于第三申请个数，第一故障提示信息列表与第二故障提示信息列表不同。
在一实施例中，错误码更新信息包括待删除的目标错误码，则服务器删除目标用户账号的错误码授权信息中的目标错误码以及目标错误码对应的故障提示信息，并更新匹配关系表的版本号。或者，错误码更新信息包括待增加的目标错误码和目标错误码对应的故障提示信息，则服务器将目标错误码和目标错误码对应的故障提示信息写入目标用户账号的错误码授权信息中，并更新匹配关系表的版本号。
或者，错误码更新信息包括修改前的第一错误码和修改后的第二错误码，且第一错误码和第二错误码均位于该目标用户账号的错误码授权信息中，则将该目标用户账号的错误码授权信息中的第一错误码与第二错误码进行互换，并更新匹配关系表的版本号。或者，错误码更新信息包括修改前的第一故障提示信息和修改后的第二故障提示信息，则将该目标用户账号的错误码授权信息中的第一故障提示信息替换为第二故障提示信息，并更新匹配关系表的版本号。或者，错误码更新信息包括修改前的第一故障提示信息和修改后的第二故障提示信息，且第一故障提示信息与第二提示信息均位于该目标用户账号的错误码授权信息中，则将该目标用户账号的错误码授权信息中的第一故障提示信息和第二故障提示信息进行互换，并更新匹配关系表的版本号。
请参阅图3，图3是本申请实施例中的显示设备、服务器、终端设备与SDK设备之间的数据交互示意图，如图3所示，显示设备向服务器发送账号注册请求，服务器基于账号注册请求生成用户账号的身份标识信息和权限信息，之后显示设备向服务器发送错误码申请请求，服务器基于错误码申请请求生成错误码授权信息，并向终端设备发送错误码授权信息，终端设备存储错误码授权信息，并向SDK设备发送错误码授权信息，SDK设备根据错误码授权信息配置错误码。
请参阅图4，图4是本申请实施例提供的一种故障提示方法的步骤示意流 程图。该故障提示方法可以应用于SDK设备。
如图4所示，该故障提示方法可以包括步骤S201至S204。
步骤S201、获取SDK设备中的故障监测组件输出的当前错误码。
其中，SDK设备挂载于无人机，且SDK设备安装有基于无人机的SDK框架开发的应用程序。该故障监测组件用于在SDK设备挂载于无人机，且启动的全生命周期内对SDK设备中的各组件或模块或无人机中的部分组件或模块进行故障监测，也即故障监测组件在监测到SDK设备中的各组件或模块或无人机中的部分组件或模块出现故障，则输出故障对应的错误码。
步骤S202、获取所述当前错误码的第一版本号和所述当前错误码所属的用户账号。
其中，当前错误码的第一版本号为之前SDK设备基于错误码授权信息所配置的，当前错误码所属的用户账号也是之前SDK设备基于错误码授权信息所配置的。
步骤S203、获取所述用户账号的错误码授权信息。
其中，该错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括匹配关系表中的错误码，错误码池包括无人机的健康管理系统开放的部分或者全部错误码。
在一实施例中，SDK设备的存储器中存储有错误码授权信息，则可以从SDK设备的存储器中获取该用户账号的错误码授权信息。或者，从服务器中获取用户账号的错误码授权信息。通过在本地存储错误码授权信息，可以快速的获取到用户账号的错误码授权信息，而从服务器中可以获取到用户账号的最新的错误码授权信息。
示例性的，向与SDK设备配对的终端设备发送错误码授权信息的获取请求，以供终端设备将获取请求转发给服务器，以使服务器基于获取请求中的用户账号给终端设备下发对应的错误码授权信息；获取终端设备发送的错误码授权信息。
示例性的，向无人机发送错误码授权信息的获取请求，以供无人机将获取请求转发给服务器，以使服务器基于获取请求中的用户账号给无人机下发对应的错误码授权信息；获取无人机发送的错误码授权信息。
步骤S204、若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则向与所述SDK设备配对的终端设备发送所述当前错误码，以供所述终端设备显示所述当前错误码对应的故障提示信息。
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则SDK设备向与SDK设备配对的终端设备发送当前错误码，终端设备在接收到SDK设备发送的当前错误码后，从本地存储或云端存储的错误授权信息中获取当前错误码对应的故障提示信息，并显示当前错误码对应的故障提示信息。
请参阅图5，图5是本申请实施例中的服务器、终端设备与SDK设备之间的数据交互示意图。如图5所示，显示设备向服务器发送错误码申请请求，服务器基于错误码申请请求生成错误码授权信息，并向终端设备发送错误码授权信息，终端设备存储错误码授权信息，并向SDK设备发送错误码授权信息，SDK设备根据错误码授权信息配置错误码，SDK设备拦截错误码，若拦截的错误码的版本号与错误码授权信息中的版本号相同，且拦截的错误码位于错误码授权信息中的匹配关系表，则向终端设备发送错误码，终端设备从错误码授权信息中获取错误码对应的故障提示信息，并显示该故障提示信息。
请参阅图6，图6是本申请实施例中的SDK设备、终端设备与服务器之间的数据交互示意图。如图6所示，SDK设备拦截错误码，并向终端设备发送错误码授权信息的获取请求，终端设备向服务器转发错误码授权信息的获取请求，服务器基于错误码授权信息的获取请求向终端设备发送错误码授权信息，终端设备向SDK设备转发错误码授权信息，判断拦截的错误码的版本号与错误码授权信息中的版本号是否相同以及拦截的错误码是否位于错误码授权信息中的匹配关系表，若拦截的错误码的版本号与错误码授权信息中的版本号相同，且拦截的错误码位于错误码授权信息中的匹配关系表，则向终端设备发送该错误码，终端设备显示该错误码对应的故障提示信息。
请参阅图7，图7是本申请实施例中的SDK设备、终端设备、服务器、无人机之间的数据交互示意图。如图7所示，SDK设备拦截错误码，并向无人机发送错误码授权信息的获取请求，无人机向服务器转发错误码授权信息的获取请求，服务器基于错误码授权信息的获取请求向无人机发送错误码授权信息，无人机向SDK设备转发错误码授权信息，SDK设备判断拦截的错误码的版本号与错误码授权信息中的版本号是否相同以及拦截的错误码是否位于错误码授权信息中的匹配关系表，若拦截的错误码的版本号与错误码授权信息中的版本号相同，且拦截的错误码位于错误码授权信息中的匹配关系表，则向终端设备发送该错误码，终端设备显示该错误码对应的故障提示信息。
上述实施例提供的故障提示方法，通过获取SDK设备中的故障监测组件输 出的当前错误码，并获取当前错误码的第一版本号和当前错误码所属的用户账号，然后获取该用户账号的错误码授权信息，若第一版本号与错误授权信息中的第二版本号相同，且当前错误码位于错误授权信息中的匹配关系表内，则向SDK设备配对的终端设备发送当前错误码，使得终端设备显示当前错误码对应的故障提示信息，从而提示用户SDK设备发生故障，由于错误码授权信息包括已授权的错误码，且已授权的错误码位于根据无人机的健康管理系统确定的错误码池，不需要重新设计与开发SDK设备的健康管理系统，极大的降低SDK设备的健康管理系统的开发难度。
请参阅图8，图8是本申请实施例提供的又一种故障提示方法的步骤示意流程图。
如图8所示，该故障提示方法可以包括步骤S301至步骤S305。
步骤S301、获取SDK设备发送的当前错误码、第一版本号和用户账号；
步骤S302、获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号；
步骤S303、若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则从所述错误码授权信息中获取所述当前错误码对应的故障提示信息，并显示所述故障提示信息。
其中，当前错误码是由SDK设备中的故障监测组件监测到故障时所输出的，该故障监测组件用于在SDK设备挂载于无人机，且启动的全生命周期内对SDK设备中的各组件或模块或无人机中的部分组件或模块进行故障监测，也即故障监测组件在监测到SDK设备中的各组件或模块或无人机中的部分组件或模块出现故障，则输出故障对应的错误码。
在一实施例中，SDK设备获取故障监测组件输出的当前错误码，并获取当前错误码的第一版本号和当前错误码所属的用户账号，然后将当前错误码、第一版本号和用户账号发送给与SDK设备配对的终端设备，终端设备获取SDK设备发送的当前错误码、第一版本号和用户账号。其中，SDK设备与终端设备之间的配对方式包括SDK设备与终端设备直连配对或SDK设备与终端设备分别与无人机配对，从而实现SDK设备与终端设备之间的间接配对。
在一实施例中，从存储器中获取用户账号的错误码授权信息，或者，从服务器中获取用户账号的错误码授权信息。其中，该错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括该匹配关系表中的错误码，错误码池包括无人机的健康管理 系统开放的部分或者全部错误码。
在一实施例中，获取故障提示信息的语言类别；根据语言类别对故障提示信息进行处理，并显示处理后的故障提示信息。示例性的，若故障提示信息的当前语言类别与该语言类别相同，则不对故障提示信息进行处理，仅显示故障提示信息。其中，获取故障提示信息的语言类别的方式可以为：从错误码授权信息中获取用户账号的权限等级；获取该用户账号的权限等级对应的至少一个语言类别。
在一实施例中，若该故障提示信息的当前语言类别与该语言类别不同，则获取语言类别对应的翻译模型，并将该故障提示信息输入翻译模型进行处理。其中，该翻译模型为预先训练好的神经网络模型。通过预先训练好的神经网络模型可以准确的翻译故障提示信息，进而显示翻译后的故障提示信息。
在一实施例中，在打开挂载SDK设备的无人机和终端设备后，并建立SDK设备与终端设备之间的通信连接，以使SDK设备与终端设备完成配对，在完成配对后，SDK设备向终端设备发送错误码授权信息的获取请求，在终端设备联网的情况下，终端设备将错误码授权信息的获取请求转发给服务器，服务器从该获取请求中获取用户账号，并获取该用户账号对应的错误码授权信息，然后向终端设备下发错误码授权信息，终端设备根据接收到的错误码授权信息更新存储器中存储的错误码授权信息，并向SDK设备发送最新的错误码授权信息，SDK设备对接收到的错误码授权信息进行加密存储。如果终端设备未联网，则保持SDK设备和终端设备存储的错误码授权信息不更新。
上述实施例提供的错误码管理方法，通过获取SDK设备发送的当前错误码、第一版本号和用户账号，并获取该用户账号的错误码授权信息，然后在第一版本号与错误授权信息中的第二版本号相同，且当前错误码位于错误授权信息中的匹配关系表内，则从该错误码授权信息中获取当前错误码对应的故障提示信息，并显示该故障提示信息，从而提示用户SDK设备发生故障，由于错误码授权信息包括已授权的错误码，且已授权的错误码位于根据无人机的健康管理系统确定的错误码池，不需要重新设计与开发SDK设备的健康管理系统，极大的降低SDK设备的健康管理系统的开发难度。
请参阅图9，图9是本申请实施例提供的一种服务器的结构示意性框图。
如图9所示，该服务器500包括处理器510和存储器520，处理器510和存储器520通过总线530连接，该总线530比如为I2C(Inter-integrated Circuit)总线。服务器300用于与终端设备通信连接，终端设备用于与SDK设备配对， SDK设备挂载于无人机，且SDK设备安装有基于所述无人机的SDK框架开发的应用程序。
具体地，处理器510可以是微控制单元(Micro-controller Unit，MCU)、中央处理单元(Central Processing Unit，CPU)或数字信号处理器(Digital Signal Processor，DSP)等。
具体地，存储器520可以是Flash芯片、只读存储器(ROM，Read-Only Memory)磁盘、光盘、U盘或移动硬盘等。
其中，所述处理器510用于运行存储在存储器520中的计算机程序，并在执行所述计算机程序时实现如下步骤：
获取错误码申请请求，所述错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表；
根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码，所述预设错误码池中的错误码是根据无人机的健康管理系统确定的；
根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息；
将所述错误码授权信息发送至所述用户账号对应的终端设备进行存储，以供所述终端设备向与所述终端设备配对的SDK设备发送所述错误码授权信息，以供所述SDK设备根据所述错误码授权信息配置错误码。
在一实施例中，所述处理器在实现根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码时，用于实现：
获取所述用户账号的权限信息，并获取所述权限信息对应的错误码个数；
若所述第一申请个数小于或等于错误码个数，则从预设错误码池中给所述用户账号分配所述第一申请个数的错误码。
在一实施例中，所述处理器在实现根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息时，用于实现：
从所述第一故障提示信息列表中给分配的错误码匹配故障提示信息，以生成错误码与故障提示信息之间的匹配关系表；
基于所述版本号更新所述匹配关系表的版本号，并将所述匹配关系表和更新后的版本号确定为所述错误码授权信息。
在一实施例中，所述处理器还用于实现以下步骤：
获取账号注册请求，所述账号注册请求包括待注册的用户账号和身份信息；
根据所述身份信息对所述待注册的用户账号进行实名认证；
若所述待注册的用户账号通过实名认证，则将所述待注册的用户账号写入账号数据库，以完成账号注册；
生成完成注册的用户账号的身份标识信息和权限信息，所述身份标识信息用于唯一标识所述用户账号，所述权限信息用于描述注册的用户账号的权限。
在一实施例中，所述处理器还用于实现以下步骤：
获取权限提升申请请求，所述权限提升申请请求包括待提升权限的用户账号、密码信息和目标权限等级；
对所述待提升权限的用户账号和所述密码信息进行验证；
若所述待提升权限的用户账号和所述密码信息通过验证，则将待提升权限的用户账号的当前权限等级提升为所述目标权限等级。
在一实施例中，所述处理器还用于实现以下步骤：
若所述待提升权限的用户账号和所述密码信息通过验证，则获取所述待提升权限的用户账号的当前权限等级；
在所述目标权限等级与所述当前权限等级的差值小于或等于预设阈值时，将所述待提升权限的用户账号的当前权限等级提升为所述目标权限等级。
在一实施例中，所述处理器还用于实现以下步骤：
获取错误码更新请求，所述错误码更新请求包括待更新错误码的目标用户账号、错误码更新信息；
根据所述错误码更新信息更新所述目标用户账号的错误码授权信息；
将更新后的错误码授权信息发送至所述目标用户账号对应的终端设备，以供所述终端设备更新本地存储的错误码授权信息。
在一实施例中，所述错误码更新信息包括错误码的第三申请个数和第二故障提示信息列表，所述处理器在实现根据所述错误码更新信息更新所述目标用户账号的错误码授权信息时，用于实现：
根据所述第三申请个数从预设错误码池中重新给所述用户账号分配错误码；
根据重新分配的错误码和所述第二故障提示信息列表，更新所述目标用户账号的错误码授权信息。
在一实施例中，所述第一申请个数小于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表不同；或者，所述第一申请个数大于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表相同；或者，所述第一申请个数等于所述第三申请个数，所述第一故障提示 信息列表与所述第二故障提示信息列表不同。
需要说明的是，所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的服务器的具体工作过程，可以参考前述错误码管理方法实施例中的对应过程，在此不再赘述。
请参阅图10，图10是本申请实施例提供的一种SDK设备的结构示意性框图。
如图10所示，该SDK设备600包括处理器610和存储器620，处理器610和存储器620通过总线630连接，该总线630比如为I2C(Inter-integrated Circuit)总线。其中，SDK设备600挂载于无人机，且SDK设备600安装有基于无人机的SDK框架开发的应用程序，SDK设备600用于与终端设备配对，终端设备用于与服务器通信连接。
具体地，处理器610可以是微控制单元(Micro-controller Unit，MCU)、中央处理单元(Central Processing Unit，CPU)或数字信号处理器(Digital Signal Processor，DSP)等。
具体地，存储器620可以是Flash芯片、只读存储器(ROM，Read-Only Memory)磁盘、光盘、U盘或移动硬盘等。
其中，所述处理器610用于运行存储在存储器620中的计算机程序，并在执行所述计算机程序时实现如下步骤：
获取SDK设备中的故障监测组件输出的当前错误码，所述SDK设备挂载于无人机，且所述SDK设备安装有基于无人机的SDK框架开发的应用程序；
获取所述当前错误码的第一版本号和所述当前错误码所属的用户账号；
获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则向与所述SDK设备配对的终端设备发送所述当前错误码，以供所述终端设备显示所述当前错误码对应的故障提示信息。
所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
从所述SDK设备的存储器中获取所述用户账号的错误码授权信息。
在一实施例中，所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
从服务器中获取所述用户账号的错误码授权信息。
在一实施例中，所述处理器在实现从服务器中获取所述用户账号的错误码授权信息时，用于实现：
向与所述SDK设备配对的终端设备发送错误码授权信息的获取请求，以供所述终端设备将所述获取请求转发给服务器，以使所述服务器基于所述获取请求中的用户账号给所述终端设备下发对应的错误码授权信息；
获取所述终端设备发送的所述错误码授权信息。
在一实施例中，所述处理器在实现从服务器中获取所述用户账号的错误码授权信息时，用于实现：
向所述无人机发送错误码授权信息的获取请求，以供所述无人机将所述获取请求转发给服务器，以使所述服务器基于所述获取请求中的用户账号给所述无人机下发对应的错误码授权信息；
获取所述无人机发送的所述错误码授权信息。
需要说明的是，所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的SDK设备的具体工作过程，可以参考前述故障提示方法实施例中的对应过程，在此不再赘述。
请参阅图11，图11是本申请实施例提供的一种终端设备的结构示意性框图。
如图11所示，该终端设备700包括处理器710、存储器720和显示装置730，处理器710、存储器720和显示装置730通过总线740连接，该总线740比如为I2C(Inter-integrated Circuit)总线。其中，终端设备700用于与服务器通信连接和用于与SDK设备配对，SDK设备挂载于无人机，且SDK设备安装有基于无人机的SDK框架开发的应用程序。
具体地，处理器710可以是微控制单元(Micro-controller Unit，MCU)、中央处理单元(Central Processing Unit，CPU)或数字信号处理器(Digital Signal Processor，DSP)等。
具体地，存储器720可以是Flash芯片、只读存储器(ROM，Read-Only Memory)磁盘、光盘、U盘或移动硬盘等。
其中，所述处理器710用于运行存储在存储器720中的计算机程序，并在执行所述计算机程序时实现如下步骤：
获取SDK设备发送的当前错误码、第一版本号和用户账号，所述当前错误码是由所述SDK设备中的故障监测组件监测到故障时所输出的；
获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故 障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则从所述错误码授权信息中获取所述当前错误码对应的故障提示信息，并通过所述显示装置显示所述故障提示信息。
所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
从存储器中获取所述用户账号的错误码授权信息。
在一实施例中，所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
从服务器中获取所述用户账号的错误码授权信息。
在一实施例中，所述处理器在实现通过所述显示装置显示所述故障提示信息时，用于实现：
获取所述故障提示信息的语言类别；
根据所述语言类别对所述故障提示信息进行处理，并通过所述显示装置显示处理后的故障提示信息。
在一实施例中，所述处理器在实现获取所述故障提示信息的语言类别时，用于实现：
从所述错误码授权信息中获取所述用户账号的权限等级；
获取所述用户账号的权限等级对应的至少一个语言类别。
在一实施例中，所述处理器在实现根据所述语言类别对所述故障提示信息进行处理时，用于实现：
若所述故障提示信息的当前语言类别与所述语言类别不同，则获取所述语言类别对应的翻译模型；
将所述故障提示信息输入所述翻译模型进行处理。
需要说明的是，所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的终端设备的具体工作过程，可以参考前述故障提示方法实施例中的对应过程，在此不再赘述。
请参阅图12，图12是本申请实施例提供的一种错误码管理系统的结构示意性框图。
如图12所示，错误码管理系统800包括服务器810、SDK设备820和终端设备830，服务器810与SDK设备820通信连接，SDK设备820挂载于无人机，且SDK设备820安装有基于无人机的SDK框架开发的应用程序，SDK设备820 与终端设备830配对。其中，服务器810可以为图9中的服务器500，SDK设备820可以为图10中的SDK设备600，终端设备830可以为图11中的终端设备700。
需要说明的是，所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的错误码管理系统的具体工作过程，可以参考前述错误码管理方法实施例中的对应过程，在此不再赘述。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序中包括程序指令，所述处理器执行所述程序指令，实现上述实施例提供的错误码管理方法或故障提示方法的步骤。
其中，所述计算机可读存储介质可以是前述任一实施例所述的服务器、SDK设备或终端设备的内部存储单元，例如所述服务器、SDK设备或终端设备的硬盘或内存。所述计算机可读存储介质也可以是所述服务器、SDK设备或终端设备的外部存储设备，例如所述服务器、SDK设备或终端设备上配备的插接式硬盘，智能存储卡(Smart Media Card，SMC)，安全数字(Secure Digital，SD)卡，闪存卡(Flash Card)等。
应当理解，在此本申请说明书中所使用的术语仅仅是出于描述特定实施例的目的而并不意在限制本申请。如在本申请说明书和所附权利要求书中所使用的那样，除非上下文清楚地指明其它情况，否则单数形式的“一”、“一个”及“该”意在包括复数形式。
还应当理解，在本申请说明书和所附权利要求书中使用的术语“和/或”是指相关联列出的项中的一个或多个的任何组合以及所有可能组合，并且包括这些组合。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (42)

  1. 一种错误码管理方法，其特征在于，包括：
    获取错误码申请请求，所述错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表；
    根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码，所述预设错误码池中的错误码是根据无人机的健康管理系统确定的；
    根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息；
    将所述错误码授权信息发送至所述用户账号对应的终端设备进行存储，以供所述终端设备向与所述终端设备配对的SDK设备发送所述错误码授权信息，以供所述SDK设备根据所述错误码授权信息配置错误码。
  2. 根据权利要求1所述的错误码管理方法，其特征在于，所述根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码，包括：
    获取所述用户账号的权限信息，并获取所述权限信息对应的错误码个数；
    若所述第一申请个数小于或等于错误码个数，则从预设错误码池中给所述用户账号分配所述第一申请个数的错误码。
  3. 根据权利要求1所述的错误码管理方法，其特征在于，所述根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息，包括：
    从所述第一故障提示信息列表中给分配的错误码匹配故障提示信息，以生成错误码与故障提示信息之间的匹配关系表；
    基于所述版本号更新所述匹配关系表的版本号，并将所述匹配关系表和更新后的版本号确定为所述错误码授权信息。
  4. 根据权利要求1所述的错误码管理方法，其特征在于，所述方法还包括：
    获取账号注册请求，所述账号注册请求包括待注册的用户账号和身份信息；
    根据所述身份信息对所述待注册的用户账号进行实名认证；
    若所述待注册的用户账号通过实名认证，则将所述待注册的用户账号写入账号数据库，以完成账号注册；
    生成完成注册的用户账号的身份标识信息和权限信息，所述身份标识信息用于唯一标识所述用户账号，所述权限信息用于描述注册的用户账号的权限。
  5. 根据权利要求1所述的错误码管理方法，其特征在于，所述方法还包括：
    获取权限提升申请请求，所述权限提升申请请求包括待提升权限的用户账号、密码信息和目标权限等级；
    对所述待提升权限的用户账号和所述密码信息进行验证；
    若所述待提升权限的用户账号和所述密码信息通过验证，则将待提升权限的用户账号的当前权限等级提升为所述目标权限等级。
  6. 根据权利要求5所述的错误码管理方法，其特征在于，所述方法还包括：
    若所述待提升权限的用户账号和所述密码信息通过验证，则获取所述待提升权限的用户账号的当前权限等级；
    在所述目标权限等级与所述当前权限等级的差值小于或等于预设阈值时，将所述待提升权限的用户账号的当前权限等级提升为所述目标权限等级。
  7. 根据权利要求1-6中任一项所述的错误码管理方法，其特征在于，所述方法还包括：
    获取错误码更新请求，所述错误码更新请求包括待更新错误码的目标用户账号、错误码更新信息；
    根据所述错误码更新信息更新所述目标用户账号的错误码授权信息；
    将更新后的错误码授权信息发送至所述目标用户账号对应的终端设备，以供所述终端设备更新本地存储的错误码授权信息。
  8. 根据权利要求7所述的错误码管理方法，其特征在于，所述错误码更新信息包括错误码的第三申请个数和第二故障提示信息列表，所述根据所述错误码更新信息更新所述目标用户账号的错误码授权信息，包括：
    根据所述第三申请个数从预设错误码池中重新给所述用户账号分配错误码；
    根据重新分配的错误码和所述第二故障提示信息列表，更新所述目标用户账号的错误码授权信息。
  9. 根据权利要求8所述的错误码管理方法，其特征在于，所述第一申请个数小于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表不同；或者，所述第一申请个数大于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表相同；或者，所述第一申请个数等于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表不同。
  10. 一种故障提示方法，其特征在于，包括：
    获取SDK设备中的故障监测组件输出的当前错误码，所述SDK设备挂载于无人机，且所述SDK设备安装有基于无人机的SDK框架开发的应用程序；
    获取所述当前错误码的第一版本号和所述当前错误码所属的用户账号；
    获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
    若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则向与所述SDK设备配对的终端设备发送所述当前错误码，以供所述终端设备显示所述当前错误码对应的故障提示信息。
  11. 根据权利要求10所述的故障提示方法，其特征在于，所述获取所述用户账号的错误码授权信息，包括：
    从所述SDK设备的存储器中获取所述用户账号的错误码授权信息。
  12. 根据权利要求10所述的故障提示方法，其特征在于，所述获取所述用户账号的错误码授权信息，包括：
    从服务器中获取所述用户账号的错误码授权信息。
  13. 根据权利要求12所述的故障提示方法，其特征在于，所述从服务器中获取所述用户账号的错误码授权信息，包括：
    向与所述SDK设备配对的终端设备发送错误码授权信息的获取请求，以供所述终端设备将所述获取请求转发给服务器，以使所述服务器基于所述获取请求中的用户账号给所述终端设备下发对应的错误码授权信息；
    获取所述终端设备发送的所述错误码授权信息。
  14. 根据权利要求12所述的故障提示方法，其特征在于，所述从服务器中获取所述用户账号的错误码授权信息，包括：
    向所述无人机发送错误码授权信息的获取请求，以供所述无人机将所述获取请求转发给服务器，以使所述服务器基于所述获取请求中的用户账号给所述无人机下发对应的错误码授权信息；
    获取所述无人机发送的所述错误码授权信息。
  15. 一种故障提示方法，其特征在于，包括：
    获取SDK设备发送的当前错误码、第一版本号和用户账号，所述当前错误码是由所述SDK设备中的故障监测组件监测到故障时所输出的；
    获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
    若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版 本号相同，则从所述错误码授权信息中获取所述当前错误码对应的故障提示信息，并显示所述故障提示信息。
  16. 根据权利要求15所述的故障提示方法，其特征在于，所述获取所述用户账号的错误码授权信息，包括：
    从存储器中获取所述用户账号的错误码授权信息。
  17. 根据权利要求15所述的故障提示方法，其特征在于，所述获取所述用户账号的错误码授权信息，包括：
    从服务器中获取所述用户账号的错误码授权信息。
  18. 根据权利要求15所述的故障提示方法，其特征在于，所述显示所述故障提示信息，包括：
    获取所述故障提示信息的语言类别；
    根据所述语言类别对所述故障提示信息进行处理，并显示处理后的故障提示信息。
  19. 根据权利要求18所述的故障提示方法，其特征在于，所述获取所述故障提示信息的语言类别，包括：
    从所述错误码授权信息中获取所述用户账号的权限等级；
    获取所述用户账号的权限等级对应的至少一个语言类别。
  20. 根据权利要求19所述的故障提示方法，其特征在于，所述根据所述语言类别对所述故障提示信息进行处理，包括：
    若所述故障提示信息的当前语言类别与所述语言类别不同，则获取所述语言类别对应的翻译模型；
    将所述故障提示信息输入所述翻译模型进行处理。
  21. 一种服务器，其特征在于，所述服务器用于与终端设备通信连接，所述终端设备用于与SDK设备配对，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述服务器包括存储器和处理器；
    所述存储器用于存储计算机程序；
    所述处理器，用于执行所述计算机程序并在执行所述计算机程序时，实现如下步骤：
    获取错误码申请请求，所述错误码申请请求包括用户账号、版本号、错误码的第一申请个数和第一故障提示信息列表；
    根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码，所 述预设错误码池中的错误码是根据无人机的健康管理系统确定的；
    根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息；
    将所述错误码授权信息发送至所述用户账号对应的终端设备进行存储，以供所述终端设备向与所述终端设备配对的SDK设备发送所述错误码授权信息，以供所述SDK设备根据所述错误码授权信息配置错误码。
  22. 根据权利要求21所述的服务器，其特征在于，所述处理器在实现根据所述第一申请个数从预设错误码池中给所述用户账号分配错误码时，用于实现：
    获取所述用户账号的权限信息，并获取所述权限信息对应的错误码个数；
    若所述第一申请个数小于或等于错误码个数，则从预设错误码池中给所述用户账号分配所述第一申请个数的错误码。
  23. 根据权利要求21所述的服务器，其特征在于，所述处理器在实现根据所述第一故障提示信息列表、给所述用户账号分配的错误码和所述版本号，生成所述用户账号的错误码授权信息时，用于实现：
    从所述第一故障提示信息列表中给分配的错误码匹配故障提示信息，以生成错误码与故障提示信息之间的匹配关系表；
    基于所述版本号更新所述匹配关系表的版本号，并将所述匹配关系表和更新后的版本号确定为所述错误码授权信息。
  24. 根据权利要求21所述的服务器，其特征在于，所述处理器还用于实现以下步骤：
    获取账号注册请求，所述账号注册请求包括待注册的用户账号和身份信息；
    根据所述身份信息对所述待注册的用户账号进行实名认证；
    若所述待注册的用户账号通过实名认证，则将所述待注册的用户账号写入账号数据库，以完成账号注册；
    生成完成注册的用户账号的身份标识信息和权限信息，所述身份标识信息用于唯一标识所述用户账号，所述权限信息用于描述注册的用户账号的权限。
  25. 根据权利要求21所述的服务器，其特征在于，所述处理器还用于实现以下步骤：
    获取权限提升申请请求，所述权限提升申请请求包括待提升权限的用户账号、密码信息和目标权限等级；
    对所述待提升权限的用户账号和所述密码信息进行验证；
    若所述待提升权限的用户账号和所述密码信息通过验证，则将待提升权限 的用户账号的当前权限等级提升为所述目标权限等级。
  26. 根据权利要求25所述的服务器，其特征在于，所述处理器还用于实现以下步骤：
    若所述待提升权限的用户账号和所述密码信息通过验证，则获取所述待提升权限的用户账号的当前权限等级；
    在所述目标权限等级与所述当前权限等级的差值小于或等于预设阈值时，将所述待提升权限的用户账号的当前权限等级提升为所述目标权限等级。
  27. 根据权利要求21-26中任一项所述的服务器，其特征在于，所述处理器还用于实现以下步骤：
    获取错误码更新请求，所述错误码更新请求包括待更新错误码的目标用户账号、错误码更新信息；
    根据所述错误码更新信息更新所述目标用户账号的错误码授权信息；
    将更新后的错误码授权信息发送至所述目标用户账号对应的终端设备，以供所述终端设备更新本地存储的错误码授权信息。
  28. 根据权利要求27所述的服务器，其特征在于，所述错误码更新信息包括错误码的第三申请个数和第二故障提示信息列表，所述处理器在实现根据所述错误码更新信息更新所述目标用户账号的错误码授权信息时，用于实现：
    根据所述第三申请个数从预设错误码池中重新给所述用户账号分配错误码；
    根据重新分配的错误码和所述第二故障提示信息列表，更新所述目标用户账号的错误码授权信息。
  29. 根据权利要求28所述的服务器，其特征在于，所述第一申请个数小于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表不同；或者，所述第一申请个数大于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表相同；或者，所述第一申请个数等于所述第三申请个数，所述第一故障提示信息列表与所述第二故障提示信息列表不同。
  30. 一种SDK设备，其特征在于，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述SDK设备用于与终端设备配对，所述终端设备用于与服务器通信连接，所述SDK设备包括存储器和处理器；
    所述存储器用于存储计算机程序；
    所述处理器，用于执行所述计算机程序并在执行所述计算机程序时，实现如下步骤：
    获取SDK设备中的故障监测组件输出的当前错误码，所述SDK设备挂载于无人机，且所述SDK设备安装有基于无人机的SDK框架开发的应用程序；
    获取所述当前错误码的第一版本号和所述当前错误码所属的用户账号；
    获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
    若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则向与所述SDK设备配对的终端设备发送所述当前错误码，以供所述终端设备显示所述当前错误码对应的故障提示信息。
  31. 根据权利要求30所述的SDK设备，其特征在于，所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
    从所述SDK设备的存储器中获取所述用户账号的错误码授权信息。
  32. 根据权利要求30所述的SDK设备，其特征在于，所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
    从服务器中获取所述用户账号的错误码授权信息。
  33. 根据权利要求32所述的SDK设备，其特征在于，所述处理器在实现从服务器中获取所述用户账号的错误码授权信息时，用于实现：
    向与所述SDK设备配对的终端设备发送错误码授权信息的获取请求，以供所述终端设备将所述获取请求转发给服务器，以使所述服务器基于所述获取请求中的用户账号给所述终端设备下发对应的错误码授权信息；
    获取所述终端设备发送的所述错误码授权信息。
  34. 根据权利要求32所述的SDK设备，其特征在于，所述处理器在实现从服务器中获取所述用户账号的错误码授权信息时，用于实现：
    向所述无人机发送错误码授权信息的获取请求，以供所述无人机将所述获取请求转发给服务器，以使所述服务器基于所述获取请求中的用户账号给所述无人机下发对应的错误码授权信息；
    获取所述无人机发送的所述错误码授权信息。
  35. 一种终端设备，其特征在于，所述终端设备用于与服务器通信连接和用于与SDK设备配对，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述终端设备包括存储器、处理器和显示装置；
    所述存储器用于存储计算机程序；
    所述处理器，用于执行所述计算机程序并在执行所述计算机程序时，实现如下步骤：
    获取SDK设备发送的当前错误码、第一版本号和用户账号，所述当前错误码是由所述SDK设备中的故障监测组件监测到故障时所输出的；
    获取所述用户账号的错误码授权信息，所述错误授权信息包括错误码与故障提示信息之间的匹配关系表和第二版本号，根据无人机的健康管理系统确定的错误码池包括所述匹配关系表中的错误码；
    若所述当前错误码位于所述匹配关系表，且所述第一版本号与所述第二版本号相同，则从所述错误码授权信息中获取所述当前错误码对应的故障提示信息，并通过所述显示装置显示所述故障提示信息。
  36. 根据权利要求35所述的终端设备，其特征在于，所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
    从存储器中获取所述用户账号的错误码授权信息。
  37. 根据权利要求35所述的终端设备，其特征在于，所述处理器在实现获取所述用户账号的错误码授权信息时，用于实现：
    从服务器中获取所述用户账号的错误码授权信息。
  38. 根据权利要求35所述的终端设备，其特征在于，所述处理器在实现通过所述显示装置显示所述故障提示信息时，用于实现：
    获取所述故障提示信息的语言类别；
    根据所述语言类别对所述故障提示信息进行处理，并通过所述显示装置显示处理后的故障提示信息。
  39. 根据权利要求38所述的终端设备，其特征在于，所述处理器在实现获取所述故障提示信息的语言类别时，用于实现：
    从所述错误码授权信息中获取所述用户账号的权限等级；
    获取所述用户账号的权限等级对应的至少一个语言类别。
  40. 根据权利要求39所述的终端设备，其特征在于，所述处理器在实现根据所述语言类别对所述故障提示信息进行处理时，用于实现：
    若所述故障提示信息的当前语言类别与所述语言类别不同，则获取所述语言类别对应的翻译模型；
    将所述故障提示信息输入所述翻译模型进行处理。
  41. 一种错误码管理系统，其特征在于，所述错误码管理系统包括如权利要求21-29中任一项所述的服务器、如权利要求30-34中任一项所述的SDK设 备以及与如权利要求35-40中任一项所述的终端设备，所述服务器与SDK设备通信连接，所述SDK设备挂载于无人机，且所述SDK设备安装有基于所述无人机的SDK框架开发的应用程序，所述SDK设备与所述终端设备配对。
  42. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时使所述处理器实现如权利要求1-9中任一项所述的错误码管理方法或实现如权利要求10-20中任一项所述的故障提示方法。
PCT/CN2021/082789 2021-03-24 2021-03-24 错误码管理方法、故障提示方法、设备、系统及存储介质 WO2022198512A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/082789 WO2022198512A1 (zh) 2021-03-24 2021-03-24 错误码管理方法、故障提示方法、设备、系统及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/082789 WO2022198512A1 (zh) 2021-03-24 2021-03-24 错误码管理方法、故障提示方法、设备、系统及存储介质

Publications (1)

Publication Number Publication Date
WO2022198512A1 true WO2022198512A1 (zh) 2022-09-29

Family

ID=83395065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/082789 WO2022198512A1 (zh) 2021-03-24 2021-03-24 错误码管理方法、故障提示方法、设备、系统及存储介质

Country Status (1)

Country Link
WO (1) WO2022198512A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106598033A (zh) * 2016-12-31 2017-04-26 清华大学深圳研究生院 基于中间件的无人机phm系统
CN111752246A (zh) * 2020-07-02 2020-10-09 中国科学技术大学 基于区块链和人工智能驱动的无人机蜂群协同工作平台
CN112407326A (zh) * 2020-11-13 2021-02-26 深圳市领峰电动智能科技有限公司 无人机系统故障诊断方法、装置、电子设备和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106598033A (zh) * 2016-12-31 2017-04-26 清华大学深圳研究生院 基于中间件的无人机phm系统
CN111752246A (zh) * 2020-07-02 2020-10-09 中国科学技术大学 基于区块链和人工智能驱动的无人机蜂群协同工作平台
CN112407326A (zh) * 2020-11-13 2021-02-26 深圳市领峰电动智能科技有限公司 无人机系统故障诊断方法、装置、电子设备和存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED, FUTUREWEI, AT&T, VERIZON: "KI#1, KI#4, New Sol: UAV Identitity Allocation and Usage For Remote Identification", 3GPP DRAFT; S2-2003797, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-Meeting; 20200601 - 20200608, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051889821 *

Similar Documents

Publication Publication Date Title
US10281981B2 (en) AR output method and electronic device for supporting the same
EP3479243B1 (en) Fault-tolerant variable region repaving during firmware over the air update
US10809711B2 (en) Electronic device and method for controlling the same
US9950258B2 (en) System, program, and method for operating screen by linking display and plurality of controllers connected via network
US10402281B2 (en) Dynamic capsule generation and recovery in computing environments
EP3449328B1 (en) Method, storage medium, and electronic device for controlling unmanned aerial vehicle
US10185553B2 (en) Fault-tolerant variable region repaving during firmware over the air update
US20170093593A1 (en) FACILITATING PORTABLE, REUSABLE, AND SHARABLE INTERNET OF THINGS (IoT)-BASED SERVICES AND RESOURCES
US10809710B2 (en) Method for controlling unmanned aerial vehicle and electronic device for controlling unmanned aerial vehicle
US10878070B2 (en) Method of controlling a terminal based on motion of the terminal, terminal therefore, and storage medium
US10038834B2 (en) Video call method and device
US20240144617A1 (en) Methods and systems for anchoring objects in augmented or virtual reality
US10062244B2 (en) Method and apparatus for associating data with time information
GB2603241A (en) Latency determinations for human interface devices
WO2022198512A1 (zh) 错误码管理方法、故障提示方法、设备、系统及存储介质
US10217435B2 (en) Electronic device for displaying screen and method of controlling same
CN108628340A (zh) 基于外部对象的移动确定移动位置的方法及电子设备
EP3220332A1 (en) Method of processing card operating information and electronic device supporting the same
CN117897693A (zh) 不同租赁拥有的计算实例的附接和分离
WO2021087724A1 (zh) 一种控制方法、控制设备、可移动平台及控制系统
KR20170065295A (ko) 외부 전자 장치를 제어하는 전자 장치 및 동작 방법
EP3958096A1 (en) A method and system to integrate multiple virtual reality/augmented reality glass headsets and accessory devices
JP7386583B1 (ja) プログラム、情報処理装置及び方法
US20220035440A1 (en) Adapting extended reality applications to user capability and preference
JP2023134340A (ja) プログラム、情報処理装置及び方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21932140

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21932140

Country of ref document: EP

Kind code of ref document: A1