Debugging system and electronic device

CN122884812APending Publication Date: 2026-10-09SHENZHEN GOERTEK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610958264.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-29
Publication Date
2026-10-09

AI Technical Summary

Technical Problem

相关技术中,不同工站的连接信息、运行环境及依赖配置通常需要人工维护,存在配置步骤繁琐、重复操作较多及环境一致性难以保障的问题,增加了研发与运维成本

Benefits of technology

[0014]本公开提供了一种调试系统,实现多工站环境下的统一协同开发、日志智能分析、自动化调试及自动化研发任务执行,解决了工具链分散、工站配置管理复杂、故障排查效率低、缺乏自动化修复能力的问题,提高了研发效率、降低了运维成本、提升了系统稳定性。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122884812A_ABST
    Figure CN122884812A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a debugging system and an electronic device, the system comprising a work station management layer, a task scheduling layer and an execution layer, wherein the work station management layer is configured to determine a target task, an associated work station for executing the target task and a target electronic device for executing the target task, and send the target task to the task scheduling layer, wherein the associated work station is connected to the target electronic device; the task scheduling layer is provided with a target agent, the target agent is configured to generate a first task execution strategy according to the target task, and send the first task execution strategy to the execution layer, wherein the first task execution strategy comprises at least one target capability unit for executing the target task and at least one processing tool corresponding to each target capability unit; and the execution layer is configured to execute the target task according to the first task execution strategy.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of system testing technology, and more specifically, to a debugging system and an electronic device. Background Technology

[0002] In distributed R&D scenarios, developers typically need to maintain multiple workstations with independent operating environments and hardware configurations simultaneously. In related technologies, the connection information, operating environment, and dependency configurations of different workstations usually require manual maintenance, resulting in cumbersome configuration steps, numerous repetitive operations, and difficulties in ensuring environment consistency, thus increasing R&D and maintenance costs. System logs, operating status, and debugging information are scattered across multiple workstations, lacking unified data aggregation, anomaly correlation analysis, and root cause fault location capabilities. Furthermore, the system mainly relies on developers manually analyzing operating status, locating anomalies, and performing repair operations, leading to low efficiency. Summary of the Invention

[0003] One objective of this invention is to provide a new technical solution for a debugging system.

[0004] According to a first aspect of the present invention, a debugging system is provided, comprising a workstation management layer, a task scheduling layer, and an execution layer, wherein, The workstation management layer is used to determine the target task, the associated workstations that execute the target task, and the target electronic device that executes the target task, and to send the target task to the task scheduling layer, wherein the associated workstations and the target electronic device establish a connection; The task scheduling layer is provided with a target intelligent agent, which is used to generate a first task execution strategy according to the target task and send the first task execution strategy to the execution layer. The first task execution strategy includes at least one target capability unit for executing the target task and at least one processing tool corresponding to each target capability unit. The execution layer is used to execute the target task according to the first task execution strategy.

[0005] Optionally, the target task is a test task input by the user based on the setting interface, or the target task is a fault detection and repair task performed by the target electronic device to execute the set test task.

[0006] Optionally, when the target task is a test task input by the user based on the setting interface, the execution layer is used to generate a first target code according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, and send the first target code to the associated workstation so that the associated workstation sends the first target code to the target electronic device.

[0007] Optionally, the workstation management layer is used to obtain the first log data collected by the associated workstation from the target electronic device, and send the first log data to the task scheduling layer, wherein the first log data is the log data generated by the target electronic device running the first target code; The target agent is used to analyze the first log data according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, and determine the execution result based on the first target code.

[0008] Optionally, if the execution result of the first target code is abnormal, the target agent analyzes the first log data, determines the cause of the abnormality, adjusts the first task execution strategy according to the cause of the abnormality, obtains a second task execution strategy, and sends the second task execution strategy to the execution layer. The execution layer is used to call the corresponding target capability unit and the corresponding processing tool according to the second task execution strategy, generate the second target code, and send the second target code to the associated workstation so that the associated workstation sends the second target code to the corresponding target electronic device.

[0009] Optionally, when the target task is the fault detection and repair task of the target electronic device performing a set test task, the workstation management layer is used to obtain the second log data collected by the associated workstation from the target electronic device, wherein the second log data is the log data generated when the target electronic device performs the set test task; The target intelligent agent is used to analyze the second log data according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, determine the cause of the fault, and generate the first task execution strategy according to the cause of the fault. The execution layer is used to call the corresponding target capability unit and the corresponding processing tool according to the first task execution strategy, generate the third target code, and send the third target code to the associated workstation so that the associated workstation sends the third target code to the corresponding target electronic device.

[0010] Optionally, if the execution result of the first target code is without exception, the target agent is used to store the first task execution strategy corresponding to the target task in a set knowledge base, or... If the execution result based on the third target code is a successful repair, the target agent is used to store the first task execution strategy corresponding to the target task into a set knowledge base.

[0011] Optionally, the workstation management layer includes a workstation management module and a log processing module, wherein, The workstation management module is used to uniformly manage multiple workstations, as well as to determine the target task, the associated workstations that execute the target task, and the target electronic devices that execute the target task, and to send the target task to the task scheduling layer; The log processing module is used to acquire log data collected by each workstation from each connected electronic device and send the log data to the task scheduling layer.

[0012] Optionally, the target intelligent agent includes a task decomposition module, a capability unit management module, a processing tool management module, and a task execution strategy generation module, wherein, The task decomposition module is used to decompose the target task into multiple sub-tasks. The capability unit management module is used to determine at least one target capability unit corresponding to each sub-task. The processing tool management module is used to determine at least one processing tool corresponding to each target capability unit. The task execution strategy generation module is used to generate a corresponding task execution strategy based on each sub-task, at least one target capability unit corresponding to each sub-task, and at least one processing tool corresponding to each target capability unit.

[0013] According to a second aspect of the invention, an electronic device is provided, wherein the electronic device deploys a debugging system as described in any one of the first aspects.

[0014] This disclosure provides a debugging system that enables unified collaborative development, intelligent log analysis, automated debugging, and automated R&D task execution in a multi-workstation environment. It solves the problems of fragmented toolchains, complex workstation configuration management, low fault diagnosis efficiency, and lack of automated repair capabilities, thereby improving R&D efficiency, reducing operation and maintenance costs, and enhancing system stability.

[0015] The features and advantages of the embodiments of this specification will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of this specification and, together with their description, serve to explain the principles of these embodiments.

[0017] Figure 1 This is a schematic diagram of the structure of an electronic device according to some embodiments.

[0018] Figure 2 This is a schematic diagram of the structure of a debugging system according to some embodiments.

[0019] Figure 3 This is a schematic diagram of the structure of an electronic device according to some embodiments. Detailed Implementation

[0020] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0021] The following description of at least one exemplary embodiment is merely illustrative and is not intended to limit the scope of this disclosure or its application or use.

[0022] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0023] In all the examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0024] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0025] This disclosure relates to a debugging system. Figure 1 This is a schematic diagram of the structure of an electronic device equipped with the debugging system of this embodiment. The electronic device 1000 is a device capable of running computer programs. These computer programs can be local applications installed on a head-mounted device, or web applications, lightweight applications, or mini-programs, etc., and are not limited thereto. The electronic device 1000 can be a mobile phone, tablet computer, laptop computer, server, etc., and is not limited thereto.

[0026] like Figure 1 As shown, the electronic device 1000 may include a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, an input device 1500, a display device 1600, etc. Figure 1 The hardware configuration shown is illustrative only and is not intended to limit this disclosure, its application, or its use.

[0027] The processor 1100 is used to execute computer programs, which can be written using instruction sets of architectures such as x86, Arm, RISC, MIPS, and SSE. The memory 1200 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), and non-volatile memory such as a hard disk. The interface device 1300 includes, for example, a USB interface, a network cable interface, and a headphone jack. The communication device 1400 is capable of wired or wireless communication. The communication device 1400 may include at least one short-range communication module, such as any module for short-range wireless communication based on short-range wireless communication protocols such as Hilink, WiFi (IEEE 802.11), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, and LiFi. The communication device 1400 may also include a long-range communication module, such as any module for WLAN, GPRS, or 2G / 3G / 4G / 5G long-range communication.

[0028] This disclosure provides a debugging system that enables unified collaborative development, intelligent log analysis, automated debugging, and automated R&D task execution in a multi-workstation environment. It solves the problems of fragmented toolchains, complex workstation configuration management, low fault diagnosis efficiency, and lack of automated repair capabilities, thereby improving R&D efficiency, reducing operation and maintenance costs, and enhancing system stability.

[0029] The following combination Figure 1 The electronic device shown illustrates the debugging system provided in this disclosure.

[0030] <First Embodiment> Figure 2 This is a schematic diagram of the overall architecture of a debugging system according to some embodiments. For example... Figure 2 As shown, the debugging system includes a workstation management layer 201, a task scheduling layer 202, and an execution layer 203.

[0031] The workstation management layer 201 is used to determine the target task, the associated workstation that executes the target task, and the target electronic device that executes the target task, and then send the target task to the task scheduling layer.

[0032] according to Figure 2 As shown, the workstation management layer 201 includes a workstation management module 2011 and a log processing module 2012.

[0033] The Workstation Management Module 2011, in addition to identifying target tasks, associated workstations executing those tasks, and target electronic devices, and sending the task to the task scheduling layer 202, also manages multiple workstations uniformly. This module features standardized protocol encapsulation capabilities for SSH (Secure Shell), VNC (Virtual Network Computing), file transfer, code synchronization, and remote control. It supports unified management of workstation connection configurations and can store information for each workstation. Furthermore, it supports workstation operational status monitoring, enabling real-time monitoring of each workstation's running status and providing a basis for task scheduling.

[0034] The log processing module 2012 is used to acquire log data collected by each workstation from each connected electronic device and send the log data to the task scheduling layer 202.

[0035] In some examples, the target task can be a test task entered by the user based on the settings interface. For example, the user enters a test task on the settings interface displayed on the electronic device, and the workstation management layer 201 determines that the test task is the target task and determines the associated workstation and target electronic device required to execute the target task.

[0036] In other examples, the target task may be a fault detection and repair task performed by the target electronic device to perform a predefined test task. For example, when the target electronic device is performing a predefined test task, the workstation management layer 201 determines that the fault detection and repair task performed to perform the predefined test task is the target task, and determines the associated workstations and target electronic devices required to perform the fault detection and repair task.

[0037] By supporting both testing and troubleshooting tasks, the debugging system can cover the entire process from R&D to debugging.

[0038] The task scheduling layer 202 is equipped with a target agent, which generates a first task execution strategy based on the target task and sends the first task execution strategy to the execution layer 203. The first task execution strategy includes at least one target capability unit for executing the target task and at least one processing tool corresponding to each target capability unit.

[0039] according to Figure 2 As shown, the target intelligent agent includes a task decomposition module 2021, a capability unit management module 2022, a processing tool management module 2023, and a task execution strategy generation module 2024.

[0040] The task breakdown module 2021 is used to break down the target task into multiple sub-tasks. The capability unit management module 2022 is used to determine at least one target capability unit corresponding to each sub-task. The processing tool management module 2023 is used to determine at least one processing tool corresponding to each target capability unit.

[0041] The target capability units include a fault analysis capability unit, a code generation capability unit, an automated debugging capability unit, and a repair and verification capability unit. The fault analysis capability unit is used to analyze the causes of faults or anomalies based on log data. The code generation capability unit is used to automatically generate code files. The automated debugging capability unit can be used to automatically execute the debugging process. The repair and verification capability unit is used to verify whether the repair results meet expectations.

[0042] The processing tools include code synchronization tools, remote compilation tools, signing tools, deployment and startup tools, log collection tools, test execution tools, and result acquisition tools. The code synchronization tool synchronizes code files to associated workstations. The remote compilation tool performs compilation operations on associated workstations. The signing tool signs the compiled artifacts. The deployment and startup tool deploys the compiled artifacts to the workstations and starts the service. The log collection tool acquires logs from the target electronic devices collected by the workstations. The test execution tool executes test cases. The result acquisition tool obtains test results or service running status.

[0043] The task execution strategy generation module 2024 is used to generate corresponding task execution strategies based on each subtask, at least one target capability unit corresponding to each subtask, and at least one processing tool corresponding to each target capability unit. The task execution strategy can be a workflow.

[0044] The execution layer 203 is used to execute the target task according to the first task execution strategy.

[0045] When the target task is a test task input by the user based on the setting interface, the execution layer 203 is used to generate the first target code according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, and send the first target code to the associated workstation so that the associated workstation sends the first target code to the target electronic device.

[0046] After receiving the first task execution strategy, execution layer 203 automatically performs operations such as code generation, compilation, signing, and packaging according to the corresponding target capability unit and processing tool, generating deployable first target code and distributing it to the associated workstation. For example, execution layer 203 first calls the code generation capability unit and code generation tool to generate code files. Execution layer 203 calls the remote compilation tool to perform compilation operations on the associated workstation, generating compilation artifacts. Execution layer 203 calls the signing tool to sign the compilation artifacts, ensuring the integrity and security of the code. Execution layer 203 packages the signed compilation artifacts into deployable first target code and distributes the first target code to the associated workstation. Throughout the entire execution process, execution layer 203 can automatically complete operations such as code synchronization, remote compilation, signing, and packaging without manual intervention, significantly improving R&D efficiency.

[0047] After receiving the first target code, the associated workstation sends it to the target electronic device via a network connection and deploys and starts the first target code on the target electronic device. The target electronic device executes the first target code to complete the test task. During execution, the target electronic device can generate logs, which can be collected by the associated workstation and sent to the workstation management layer for subsequent log analysis and verification.

[0048] The workstation management layer 201 obtains the first log data collected from the target electronic device by the associated workstation through the log processing module 2012, and sends the first log data to the task scheduling layer 202. The first log data is the log data generated by the target electronic device when it executes the target task.

[0049] In some examples, the workstation management layer 201 also processes the first log data through the log processing module 2012. This log processing module 2012 is used to uniformly process log data from different workstations. The log processing module 2012 includes a log cleaning submodule, a log structured parsing submodule, a log vectorized storage submodule, an exception event extraction submodule, and a log context association submodule.

[0050] The log collection submodule receives log data collected from workstations in real time. The log cleaning submodule performs unified formatting on logs of different formats to ensure consistency in subsequent processing. The log structure parsing submodule extracts log time, service name, call chain, exception type, and context information. The log vectorization storage submodule encodes and stores log semantic features to support retrieval and fault analysis. The exception event extraction submodule identifies exception patterns and extracts exception events, providing input for fault analysis. The log context association submodule builds fault correlation relationships between multiple services and workstations.

[0051] The target agent analyzes the first log data based on the corresponding target capability unit and processing tool in the first task execution strategy to determine the execution result based on the first target code. For example, the target agent can analyze abnormal events, service status, test results, and performance indicators in the first log data to determine whether the result of the target electronic device executing the first target code meets expectations. If no abnormal events are detected in the first log data, the target agent can determine that the execution result is without abnormalities. If abnormal events are detected in the first log data, the target agent can determine that the execution result contains abnormalities.

[0052] If the execution result of the first target code is abnormal, the target agent can analyze the first log data to determine the cause of the abnormality, adjust the first task execution strategy according to the cause, obtain a second task execution strategy, and send the second task execution strategy to the execution layer. The execution layer 203 is used to call the corresponding target capability unit and corresponding processing tool according to the second task execution strategy, generate the second target code, and distribute the second target code to the associated workstation, so that the associated workstation can send the second target code to the corresponding target electronic device. In this way, the debugging system can form an automated closed-loop process from anomaly detection and problem analysis to code repair and deployment verification, reducing manual intervention.

[0053] The execution layer 203 is used to invoke the corresponding target capability unit and corresponding processing tool according to the second task execution strategy, generate the second target code, and send the second target code to the associated workstation, so that the associated workstation sends the second target code to the corresponding target electronic device. The debugging system can collect the log data generated by the target electronic device executing the second target code again, process it through the log processing module 2012, and then have the target intelligent agent verify the repair result.

[0054] In some examples, when the target task is to perform a fault detection and repair task for a target electronic device as part of a predefined test task, the workstation management layer 201 is used to acquire second log data collected from the target electronic device by associated workstations. This second log data is the log data generated by the target electronic device when performing the predefined test task. The target agent is used to analyze the second log data according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, determine the cause of the fault, and generate the first task execution strategy based on the cause of the fault.

[0055] The workstation management layer 201 can use the log processing module to collect, clean, structure, parse, vectorize, extract abnormal events, and correlate log contexts for the second log data. The target agent can then analyze the causes of failures and generate a first task execution strategy based on the abnormal events in the second log data.

[0056] The execution layer 203 is used to call the corresponding target capability unit and the corresponding processing tool according to the first task execution strategy, generate the third target code, and send the third target code to the associated workstation so that the associated workstation sends the third target code to the corresponding target electronic device.

[0057] The debugging system can collect log data generated by the execution of third-party target code by the target electronic device, and the target intelligent agent can verify whether the repair task has been completed.

[0058] In some examples, if the execution result based on the first target code is without exception, the target agent stores the first task execution strategy corresponding to the target task in a designated knowledge base. Alternatively, if the execution result based on the third target code is a successful repair, the target agent stores the first task execution strategy corresponding to the target task in a designated knowledge base. This allows for reference in subsequent tasks targeting the same target.

[0059] In some examples, if the execution result based on the first target code is without exception, the target agent stores the first task execution strategy corresponding to the target task in a cloud knowledge base; or, if the execution result based on the third target code is a successful repair, the target agent stores the first task execution strategy corresponding to the target task in a cloud knowledge base. This allows for reference in subsequent tasks targeting the same target.

[0060] The debugging system provided in this disclosure can realize unified collaborative development, intelligent log analysis, automated debugging, and automated R&D task execution in a multi-workstation environment. It solves the problems of scattered toolchains, complex workstation configuration management, low fault diagnosis efficiency, and lack of automated repair capabilities, thereby improving R&D efficiency, reducing operation and maintenance costs, and enhancing system stability.

[0061] <Second Embodiment> This embodiment provides an electronic device. Figure 3 A schematic diagram of the hardware structure of the electronic device is shown.

[0062] like Figure 3 As shown, the electronic device 300 includes a processor 310 and a memory 320. The memory can be used to store computer programs, and the processor can be used to retrieve the computer programs from the memory to execute any method embodiment of this disclosure. The processor can be one or more, and these processors can execute instructions individually or jointly. Similarly, the memory can be one or more, and these memories can store the aforementioned computer programs individually or jointly.

[0063] The processor 310 is used to execute computer instructions, which can be written using instruction sets of architectures such as x86, Arm, RISC, MIPS, and SSE. The memory 320 includes, for example, ROM (Read-Only Memory), RAM (Random Access Memory), and non-volatile memory such as hard disks, etc., and is not limited here.

[0064] This disclosure also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the audio storage method in any embodiment of this disclosure. Optionally, the computer-readable storage medium may be a non-transitory storage medium, but is not limited thereto; it may also be a temporary storage medium.

[0065] This invention can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of the invention.

[0066] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example, but not limited to, electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0067] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0068] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuits, such as programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), are personalized by utilizing state information from computer-readable program instructions. These electronic circuits can execute computer-readable program instructions to implement various aspects of the present invention.

[0069] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0070] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0071] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0072] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions. It will be known to those skilled in the art that implementation in hardware, implementation in software, and implementation using a combination of software and hardware are equivalent.

[0073] The various embodiments of the present invention have been described above. These descriptions are exemplary and not exhaustive, and are not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.

Claims

1. A debugging system, characterized in that, It includes the workstation management layer, task scheduling layer, and execution layer, among which, The workstation management layer is used to determine the target task, the associated workstations that execute the target task, and the target electronic device that executes the target task, and to send the target task to the task scheduling layer, wherein the associated workstations and the target electronic device establish a connection; The task scheduling layer is provided with a target intelligent agent, which is used to generate a first task execution strategy according to the target task and send the first task execution strategy to the execution layer. The first task execution strategy includes at least one target capability unit for executing the target task and at least one processing tool corresponding to each target capability unit. The execution layer is used to execute the target task according to the first task execution strategy.

2. The debugging system according to claim 1, characterized in that, The target task is a test task input by the user based on the setting interface, or the target task is a fault detection and repair task performed by the target electronic device to execute the set test task.

3. The debugging system according to claim 2, characterized in that, When the target task is a test task input by the user based on the setting interface, the execution layer is used to generate a first target code according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, and send the first target code to the associated workstation so that the associated workstation sends the first target code to the target electronic device.

4. The debugging system according to claim 3, characterized in that, The workstation management layer is used to obtain the first log data collected by the associated workstation from the target electronic device, and send the first log data to the task scheduling layer, wherein the first log data is the log data generated by the target electronic device running the first target code; The target agent is used to analyze the first log data according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, and determine the execution result based on the first target code.

5. The method according to claim 4, characterized in that, If the execution result of the first target code is abnormal, the target agent analyzes the first log data, determines the cause of the abnormality, adjusts the first task execution strategy according to the cause of the abnormality, obtains a second task execution strategy, and sends the second task execution strategy to the execution layer. The execution layer is used to call the corresponding target capability unit and the corresponding processing tool according to the second task execution strategy, generate the second target code, and send the second target code to the associated workstation so that the associated workstation sends the second target code to the corresponding target electronic device.

6. The debugging system according to claim 2, characterized in that, When the target task is the fault detection and repair task of the target electronic device to perform the set test task, the workstation management layer is used to obtain the second log data collected by the associated workstation from the target electronic device, wherein the second log data is the log data generated when the target electronic device performs the set test task; The target intelligent agent is used to analyze the second log data according to the corresponding target capability unit and corresponding processing tool in the first task execution strategy, determine the cause of the fault, and generate the first task execution strategy according to the cause of the fault. The execution layer is used to call the corresponding target capability unit and the corresponding processing tool according to the first task execution strategy, generate the third target code, and send the third target code to the associated workstation so that the associated workstation sends the third target code to the corresponding target electronic device.

7. The debugging system according to claim 4 or 6, characterized in that, If the execution result of the first target code is without exception, the target agent stores the first task execution strategy corresponding to the target task in a set knowledge base, or... If the execution result based on the third target code is a successful repair, the target agent is used to store the first task execution strategy corresponding to the target task into a set knowledge base.

8. The debugging system according to claim 1, characterized in that, The workstation management layer includes a workstation management module and a log processing module, wherein... The workstation management module is used to uniformly manage multiple workstations, as well as to determine the target task, the associated workstations that execute the target task, and the target electronic devices that execute the target task, and to send the target task to the task scheduling layer; The log processing module is used to acquire log data collected by each workstation from each connected electronic device and send the log data to the task scheduling layer.

9. The debugging system according to claim 1, characterized in that, The target intelligent agent includes a task decomposition module, a capability unit management module, a processing tool management module, and a task execution strategy generation module, wherein... The task decomposition module is used to decompose the target task into multiple sub-tasks. The capability unit management module is used to determine at least one target capability unit corresponding to each sub-task. The processing tool management module is used to determine at least one processing tool corresponding to each target capability unit. The task execution strategy generation module is used to generate a corresponding task execution strategy based on each sub-task, at least one target capability unit corresponding to each sub-task, and at least one processing tool corresponding to each target capability unit.

10. An electronic device, characterized in that, The electronic device is equipped with a debugging system as described in any one of claims 1 to 9.