A functional configuration method and a front-end service device

Abstract

The embodiment of the present application provides a function configuration method and a front-end service device. The scheme is as follows: generating a function configuration instruction including target configuration parameters according to a function configuration operation triggered by a user on a front-end service page for a target function module in a task management device; wherein the target function module is a kernel module used for task scheduling and task supervision in a quantum computing task execution process, or a monitoring module used for device supervision in a task management device running process; and sending the function configuration instruction to the task management device, so that the target function module in the task management device performs function configuration according to the target configuration parameters included in the function configuration instruction. Through the technical scheme provided by the embodiment of the present application, the function configuration of the task management device can be realized through the front-end service page.

Description

Technical Field

[0001] This application relates to the field of quantum computing technology, and in particular to a functional configuration method and a front-end service device. Background Technology

[0002] Quantum computing is a computational paradigm that utilizes the fundamental properties of quantum mechanics to solve problems. By constructing precisely operable quantum physics hardware systems and running quantum computing software to implement quantum algorithms, computational problems can be solved, enabling the application of quantum computing in specific problems or fields.

[0003] In the quantum computing process, the task management device can compile and distribute the quantum computing tasks to be executed, and then the qubits on the quantum chip will complete the execution of the quantum computing tasks. Summary of the Invention

[0004] The purpose of this application is to provide a function configuration method and a front-end service device, so as to realize the function configuration of the task management device through the front-end service page. The specific technical solution is as follows:

[0005] This application provides a function configuration method applied to a front-end service device that provides a front-end service page. The front-end service device is communicatively connected to a task management device. The method includes:

[0006] Based on the user's function configuration operation triggered on the front-end service page for the target function module in the task management device, a function configuration instruction including target configuration parameters is generated; wherein, the target function module is a kernel module for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module for device supervision during the operation of the task management device;

[0007] The function configuration instruction is sent to the task management device so that the target function module in the task management device performs function configuration according to the target configuration parameters included in the function configuration instruction.

[0008] This application embodiment also provides a front-end service device, which provides a front-end service page and is communicatively connected to a task management device. The front-end service device includes:

[0009] The first generation unit is used to generate a function configuration instruction including target configuration parameters based on the function configuration operation triggered by the user on the front-end service page for the target function module in the task management device; wherein, the target function module is a kernel module for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module for device supervision during the operation of the task management device;

[0010] The first sending unit is configured to send the function configuration instruction to the task management device, so that the target function module in the task management device performs function configuration according to the target configuration parameters included in the function configuration instruction.

[0011] This application embodiment also provides a front-end service device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0012] Memory, used to store computer programs;

[0013] When a processor executes a program stored in memory, it implements any of the functional configuration method steps described above.

[0014] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the functional configuration method steps described above.

[0015] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the above-described function configuration methods.

[0016] Beneficial effects of the embodiments in this application:

[0017] The technical solution provided in this application allows users to trigger function configuration operations for target functional modules in a task management device via a front-end service page provided by the front-end service device. In this case, the front-end service device can generate a function configuration instruction including target configuration parameters based on the function configuration operation, and then send this instruction to the task management device. The target functional module in the task management device then performs function configuration based on the target configuration parameters carried in the received instruction. Therefore, the function configuration of each functional module in the task management device can be achieved through the front-end service page provided by the front-end service device; that is, the function configuration of the task management device is realized through the front-end service page.

[0018] Of course, implementing any product or method of this application does not necessarily require achieving all of the advantages described above at the same time. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a first flowchart illustrating the functional configuration method provided in the embodiments of this application;

[0021] Figure 2-a A schematic diagram of the structure of a quantum computer provided in an embodiment of this application;

[0022] Figure 2-b A schematic diagram of the structure of a task management device provided in an embodiment of this application;

[0023] Figure 2-c A schematic diagram of a quantum computing measurement and control system provided in an embodiment of this application;

[0024] Figure 3-a A schematic diagram of the front-end service page when configuring the functions provided in the embodiments of this application;

[0025] Figure 3-b for Figure 3-a The diagram illustrates a front-end service page when a kernel change operation is triggered.

[0026] Figure 3-c for Figure 3-a The diagram shows a front-end service page when the scheduling configuration is triggered.

[0027] Figure 3-d for Figure 3-a The image shown is a partial schematic of the front-end service page when the task operation is triggered.

[0028] Figure 3-e for Figure 3-a The diagram shows a front-end service page when the kernel monitoring configuration is triggered.

[0029] Figure 3-f for Figure 3-a The diagram shows a front-end service page when the OPS configuration is triggered.

[0030] Figure 4 This is a second flowchart illustrating the functional configuration method provided in the embodiments of this application;

[0031] Figure 5 for Figure 3-a The diagram shows a front-end service page when the simulator mode change is triggered.

[0032] Figure 6 for Figure 3-a The diagram illustrates a front-end service page when the time-limited access is triggered.

[0033] Figure 7 for Figure 3-a The diagram illustrates a front-end service page when a platform command is triggered.

[0034] Figure 8-a for Figure 3-a This is another partial illustration of the front-end service page when the task operation is triggered;

[0035] Figure 8-b for Figure 3-a This is a schematic diagram of the front-end service page when other operations are triggered.

[0036] Figure 9 for Figure 3-a The diagram shows a front-end service page when the AC time interval is triggered.

[0037] Figure 10 This is a schematic diagram of a first structure of a front-end service device provided in an embodiment of this application;

[0038] Figure 11 This is a schematic diagram of a second structure of the front-end service device provided in an embodiment of this application. Detailed Implementation

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

[0040] To address the problems in related technologies, embodiments of this application provide a function configuration method, such as... Figure 1 As shown, Figure 1 This is a first flowchart illustrating a functional configuration method provided in an embodiment of this application. The method is applied to a front-end service device that provides a front-end service page, and the front-end service device is communicatively connected to a task management device. Figure 1 The method shown includes the following steps.

[0041] Step S101: Based on the function configuration operation triggered by the user on the front-end service page for the target function module in the task management device, generate a function configuration instruction including target configuration parameters; wherein, the target function module is a kernel module used for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module used for device supervision during the operation of the task management device.

[0042] Step S102: Send a function configuration instruction to the task management device so that the target function module in the task management device can perform function configuration according to the target configuration parameters included in the function configuration instruction.

[0043] like Figure 2-a As shown, Figure 2-aThis is a schematic diagram of a quantum computer provided in an embodiment of this application. The quantum computer includes a front-end service device, a task management device, a quantum computing measurement and control system, and a quantum chip. The front-end service device is communicatively connected to the task management device, the task management device is communicatively connected to the quantum computing measurement and control system, and the quantum computing measurement and control system is communicatively connected to the quantum chip.

[0044] The aforementioned front-end service device provides a front-end service page to the user. The user can display this front-end service page on the screen through the service functions installed on their device. The front-end service device can generate corresponding instructions based on the user's actions triggered on the front-end service page and send these instructions to the task management device connected to it. The task management device responds to the received instructions. During the execution of the quantum computing task, the task management device can compile the quantum computing task and distribute it to the quantum computing measurement and control system. The quantum computing measurement and control system then generates the driving signal corresponding to the quantum computing task and distributes the driving signal to the qubits and couplers on the quantum chip connected to the communication link, thereby realizing the execution of the quantum computing task.

[0045] For the aforementioned task management devices, such as Figure 2-b As shown, Figure 2-b This is a schematic diagram of a task management device provided in an embodiment of this application. Figure 2-b The task management device shown includes a kernel module and a monitoring module.

[0046] The aforementioned kernel modules primarily undertake two major functions: task management and platform management. Task management provides various task scheduling modes for quantum computing tasks, enabling task scheduling during the quantum computing process. Furthermore, task management includes handling exceptions during quantum computing task execution, i.e., task monitoring during quantum computing task execution. Platform monitoring manages the software programs of the driver module and performs platform recovery when anomalies are detected.

[0047] The aforementioned monitoring module primarily performs the following functions: system monitoring and alarming, system command execution, module heartbeat management, and scheduled historical task cleanup. System monitoring and alarming monitors data acquisition from various functional modules within the task management device, using configured threshold levels for alarms; for example, an alarm is triggered when a threshold is reached. System command execution involves starting and stopping the router, compiler, and processor submodules within the driver module, as well as cleaning up data in MongoDB, Redis, and system logs. Module heartbeat management detects heartbeats from the router, compiler, and processor submodules. Scheduled historical task cleanup performs periodic cleanup of historical tasks in Redis.

[0048] The MongoDB and Redis mentioned above can be used for configuring the functions of task management devices, configuring the parameters of quantum computing measurement and control systems, and storing data during the execution of quantum computing tasks. The data storage process will not be described in detail here.

[0049] In this embodiment, the task management device also includes other modules, such as a driver module for compiling and distributing quantum computing tasks. Here, no specific limitations are made on the functional modules included in the task management device.

[0050] For the aforementioned quantum computing measurement and control system, such as Figure 2-c As shown, Figure 2-c A schematic diagram of a quantum computing measurement and control system provided in an embodiment of this application. The quantum computing measurement and control system includes a central control module and multiple routing modules (…). Figure 2-c (not shown in the image) and multiple underlying modules ( Figure 2-c (Not shown in the image). The underlying modules of the quantum computing measurement and control system are communicatively connected to the quantum chip. The drive signals transmitted to the quantum chip can be generated by various signal boards in the underlying modules.

[0051] In this embodiment of the application, the aforementioned quantum computing measurement and control system can be a physical cabinet. Figure 2-c The central control module, routing module, and underlying module shown can be different chassis in the cabinet.

[0052] In the above embodiments, only Figure 2-c The quantum computing measurement and control system shown is used as an example for illustration. In addition, the aforementioned front-end service equipment and task management equipment can also be deployed in the aforementioned quantum computing measurement and control system. That is, the aforementioned front-end service equipment and task management equipment can be the chassis in the corresponding rack of the quantum computing measurement and control system. Here, no specific limitation is made on the chassis included in the aforementioned quantum computing measurement and control system or the number of chassis. For ease of understanding, the following only uses... Figure 2-cThe quantum computing measurement and control system shown is used as an example for illustration and is not intended to be limiting.

[0053] pass Figure 1 The method shown allows users to trigger function configuration operations for target functional modules in the task management device via a front-end service page provided by the front-end service device. The front-end service device then generates a function configuration instruction including target configuration parameters based on this operation, and sends this instruction to the task management device. The target functional module in the task management device then performs function configuration based on the target configuration parameters carried in the received instruction. Therefore, the function configuration of each functional module in the task management device can be achieved through the front-end service page provided by the front-end service device; in other words, the function configuration of the task management device is realized through the front-end service page.

[0054] The embodiments of this application will be described below through specific examples.

[0055] Regarding step S101 above, that is, based on the function configuration operation triggered by the user on the front-end service page for the target function module in the task management device, a function configuration instruction including target configuration parameters is generated; wherein, the target function module is a kernel module used for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module used for device supervision during the operation of the task management device.

[0056] The aforementioned task management device includes a kernel module and a monitoring module. On the front-end service page provided by the aforementioned front-end service device, users can trigger function configuration operations targeting a specific functional module within the task management device. The target functional module can be either the kernel module or the monitoring module. When the front-end service device detects a user triggering a function configuration operation, it can generate a function configuration command matching that operation. This function configuration command carries various configuration parameters (denoted as target configuration parameters) set by the user when performing the function configuration operation on the front-end service page.

[0057] In an optional embodiment, if the target functional module is a kernel module, the above-mentioned functional configuration operation can be a first configuration operation to change the running status of the kernel module, a second configuration operation to schedule tasks during the execution of quantum computing tasks, or a third configuration operation to supervise tasks during the execution of quantum computing tasks.

[0058] For ease of understanding, combined with Figure 3-a , Figure 3-b , Figure 3-c , Figure 3-d and Figure 3-e An explanation is provided. Among them, Figure 3-a This is a schematic diagram of a front-end service page for configuring the functions provided in the embodiments of this application. Figure 3-b for Figure 3-a The diagram illustrates a front-end service page when a kernel change operation is triggered. Figure 3-c for Figure 3-a The diagram shown illustrates one possible scenario for the front-end service page when the scheduling configuration is triggered. Figure 3-d for Figure 3-a The image shown is a partial illustration of the front-end service page when the task operation is triggered. Figure 3-e for Figure 3-a The diagram shows a front-end service page when the kernel monitoring configuration is triggered.

[0059] Regarding the first configuration operation mentioned above, when the user triggers it through clicking or other means... Figure 3-a When the kernel change operation occurs in the specified region, the front-end service page will switch to the one shown. Figure 3-b The front-end service page is shown. At this point, the user can set relevant parameters for changing the running status of the aforementioned kernel module, thus triggering the first configuration operation.

[0060] Regarding the second configuration operation mentioned above, when the user triggers it through methods such as clicking... Figure 3-a The region where the scheduling configuration is located, or the trigger. Figure 3-a When the task operation is located in the area shown, the front-end service page will switch to the area shown. Figure 3-c or Figure 3-d The front-end service page shown. At this time, users can respectively... Figure 3-c and Figure 3-d The front-end service page shown allows you to set relevant parameters for task scheduling during quantum computing execution, thereby triggering the second configuration operation.

[0061] Regarding the third configuration operation mentioned above, when the user triggers it through clicking or other means... Figure 3-a When the kernel monitoring configuration is set to the specified region, the front-end service page will switch to the one shown. Figure 3-e The front-end service page is shown. At this point, users can configure relevant parameters for task monitoring during the execution of quantum computing tasks, triggering third-party configuration operations.

[0062] As mentioned above Figure 3-b As shown, the target configuration parameters corresponding to the first configuration operation mentioned above may include one or more of the following: running mode, kernel state, first function option, and kernel lock state. The first function option is used to indicate whether the kernel module enables the performance analysis function. When configuring parameters, the user can... Figure 3-b The front-end service page shown allows configuration of one or more of the following: the running mode, kernel state, first function option, and kernel lock state corresponding to the kernel module.

[0063] In one optional embodiment, the above-mentioned operating modes may include: setup mode, instrument mode, experimental mode, and online mode. In the above... Figure 3-b In the front-end service page shown, users can adjust the "mode" setting in the running mode change area, such as... Figure 3-b The experimental mode shown is adjusted to the above setting mode, and the execution button 301 is triggered to change the corresponding running mode of the kernel module.

[0064] In this embodiment of the application, the above-mentioned setting mode can be used to configure the kernel module and the quantum computing measurement and control system, that is, in the setting mode, the user can configure the parameters of the kernel module and the quantum computing measurement and control system.

[0065] The instrument mode described above only supports tasks that run instrument commands and the hardware layer. In this instrument mode, the task scheduler and exception handling mechanism in the kernel module will not be active. For example, in instrument mode, the kernel module can directly communicate with the quantum computing measurement and control system through the aforementioned driver module to send specific waveform signals, even without qubit information, based on the channel information corresponding to each communication channel in the quantum computing measurement and control system.

[0066] The above experimental mode represents the normal operation of quantum computing task execution services, running under normal kernel module conditions. In this mode, the task scheduler and exception alarm mechanism within the kernel module function normally. Task scheduling can employ a hybrid multi-threaded scheduling strategy. When an exception causes the operating mode to switch to instrument mode, the status and queuing information of unfinished quantum computing tasks in experimental mode are cached; when switching back to experimental mode, an option is provided to resume unfinished quantum computing tasks.

[0067] The online deployment mode described above is the same as the experimental mode, running only when the kernel module is normally providing quantum computing task execution services. The difference lies in the introduction of an automated calibration process in the online deployment mode.

[0068] In an optional embodiment, the kernel states described above may include: initial state, offline state, abnormal state, and running state. Figure 3-b In the front-end service page shown, users can adjust the state in the kernel state change area, such as... Figure 3-b The running status shown is adjusted to the initial status mentioned above, and the execution button 302 is triggered to change the kernel status corresponding to the kernel module.

[0069] In this embodiment, when the kernel module is in the initial state, the quantum computing measurement and control system is not configured. After initializing and configuring the kernel module and the quantum computing measurement and control system, the kernel module can switch to other kernel states, such as the running state described above.

[0070] The aforementioned offline state is the state the quantum computing measurement and control system switches to when it loses power or when no chassis within the system can be connected, indicating that the quantum computing measurement and control system has failed to connect correctly to the corresponding hardware. After the kernel state switches to offline state, the kernel module will only switch back to running state after the quantum computing measurement and control system is tested and verified to be online. In offline state, the kernel module can only run the instrument mode and setting mode described above.

[0071] The aforementioned abnormal state refers to the kernel state entered by the quantum computing measurement and control system when an anomaly affecting the quantum computing task or the task management device service occurs under normal conditions. This indicates that the kernel module and the quantum computing measurement and control system are in an abnormal state. In this situation, the kernel module can initiate a self-recovery service. If recovery is successful, the kernel module will jump back to the kernel state before the anomaly. If recovery fails, it will remain in the abnormal state, at which point the kernel state will automatically adjust from the running mode to the aforementioned instrument mode.

[0072] The above operational status indicates that the quantum computing measurement and control system has completed the corresponding configuration and can support the instrument mode, experimental mode, and online mode. When the kernel module receives a status detection request from the quantum computing measurement and control system, if it determines that the quantum computing measurement and control system is in normal condition, it can switch the kernel state from offline / abnormal state to running state.

[0073] In an optional embodiment, the first function option described above is used to indicate whether the kernel module enables the performance analysis function. This first function option is used to indicate whether the kernel module's troubleshooting (debug) function and performance analysis function are enabled. For ease of understanding, in conjunction with the above... Figure 3-b Let's take an example to illustrate. Figure 3-b In the front-end service page shown, after the user enables or disables the corresponding function options for flag_debug and profile in kernel performance analysis, triggering the execution button 303 will enable or disable the kernel module performance analysis function. During the execution of the quantum computing task, if flag_debug and profile are enabled, the monitoring module in the task management device will collect the usage of system computing and storage resources during the execution process for subsequent performance analysis and optimization.

[0074] In an optional embodiment, the kernel lock state described above is used to indicate whether the kernel module is currently locked. When the kernel module is in a locked state, it can switch to any of the following operating modes: setup mode, instrument mode, experimental mode, and online mode.

[0075] The aforementioned kernel module can only switch to the unlocked state while it is in a locked state. When the kernel module is in the unlocked state, all locks on the task scheduler within the kernel module will be unlocked, thereby restoring the normal operation of the quantum computing task. For example, after completing the above functional configuration, if a quantum computing task needs to be executed, the user can trigger the kernel unlocking through the front-end service page.

[0076] For ease of understanding, in conjunction with the above Figure 3-b This section uses an example to illustrate the switching of kernel lock states. Figure 3-b In the front-end service page shown, users can select to lock, unlock, and disable the kernel in the corresponding operation function options in the kernel operation area. When the user selects... Figure 3-b When locked, the user can select the locking state of the kernel module through the "Lock" function option, and select the corresponding function options for "task_rollback_compiler" and "task_rollback_lower" to trigger the execution button 304 to switch the kernel module's locking state. Specifically, "task_rollback_compiler" indicates whether to return all quantum computing tasks under compilation to the primary task queue, and "task_rollback_lower" indicates whether to return all unexecuted quantum computing tasks to the primary task queue.

[0077] When the kernel module is in the aforementioned locked state, the user can select... Figure 3-b The kernel module lock state is switched to the unlock state by selecting the unlock option in the kernel operation area of ​​the front-end service page shown, or by turning off the Lock option and triggering the execution button 304.

[0078] Additionally, when users are Figure 3-b When the kernel module is shut down, the corresponding operation function option in the kernel operation area is selected on the front-end service page shown, and the execution button 304 is triggered, the kernel module can be shut down.

[0079] In this embodiment, there is a certain correlation between the aforementioned operating mode, kernel state, and kernel lock state. For example, some configuration parameters in the kernel module are not hot-update data; that is, the data can be stored in Redis and read from Redis to take effect when the kernel module needs it. In this case, when updating / configuring such data, the kernel lock state can be set to locked first, the kernel state can be set to the initial state, and then the operating mode can be changed to setting mode to update / configure the configuration parameters. Here, the correlation between the aforementioned operating mode, kernel state, and kernel lock state is not specifically limited.

[0080] In the above Figure 3-b In the front-end service page shown, each triggering of the execute button, i.e., each triggering of execute button 301-execute button 304, is accompanied by the generation of the aforementioned function configuration instructions. In addition, in the aforementioned... Figure 3-b The front-end service page design shown can also include only one execute button. No specific limitations are imposed on the design of the front-end service page here.

[0081] In an optional embodiment, the target configuration parameters corresponding to the second configuration operation described above may include one or more of the following: scheduling mode, manager type, verification type, number of threads, number of execution modules, parallel compilation limit, sliding window size, scheduling length, number of retries, safety bit distance, warning bit distance, and task queuing coefficient.

[0082] The target configuration parameters corresponding to the second configuration operation mentioned above are configuration parameters related to task scheduling during the execution of quantum computing tasks. For example... Figure 3-c As shown, users can... Figure 3-c The front-end service page shown configures parameters such as scheduling mode (task scheduling mode and advanced scheduling mode), manager type, verification type, number of threads, number of execution modules, parallel compilation limit, sliding window size, scheduling length (intermediate scheduling length and primary scheduling length), number of retries, safety bit distance, and warning bit distance, and triggers... Figure 3-c The execution button shown enables... Figure 3-c The configuration parameters shown correspond to the triggering of the second configuration operation. For example... Figure 3-d As shown, users can... Figure 3-d The front-end service page shown allows setting the function options and task queuing coefficient for abnormal tasks, and triggering the execution buttons 305 and 306 to trigger the second configuration operation corresponding to the configuration parameters.

[0083] In the above Figure 3-cIn this context, task scheduling modes can include Compile TMS, Core TMS, CorePriority TMS, and CompilerPriority TMS. Compile TMS is a runtime task scheduling mode, used to indicate whether to schedule execution when a task is issued for compilation; Core TMS is a runtime scheduling mode, used to schedule execution only after the quantum computing task has been compiled; CorePriority TMS is a priority-based compilation scheduling mode, adding priority to the compilation-time scheduling; and CompilerPriority TMS is a priority-based runtime scheduling mode, adding priority to the runtime scheduling.

[0084] In addition, in the above Figure 3-c In the high-level scheduling mode, TaskPriority HS, multiMiddle HS, and single thread HS can be included. Among them, TaskPriority HS is a single-queue multi-threaded scheduling; multiMiddle HS is a multi-queue priority multi-threaded scheduling; and single thread HS is a single-threaded scheduling.

[0085] During the execution of the aforementioned quantum computing tasks, the kernel module can contain various task scheduling queues, such as a primary task queue for scheduling and managing quantum computing tasks waiting to be compiled, a secondary task queue for scheduling and managing quantum computing tasks waiting to be executed, and a high-level task queue for scheduling and managing quantum computing tasks currently being executed. Here, no specific limitation is made on the task queues managed by the kernel module or the number of such queues.

[0086] In the above Figure 3-d In the kernel module, when the error task option (error_task_retry) is selected and the execution button 305 is triggered, the kernel module can re-execute the quantum computing task after the number of failed attempts reaches a preset number, such as 5000 or 10000. Figure 3-d The task queuing coefficients mentioned above can include: imf_expected_time, imf_priority, and imf_push, which are respectively the factors affecting the expected execution time of quantum computing tasks, the factors affecting the priority of quantum computing tasks, and the factors affecting the queuing time of quantum computing tasks in the high-level task queue.

[0087] In this embodiment of the application, the target configuration parameters corresponding to the second configuration operation can be set according to user needs, etc. Here, the target configuration parameters corresponding to the second configuration operation are not specifically limited.

[0088] In an optional embodiment, the target configuration parameter corresponding to the third configuration operation described above may include one or more of the following: timeout duration, number of timeout wait rounds, and a second function option. The second function option is used to indicate whether the kernel module enables the task check switch. The timeout duration may include: execution timeout, compilation timeout, thread timeout, and task timeout.

[0089] For example, users can in the above Figure 3-a The front-end service page shown displays the area where the kernel monitoring configuration is triggered, as shown below. Figure 3-e The front-end service page shown. Figure 3-e In the front-end service page shown, users can set each configuration parameter and trigger [the service]. Figure 3-e The execute button shown triggers the third configuration operation.

[0090] In an optional embodiment, if the target functional module is the aforementioned monitoring module, then the aforementioned functional configuration operation is a fourth configuration operation for monitoring the equipment during the operation of the task management device. The target configuration parameters corresponding to this fourth configuration operation may include one or more of alarm configuration parameters, operation configuration parameters, and monitoring water level parameters for system resources.

[0091] For ease of understanding, in conjunction with the above Figure 3-f Let's take an example to illustrate. Figure 3-f for Figure 3-a The diagram shows a front-end service page when the OPS configuration is triggered.

[0092] like Figure 3-f As shown, the front-end service page includes an OPS alarm configuration area. Users can set alarm configuration parameters in this area, which can include: platform identifier, task alarm level, service alarm level, hardware alarm level, and alarm service connection heartbeat interval (alarm_hb_intv). The task_level, service_level, and qaio_level can have multiple different levels, such as: tip alarm, debug, normal alarm, info, warning, important, and crash.

[0093] In the above Figure 3-fThe front-end service page shown includes an OPS runtime configuration area. Users can set configuration parameters for the monitoring module in the OPS runtime configuration area, which can include: a third function option (enable_collect), a fourth function option (enable_alarm), and a scheduled time (scheduled_cleanup). The third function option indicates whether the monitoring module enables monitoring data collection, and the fourth function option indicates whether the monitoring module enables alarms.

[0094] In the above Figure 3-f The front-end service page shown includes an OPS monitoring water level area. Users can configure monitoring water level parameters for system resources in this area, which can include: normal water level level (low_wm), high water level level (alarm_wm_rate), effective time for anomaly trigger (effective_time), anomaly trigger interval (trigger_interval), monitoring collection interval (collect_interval), anomaly alarm trigger type (alarm_type), number of repeated anomaly alarm triggers (alarm_repeats), and heartbeat interval configuration (heartbeat_time).

[0095] The aforementioned system resources can be the system's computing and storage resources, including system CPU, system memory, system cache, system disk, Mongo disk, Mongo memory, Redis memory, and Prometheus disk.

[0096] Regarding step S102 above, a function configuration instruction is sent to the task management device so that the target function module in the task management device can perform function configuration according to the target configuration parameters included in the function configuration instruction.

[0097] In an optional embodiment, when the target functional module is the kernel module, the front-end service device can send the generated functional configuration instruction to the task management device. The kernel module in the task management device will receive the functional configuration instruction. At this time, the kernel module can perform functional configuration according to the target configuration parameters in the received functional configuration instruction.

[0098] For example, when the above function configuration operation is the second configuration operation, after receiving the above function configuration instruction, the kernel module can reconfigure the relevant configuration parameters of the task scheduling process according to the configuration parameters carried in the function configuration instruction, so as to realize the function configuration of the kernel module task scheduling process.

[0099] In another optional embodiment, when the target functional module is the monitoring module, the front-end service device can send the generated functional configuration instruction to the task management device. Upon receiving the functional configuration instruction, the kernel module in the task management device can forward it to the monitoring module. The monitoring module then configures the function according to the target configuration parameters in the received functional configuration instruction.

[0100] In an optional embodiment, according to the above... Figure 1 In addition to the method shown, this application embodiment also provides a function configuration method. For example... Figure 4 As shown, Figure 4 This is a second flowchart illustrating the functional configuration method provided in an embodiment of this application. Figure 4 The method shown includes the following steps, namely steps S103-S111.

[0101] In step S103, if the kernel module is in a locked state and the user triggers a start operation for the simulator on the front-end service page, a simulator start command is sent to the kernel module so that the kernel module can trigger the simulation execution of the quantum computing task based on the simulator start command.

[0102] For ease of understanding, combined with Figure 3-a and Figure 5 Let's take an example to illustrate. Figure 5 for Figure 3-a The diagram illustrates a front-end service page when a simulator mode change is triggered. If the aforementioned kernel module switches to a locked state, then when the user... Figure 3-a When the simulator mode is triggered and the region is changed on the front-end service page shown, the following will be displayed: Figure 5 The front-end service page shown is accessible to users. Figure 5 The front-end service page shown allows users to enable or disable the "simulate" function and trigger the execution button, thus enabling or disabling the simulator.

[0103] When the user Figure 5 The front-end service page triggers a startup operation for the emulator. Based on this operation, the front-end service page generates an emulator startup command and sends it to the task management device. At this point, the kernel module in the task management device receives the emulator startup command.

[0104] When the kernel module receives the simulator start command, it can trigger the simulation execution of the quantum computing task. The execution process of the quantum computing task can be found in relevant technical documentation and will not be detailed here.

[0105] In step S103 above, the user can trigger the start operation for the simulator in the front-end service page, which enables the kernel module in the task management device to start the simulation execution process for the quantum computing task, thereby realizing the simulation execution of the quantum computing task.

[0106] In an optional embodiment, when a user triggers a shutdown operation for the simulator on the front-end service page, the front-end service device can generate a simulator shutdown command and send the simulator shutdown command to the task management device. Upon receiving the simulator shutdown command, the kernel module in the task management device can trigger the shutdown of the quantum computing task simulation execution process.

[0107] Step S104: Based on the exclusive operation triggered by the user on the front-end service page for the quantum computing measurement and control system, generate a user exclusive instruction. The user exclusive instruction includes: username and exclusive duration.

[0108] For ease of understanding, in conjunction with the above Figure 3-a and Figure 6 Let's take an example to illustrate. Figure 6 for Figure 3-a The diagram shows a front-end service page when the machine time is exclusively triggered.

[0109] Users Figure 3-a The front-end service page shown displays the trigger mechanism after it exclusively occupies the designated area. Figure 6 The front-end service page shown. Figure 6 In the front-end service page shown, after selecting "Enable device-wide exclusive access" in the operation function options, the user can set the username and exclusive access duration (expire_time) and trigger the function. Figure 6 The execute button shown triggers an exclusive operation on the quantum computing measurement and control system. At this time, the front-end service device can generate the exclusive command corresponding to this exclusive operation.

[0110] In an optional embodiment, the above exclusive instructions may further include, for example: Figure 6 The exclusive closing restriction (i.e., close_only) is shown. This exclusive closing restriction is used to indicate whether only the user can close the exclusive operation, that is, whether only the user can close the exclusive operation.

[0111] In an optional embodiment, when the aforementioned user triggers the exclusive operation, if another user's exclusive operation already exists at the current moment, then the above-mentioned... Figure 6 When the front-end service page is displayed, it can show the exclusive information corresponding to the current exclusive operation, such as the username and remaining duration of the exclusive operation. At this time, the front-end service device can prevent users from accessing the exclusive service. Figure 6The exclusive operation is triggered in the front-end service page shown.

[0112] Step S105: Send a user exclusive instruction to the kernel module so that the kernel module, upon receiving the user exclusive instruction, will trigger the execution of the quantum computing task matching the username within the exclusive duration.

[0113] In this step, after generating the aforementioned user-exclusive instruction, the front-end service device can send the user-exclusive instruction to the task management device. The kernel module in the task management device will receive the user-exclusive instruction. At this time, the kernel module can trigger the execution of the quantum computing task matching the username within the exclusive duration based on the information carried in the received user-exclusive instruction.

[0114] For example, a kernel module can call the task scheduler to move all quantum computing tasks that do not match the username to the cache queue and move the quantum computing tasks that match the username to the VIP task queue, thereby executing the quantum computing tasks in the VIP task queue during the exclusive time period.

[0115] In steps S104-S105 above, after the user triggers an exclusive operation on the front-end service page, the kernel module in the task management device can execute only the user's quantum computing task within the exclusive duration according to the user exclusive instruction corresponding to the exclusive operation, thus ensuring the exclusivity of the execution of the user's corresponding quantum computing task.

[0116] In an optional embodiment, in the above... Figure 6 In the front-end service page shown, when a user changes the exclusive operation option from "power-on" to "power-off" and triggers the execute button, an exclusive shutdown operation for the quantum computing measurement and control system will be triggered. At this time, the front-end service device will generate an exclusive shutdown command corresponding to this operation and send it to the task management device. Upon receiving the exclusive shutdown command, the kernel module in the task management device can disable the user's exclusive operation at the current moment. For example, all quantum computing tasks in the aforementioned VIP task queue can be moved to the cache queue.

[0117] In an optional embodiment, when the exclusive shutdown restriction in the above user exclusive instruction indicates that only the user can operate on the exclusive operation of the user, the kernel module may not respond to the exclusive shutdown instruction when it receives an exclusive shutdown instruction triggered by someone other than the user.

[0118] Step S106: Based on the first target operation triggered by the user on the front-end service page for the data related to the execution process of the quantum computing task, generate a first operation instruction. The first target operation is a data cleaning operation or a log transfer operation. The first operation instruction includes: the instruction number corresponding to the first target operation, the operation interval duration / operation data volume.

[0119] For ease of understanding, in conjunction with the above Figure 3-a and Figure 7 Let's take an example to illustrate. Figure 7 for Figure 3-a The diagram shows a front-end service page when a platform command is triggered.

[0120] In the above Figure 3-a In the front-end service page shown, when a user triggers the area containing the platform command, the following can be displayed: Figure 7 The front-end service page shown. At this time, the user can... Figure 7 The data cleanup or log transfer operation is triggered in the front-end service page shown (denoted as the first target operation). For example, a user can... Figure 7 The front-end service page shows settings for `cached_inst` (command number) and `clear_policy` (operation interval duration / operation data volume), and triggers the execute button to initiate the first target operation. The front-end service device can generate a corresponding operation command (denoted as the first operation command) based on the first target operation.

[0121] In this embodiment, the instruction numbers include: Mongo data cleanup, data cleanup, system log dump, Prometheus data cleanup, and system memory cleanup. The data related to the execution of the quantum computing task may include log data, data stored in MongoDB and Redis, etc. Here, no specific limitations are made on the instruction numbers and related data.

[0122] Step S107: The kernel module sends a first operation instruction to the monitoring module, so that after receiving the first operation instruction, the monitoring module triggers the execution of the first target operation corresponding to the instruction number according to the operation interval duration / operation data volume.

[0123] In this step, after the front-end service device sends the first operation instruction to the task management device, the kernel module in the task management device will receive the first operation instruction. At this time, the kernel module can forward the first operation instruction to the monitoring module. After receiving the first operation instruction, the monitoring module can execute the data cleanup operation / log transfer operation corresponding to the instruction number according to the operation interval / operation data volume.

[0124] For ease of understanding, Figure 7 The first target operation shown is used as an example for explanation. The monitoring module receives... Figure 7 After the first operation instruction corresponding to the first target operation shown, data cleanup can be performed on the data in Mongo every 30 days.

[0125] The above Figure 7The clear_policy shown can be either time data (i.e., the duration of the operation interval mentioned above) or data volume (i.e., the amount of data involved in the operation mentioned above).

[0126] In steps S106-S107 above, the front-end service device can generate a first operation instruction based on the first target operation triggered by the user in the front-end service page, and then send the first operation instruction to the task management device, so that the monitoring module in the task management device can respond to the first operation instruction and realize the execution of the first target operation.

[0127] Step S108: Based on the second target operation triggered by the user for the quantum computing task on the front-end service page, generate a second operation instruction. The second target operation includes: an inter-queue operation, a priority adjustment operation, a deletion operation, or a retry operation for any quantum computing task; a clear operation for all quantum computing tasks; and a recovery operation for the thread corresponding to the quantum computing task.

[0128] To facilitate understanding, let's combine the above points respectively. Figure 3-a , Figure 8-a and Figure 8-b Let's take an example to illustrate. Figure 8-a for Figure 3-a The diagram shows another partial view of the front-end service page when the task operation is triggered. Figure 8-b for Figure 3-a This is a schematic diagram of the front-end service page when other operations are triggered.

[0129] In the above Figure 3-a In the front-end service page shown, after the user triggers the task operation in the designated area, the following is displayed: Figure 8-a The front-end service page shown. Figure 8-a The front-end service page shown allows users to trigger queue-jumping, priority adjustment, deletion, or retry operations for quantum computing tasks. For ease of understanding, only the queue-jumping operation is illustrated. Users can... Figure 8-a In the front-end service page shown, the operator (task operation) is set to... Figure 8-a The task shown is called "Queue Jumping." This involves setting the task identifier (task_id) of the quantum computing task to be jumped into, and triggering the execute button to initiate the queue jumping operation. At this point, the front-end service device can generate an operation command (i.e., a second operation command) corresponding to this queue jumping operation.

[0130] In the above Figure 3-a In the front-end service page shown, after a user triggers another operation in that area, the following can be displayed: Figure 8-b The front-end service page shown. Figure 8-b In the front-end service page shown, users can trigger Figure 8-bThe "Clear All Tasks" button shown triggers the clear operation for all quantum computing tasks; alternatively, the user can trigger... Figure 8-b The "Restore Thread" button shown triggers the restore operation for the thread corresponding to the quantum computing task. The front-end service device can generate operation instructions that match the clear / restore operation, i.e., the second operation instruction mentioned above.

[0131] Step S109: Send a second operation instruction to the kernel module so that the kernel module executes the second target operation according to the received second operation.

[0132] For ease of understanding, the above will still be used. Figure 8-a and Figure 8-b Let's take an example to illustrate. When a user... Figure 8-a When the above-mentioned kernel module triggers a queue-jumping operation for a specific task, after receiving the second operation instruction, if the quantum computing task is in the cache queue, the kernel module can move the quantum computing task to the high-level task queue to wait for execution; if the quantum computing task is in the high-level task queue, the kernel module can advance the execution order of the quantum computing task. When the user triggers such... Figure 8-b When the "Clear All Tasks" button is shown, the kernel module, upon receiving the second operation instruction, can clear all quantum computing tasks in the task queue; when the user triggers... Figure 8-b When the "Resume Thread" button is pressed, the kernel module can re-execute the quantum computing task that the thread core is currently executing after receiving the second operation instruction.

[0133] In steps S108-S109 above, the user triggers the second target operation through the front-end service page, thereby causing the front-end service device to send a second operation instruction to the task management device. The kernel module in the task management device responds to the received second operation instruction, realizing the user's management and control of the quantum computing task.

[0134] Step S110: Based on the voltage calibration operation triggered by the user on the front-end service page, generate a voltage calibration instruction, which includes the calibration interval duration.

[0135] In this embodiment, the voltage of the arbitrary waveform generator (AWG) signal output by the quantum computing measurement and control system to the quantum chip may deviate due to environmental factors and the equipment itself during quantum computing. To reduce the impact of voltage deviation on the quantum computing process, the user can trigger voltage calibration of the quantum computing measurement and control system through the aforementioned front-end service page. For ease of understanding, in conjunction with the above... Figure 3-a and Figure 9 Let's take an example to illustrate. Figure 9 for Figure 3-a The diagram shows a front-end service page when the AC time interval is triggered.

[0136] In the above Figure 3-a In the front-end service page shown, when the user triggers the area where the AC time interval is located, the following will be displayed: Figure 9 The front-end service page shown. Users are on... Figure 9 The front-end service page shows how to set the `ac_reset_time` (calibration interval duration) and trigger the execute button to initiate the voltage calibration operation. At this point, the front-end service device can generate the voltage calibration command corresponding to this operation.

[0137] Step S111: Send a voltage calibration command to the kernel module so that the kernel module triggers the voltage calibration of the quantum computing measurement and control system according to the calibration interval in the voltage calibration command.

[0138] For ease of understanding, the above will still be used. Figure 9 Let's take an example to illustrate. For example, users... Figure 9 After the voltage calibration operation is triggered, the kernel module, upon receiving the corresponding voltage command, can trigger voltage calibration of the quantum computing measurement and control system every 600 seconds. For example, it can send a trigger command to the quantum computing measurement and control system every 600 seconds, so that the quantum computing measurement and control system can perform voltage calibration according to the received trigger command.

[0139] In steps S110-S111 above, users can send voltage calibration commands through the aforementioned front-end service page, thereby prompting the task management device to trigger the automatic calibration of the quantum computing measurement and control system according to the calibration interval, realizing voltage calibration of the quantum computing measurement and control system, and improving the accuracy of quantum computing task execution results.

[0140] In the above embodiment, steps S101-S111 are executed sequentially. In practical applications, depending on the user's actions triggered on the front-end service page, steps S101-S102, S103, S104-S105, S106-S107, S108-S109, and S110-S111 can be executed independently or in combination. Here, the execution order of each step in steps S101-S111 is not specifically limited.

[0141] Based on the same inventive concept, and according to the functional configuration method provided in the above embodiments of this application, this application also provides a front-end service device. For example... Figure 10 As shown, Figure 10This is a schematic diagram of a first structure of a front-end service device provided in an embodiment of this application. The front-end service device provides a front-end service page and is communicatively connected to a task management device. The front-end service device includes:

[0142] The first generation unit 1001 is used to generate a function configuration instruction including target configuration parameters based on the function configuration operation triggered by the user on the front-end service page for the target function module in the task management device; wherein, the target function module is a kernel module used for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module used for device supervision during the operation of the task management device.

[0143] The first sending unit 1002 is used to send a function configuration instruction to the task management device so that the target function module in the task management device can perform function configuration according to the target configuration parameters included in the function configuration instruction.

[0144] Optionally, the aforementioned front-end service equipment may further include:

[0145] The second sending unit is used to send a simulator start command to the kernel module when the kernel module is in a locked state and the kernel module detects that the user has triggered a simulator start operation on the front-end service page, so that the kernel module can trigger the simulation execution of the quantum computing task based on the simulator start command.

[0146] Optionally, the aforementioned front-end service equipment may further include:

[0147] The second generation unit is used to generate user exclusive instructions based on the exclusive operation triggered by the user on the front-end service page for the quantum computing measurement and control system. The user exclusive instructions include: username and exclusive duration.

[0148] The third sending unit is used to send a user exclusive instruction to the kernel module, so that the kernel module can trigger the execution of the quantum computing task matching the username within the exclusive duration after receiving the user exclusive instruction.

[0149] Optionally, the aforementioned front-end service equipment may further include:

[0150] The third generation unit is used to generate a first operation instruction based on the first target operation triggered by the user on the front-end service page for the data related to the execution process of the quantum computing task. The first target operation is a data cleaning operation or a log transfer operation. The first operation instruction includes: the instruction number corresponding to the first target operation, the operation interval duration / operation data volume.

[0151] The fourth sending unit is used to send a first operation instruction to the monitoring module through the kernel module, so that after receiving the first operation instruction, the monitoring module will trigger the execution of the first target operation corresponding to the instruction number according to the operation interval duration / operation data volume.

[0152] Optionally, the aforementioned front-end service equipment may further include:

[0153] The fourth generation unit is used to generate a second operation instruction based on the second target operation triggered by the user on the front-end service page for the quantum computing task. The second target operation includes: an inter-queue operation, a priority adjustment operation, a deletion operation or a retry operation for any quantum computing task, a clear operation for all quantum computing tasks, and a recovery operation for the corresponding thread of the quantum computing task.

[0154] The fifth sending unit is used to send a second operation instruction to the kernel module so that the kernel module can execute the second target operation according to the received second operation.

[0155] Optionally, the aforementioned task management equipment is communicatively connected to the quantum computing measurement and control system;

[0156] The aforementioned front-end service equipment may also include:

[0157] The fifth generation unit is used to generate voltage calibration instructions based on the voltage calibration operation triggered by the user on the front-end service page. The voltage calibration instructions include the calibration interval duration.

[0158] The sixth sending unit is used to send voltage calibration commands to the kernel module so that the kernel module triggers the voltage calibration of the quantum computing measurement and control system according to the calibration interval in the voltage calibration command.

[0159] Optionally, if the target functional module is a kernel module, the functional configuration operation is a first configuration operation to change the running status of the kernel module, a second configuration operation to schedule tasks during the execution of quantum computing tasks, or a third configuration operation to monitor tasks during the execution of quantum computing tasks.

[0160] If the target functional module is a monitoring module, then the functional configuration operation is the fourth configuration operation for monitoring the operation of the task management device.

[0161] Optionally, the target configuration parameters corresponding to the first configuration operation mentioned above include one or more of the following: running mode, kernel state, first function option, and kernel lock state. The first function option is used to indicate whether the kernel module enables the performance analysis function.

[0162] The target configuration parameters corresponding to the second configuration operation mentioned above include one or more of the following: scheduling mode, manager type, verification type, number of threads, number of execution modules, parallel compilation limit, sliding window size, scheduling length, number of retries, safety bit distance, warning bit distance, and task queuing coefficient.

[0163] The target configuration parameters corresponding to the third configuration operation mentioned above include one or more of the following: timeout time, number of timeout wait rounds, and second function option. The second function option is used to indicate whether the kernel module enables the task check switch.

[0164] The target configuration parameters corresponding to the fourth configuration operation mentioned above include one or more of the following: alarm configuration parameters, operation configuration parameters, and monitoring water level parameters for system resources.

[0165] Optionally, the above operating modes include: settings mode, instrument mode, experiment mode, and online mode;

[0166] The kernel states mentioned above include: initial state, offline state, abnormal state, and running state;

[0167] The timeout periods mentioned above include: execution timeout, compilation timeout, thread timeout, and task timeout.

[0168] The above alarm configuration parameters include: platform identifier, task alarm level, service alarm level, hardware alarm level, and alarm service connection heartbeat interval;

[0169] The above operating configuration parameters include: the third function option, the fourth function option, and the timer. The third function option indicates whether the monitoring module enables monitoring and data acquisition, and the fourth function option indicates whether the monitoring module enables alarms.

[0170] The above-mentioned monitoring water level parameters include: normal water level level, high water level level, effective time for abnormal triggering, abnormal triggering interval, monitoring and acquisition interval, abnormal alarm triggering category, number of repeated abnormal alarm triggers, and heartbeat interval configuration.

[0171] Through the front-end service device provided in this application embodiment, users can trigger function configuration operations for target functional modules in the task management device via the front-end service page provided by the front-end service device. At this time, the front-end service device can generate a function configuration instruction including target configuration parameters based on the function configuration operation, and then send the function configuration instruction to the task management device. The target functional module in the task management device then performs function configuration according to the target configuration parameters carried in the received function configuration instruction. Therefore, the function configuration of each functional module in the task management device can be realized through the front-end service page provided by the front-end service device; that is, the function configuration of the task management device is achieved through the front-end service page.

[0172] Based on the same inventive concept, and according to the functional configuration method provided in the above embodiments of this application, this application also provides a front-end service device, such as... Figure 11As shown, it includes a processor 1101, a communication interface 1102, a memory 1103, and a communication bus 1104. The processor 1101, communication interface 1102, and memory 1103 communicate with each other via the communication bus 1104.

[0173] Memory 1103 is used to store computer programs;

[0174] When the processor 1101 executes the program stored in the memory 1103, it implements any of the above-described functional configuration method steps.

[0175] The communication bus mentioned in the aforementioned front-end service equipment can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0176] The communication interface is used for communication between the aforementioned front-end service device and other devices.

[0177] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0178] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0179] Based on the same inventive concept, and according to the functional configuration method provided in the above embodiments of this application, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the above functional configuration methods.

[0180] Based on the same inventive concept, and according to the functional configuration method provided in the above embodiments of this application, this application also provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute any of the functional configuration methods in the above embodiments.

[0181] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0182] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0183] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, embodiments such as front-end service devices, computer-readable storage media, and computer program products are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0184] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. A function configuration method, characterized in that, A front-end service device is applied to provide front-end service pages, the front-end service device being communicatively connected to a task management device, the method comprising: Based on the user's function configuration operation triggered on the front-end service page for the target function module in the task management device, a function configuration instruction including target configuration parameters is generated; wherein, the target function module is a kernel module for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module for device supervision during the operation of the task management device; The function configuration instruction is sent to the task management device so that the target function module in the task management device performs function configuration according to the target configuration parameters included in the function configuration instruction.

2. The method according to claim 1, characterized in that, The method further includes: When the kernel module is in a locked state, if it detects that the user has triggered a start operation for the simulator on the front-end service page, it sends a simulator start command to the kernel module so that the kernel module can trigger the simulation execution of the quantum computing task based on the simulator start command.

3. The method according to claim 1, characterized in that, The method further includes: Based on the exclusive operation triggered by the user on the front-end service page for the quantum computing measurement and control system, a user exclusive instruction is generated, which includes: username and exclusive duration; A user exclusive instruction is sent to the kernel module so that, upon receiving the user exclusive instruction, the kernel module triggers the execution of a quantum computing task matching the username within the exclusive duration.

4. The method according to claim 1, characterized in that, The method further includes: Based on the first target operation triggered by the user on the front-end service page for data related to the execution process of the quantum computing task, a first operation instruction is generated. The first target operation is a data cleaning operation or a log transfer operation. The first operation instruction includes: the instruction number corresponding to the first target operation, the operation interval duration / operation data volume. The kernel module sends the first operation instruction to the monitoring module, so that after receiving the first operation instruction, the monitoring module triggers the execution of the first target operation corresponding to the instruction number according to the operation interval duration / the operation data volume.

5. The method according to claim 1, characterized in that, The method further includes: Based on the second target operation triggered by the user for the quantum computing task on the front-end service page, a second operation instruction is generated. The second target operation includes: queueing operation, priority adjustment operation, deletion operation or retry operation for any quantum computing task, clearing operation for all quantum computing tasks, and recovery operation for the corresponding thread of the quantum computing task. The kernel module is sent the second operation instruction so that the kernel module performs the second target operation according to the received second operation.

6. The method according to claim 1, characterized in that, The task management device is communicatively connected to the quantum computing measurement and control system. The method further includes: Based on the voltage calibration operation triggered by the user on the front-end service page, a voltage calibration instruction is generated, which includes the calibration interval duration; The voltage calibration command is sent to the kernel module so that the kernel module triggers the voltage calibration of the quantum computing measurement and control system according to the calibration interval in the voltage calibration command.

7. The method according to claim 1, characterized in that, If the target functional module is the kernel module, then the functional configuration operation is a first configuration operation to change the running status of the kernel module, a second configuration operation to schedule tasks during the execution of quantum computing tasks, or a third configuration operation to monitor tasks during the execution of quantum computing tasks. If the target functional module is the monitoring module, then the functional configuration operation is the fourth configuration operation for monitoring the operation of the task management device.

8. The method according to claim 7, characterized in that, The target configuration parameters corresponding to the first configuration operation include one or more of the following: running mode, kernel state, first function option, and kernel lock state. The first function option is used to indicate whether the kernel module enables the performance analysis function. The target configuration parameters corresponding to the second configuration operation include one or more of the following: scheduling mode, manager type, verification type, number of threads, number of execution modules, parallel compilation limit, sliding window size, scheduling length, number of retries, safety bit distance, warning bit distance, and task queuing coefficient. The target configuration parameters corresponding to the third configuration operation include one or more of the timeout time, timeout waiting rounds, and second function options. The second function options are used to indicate whether the kernel module enables the task check switch. The target configuration parameters corresponding to the fourth configuration operation include one or more of the following: alarm configuration parameters, operation configuration parameters, and monitoring water level parameters for system resources.

9. The method according to claim 8, characterized in that, The operating modes include: setting mode, instrument mode, experiment mode, and online mode; The kernel states include: initial state, offline state, abnormal state, and running state; The timeout period includes: execution timeout, compilation timeout, thread timeout, and task timeout. The alarm configuration parameters include: platform identifier, task alarm level, service alarm level, hardware alarm level, and alarm service connection heartbeat interval. The operation configuration parameters include: a third function option, a fourth function option, and a timer. The third function option indicates whether the monitoring module enables monitoring and data acquisition, and the fourth function option indicates whether the monitoring module enables alarms. The monitoring water level parameters include: normal water level level, high water level level, effective time for abnormal triggering, abnormal triggering interval, monitoring and acquisition interval, abnormal alarm triggering category, number of repeated abnormal alarm triggers, and heartbeat interval configuration.

10. A front-end service device, characterized in that, The front-end service device provides a front-end service page and is communicatively connected to the task management device. The front-end service device includes: The first generation unit is used to generate a function configuration instruction including target configuration parameters based on the function configuration operation triggered by the user on the front-end service page for the target function module in the task management device; wherein, the target function module is a kernel module for task scheduling and task supervision during the execution of quantum computing tasks, or a monitoring module for device supervision during the operation of the task management device; The first sending unit is configured to send the function configuration instruction to the task management device, so that the target function module in the task management device performs function configuration according to the target configuration parameters included in the function configuration instruction.

Images