A quick operation method and a front-end service device

Abstract

The embodiment of the application provides a quick operation method and a front-end service device. The scheme is as follows: when a user triggers a first quick operation in a front-end service page, if a first running parameter of a kernel module at a current time does not match a second running parameter corresponding to the first quick operation, the first running parameter is adjusted to the second running parameter, wherein the first quick operation is used for clearing all quantum computing tasks scheduled and managed in the kernel module, and the running parameter of the kernel module includes a running mode corresponding to the kernel module, a kernel state and a locking state; all quantum computing tasks scheduled and managed by the kernel module are deleted under the second running parameter of the kernel module; and first feedback information for the first quick operation is displayed on the front-end service page according to the clearing condition of the quantum computing tasks in the kernel module. Through the technical scheme provided by the embodiment of the application, the quick operation of clearing all quantum computing tasks in a task management device is realized.

Description

Technical Field

[0001] This application relates to the field of quantum computing technology, and in particular to a fast operation method and 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 quick operation method and front-end service device to achieve quick clearing of all quantum computing tasks in a task management device. The specific technical solution is as follows:

[0005] This application provides a quick operation 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, which includes a kernel module for quantum computing task scheduling and management. The method includes:

[0006] When a user triggers a first shortcut operation on the front-end service page, if the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation, the first running parameter is adjusted to the second running parameter. The first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state and lock state corresponding to the kernel module.

[0007] When the kernel module is under the second operating parameter, delete all quantum computing tasks scheduled and managed by the kernel module.

[0008] Based on the clearing status of quantum computing tasks in the kernel module, the first feedback information for the first shortcut operation is displayed on the front-end service page.

[0009] 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 task management device includes a kernel module for quantum computing task scheduling management. The front-end service device includes:

[0010] The first adjustment unit is used to adjust the first running parameter to the second running parameter when the user triggers the first shortcut operation on the front-end service page, if the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation. The first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state and lock state corresponding to the kernel module.

[0011] The deletion unit is used to delete all quantum computing tasks scheduled and managed by the kernel module when the kernel module is under the second running parameter.

[0012] The first display unit is used to display first feedback information for the first quick operation on the front-end service page based on the clearing status of quantum computing tasks in the kernel module.

[0013] 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;

[0014] Memory, used to store computer programs;

[0015] When a processor executes a program stored in memory, it implements any of the shortcut operation method steps described above.

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

[0017] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the shortcut operation methods described above.

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

[0019] The technical solution provided in this application embodiment, when a user triggers a first shortcut operation corresponding to all quantum computing tasks scheduled and managed by the kernel module in the task management device, adjusts the kernel module's running parameters to the second running parameters corresponding to the first shortcut operation, and deletes all quantum computing tasks scheduled and managed by the kernel module when the kernel module is under the second running parameters. Based on the clearing status of the quantum computing tasks, the first feedback information for the first shortcut operation is displayed on the front-end service page.

[0020] Since the clearing of all quantum computing tasks scheduled and managed by the kernel module in the task management module is triggered by the front-end service device, after the user triggers the first quick operation on the front-end service page provided by the front-end service device, the front-end service device will directly display the first feedback information determined based on the clearing status of quantum computing tasks in the kernel module, thus realizing the quick operation of clearing all quantum computing tasks in the task management device.

[0021] 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

[0022] 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.

[0023] Figure 1 This is a schematic diagram of a first type of quick operation method provided in the embodiments of this application;

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

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

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

[0027] Figure 3 A schematic diagram of a front-end service page for quick operations provided in an embodiment of this application;

[0028] Figure 4 This is a second flowchart illustrating the quick operation method provided in the embodiments of this application;

[0029] Figure 5 A third flowchart illustrating the quick operation method provided in the embodiments of this application;

[0030] Figure 6 This is a fourth flowchart illustrating the quick operation method provided in the embodiments of this application;

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

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

[0033] 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.

[0034] To address the problems in related technologies, embodiments of this application provide a quick operation method. For example... Figure 1 As shown, Figure 1 This is a schematic flowchart of a first embodiment of the shortcut operation method provided in this application. The method is applied to a front-end service device that provides a front-end service page. This front-end service device is communicatively connected to a task management device, which includes a kernel module for quantum computing task scheduling and management. Figure 1 The method shown includes the following steps.

[0035] Step S101: When the user triggers the first shortcut operation on the front-end service page, if the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation, the first running parameter is adjusted to the second running parameter. The first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state and lock state corresponding to the kernel module.

[0036] Step S102: With the kernel module running under the second operating parameter, delete all quantum computing tasks scheduled and managed by the kernel module.

[0037] Step S103: Based on the clearing status of quantum computing tasks in the kernel module, display the first feedback information for the first quick operation on the front-end service page.

[0038] like Figure 2-a As shown, Figure 2-a This 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.

[0039] 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.

[0040] 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, a monitoring module, and a driver module.

[0041] 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 controls the software programs of the driver modules and performs platform anomaly recovery when platform anomalies are detected.

[0042] 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 timed cleanup of historical tasks in Redis.

[0043] The aforementioned driver module is used for compiling and distributing quantum computing tasks during the quantum computing process, as well as parsing feedback information from the quantum computing measurement and control system during the quantum computing process.

[0044] 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.

[0045] In this embodiment, the kernel module is used for scheduling and managing quantum computing tasks, the monitoring module is used for monitoring and management, and the driver module is used for compiling and distributing quantum computing tasks, and this is not intended to limit the scope of the application.

[0046] 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. This 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.

[0047] 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.

[0048] 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-c The quantum computing measurement and control system shown is used as an example for illustration and is not intended to be limiting.

[0049] pass Figure 1 The method shown involves adjusting the kernel module's running parameters to the second running parameters corresponding to the first quick operation when the user triggers the first quick operation for all quantum computing tasks scheduled and managed by the kernel module in the task management device. Then, when the kernel module is under the second running parameters, all quantum computing tasks scheduled and managed by the kernel module are deleted. Based on the clearing status of the quantum computing tasks, the first feedback information for the first quick operation is displayed on the front-end service page.

[0050] Since the clearing of all quantum computing tasks scheduled and managed by the kernel module in the task management module is triggered by the front-end service device, after the user triggers the first quick operation on the front-end service page provided by the front-end service device, the front-end service device will directly display the first feedback information determined based on the clearing status of quantum computing tasks in the kernel module, thus realizing the quick operation of clearing all quantum computing tasks in the task management device.

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

[0052] Regarding step S101 above, when a user triggers the first shortcut operation on the front-end service page, if the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation, the first running parameter will be adjusted to the second running parameter. The first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state, and lock state corresponding to the kernel module.

[0053] In this embodiment, the front-end service device provides a front-end service page, which includes quick operation functions. For ease of understanding, in conjunction with... Figure 3 Let's take an example to illustrate. Figure 3 This is a schematic diagram of a front-end service page for quick operations provided in an embodiment of this application. In the above... Figure 3 In the front-end service page shown, users can trigger a shortcut operation (referred to as the first shortcut operation) to clear all quantum computing tasks scheduled and managed in the kernel module by triggering button 302, which is used to automatically clear all tasks.

[0054] In the above Figure 3 The front-end service page shown also includes other shortcut operations, such as the shortcut operations corresponding to buttons 301, 303, and 304. (For...) Figure 3 Each shortcut operation, as shown, involves a series of processing flows in both the front-end service device and the task management device. When a user triggers any shortcut operation, the front-end service device will initiate the corresponding series of processing flows, thereby displaying the final processing result on the front-end service page. This shortens the processing time of the shortcut operation's corresponding processing flow and makes the intermediate processing flow imperceptible to the user.

[0055] In addition, for each shortcut operation, the kernel module in the aforementioned task management device has a corresponding set of operating parameters. These operating parameters include the kernel module's operating mode, kernel state, and lock state.

[0056] In one optional embodiment, the above operating modes may include: setup mode, instrument mode, experiment mode, and online mode.

[0057] The above configuration mode can be used to configure the kernel module and the quantum computing measurement and control system. In other words, in configuration mode, users can configure the parameters of the kernel module and the quantum computing measurement and control system.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] In an optional embodiment, the kernel states described above may include: initial state, offline state, abnormal state, and running state.

[0062] When the kernel module is in the initial state described above, 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.

[0063] 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.

[0064] 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, and the kernel state will automatically adjust from the running mode to the aforementioned instrument mode.

[0065] 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.

[0066] In the embodiments of this application, the modes included in the operating mode corresponding to the above-mentioned kernel module and the states included in the kernel state can be set according to user needs, etc., and are not specifically limited here.

[0067] In an optional embodiment, the above-mentioned locking state may include: kernel locked state and kernel unlocked state.

[0068] The kernel lock state described above locks the kernel module, and kernel locking can be performed in any operating mode. When the kernel is locked in the experimental mode described above, the kernel module will suspend the execution of all quantum computing tasks. The kernel unlock state described above is only effective when the kernel is locked. When the kernel module switches to the kernel unlock state, all locks on the task scheduler in the kernel module will be unlocked simultaneously, and the normal execution of quantum computing tasks will resume.

[0069] In an optional embodiment, the running parameters (denoted as the second running parameters) corresponding to the first shortcut operation mentioned above include the running mode, kernel state, and lock state, which are respectively the setting mode, initial state, and kernel lock state.

[0070] After triggering the first shortcut operation, the user can determine whether the kernel module's current running parameters (denoted as the first running parameters) match the second running parameters corresponding to the first shortcut operation, that is, whether the first running parameters are the same as the second running parameters.

[0071] In an optional embodiment, when the first running parameters of the kernel module at the current moment do not match the second running parameters corresponding to the first shortcut operation, the front-end service device can send a first operation instruction for the first shortcut operation to the task management device, so that when the kernel module in the task management device receives the first operation instruction, it sequentially adjusts the current running parameters, including the lock state, kernel state and running mode, to the kernel lock state, the initial state and the setting mode, to obtain the second running parameters. The setting mode is used to configure the parameters of the kernel module.

[0072] Specifically, when the first operating parameter differs from the second operating parameter, the front-end service device can trigger the kernel module to adjust the corresponding operating parameters. At this time, the front-end service device can send a first operation instruction for the first shortcut operation to the task management device. The kernel module in the task management device will receive this first operation instruction. Then, the kernel module can adjust the current operating parameters (i.e., the first operating parameter) to the second operating parameter according to the received first operation instruction.

[0073] In this embodiment, the order in which the parameters in the kernel module's running parameters are adjusted will vary depending on the user-triggered shortcut operation. For example, for the first shortcut operation, when adjusting the first running parameter to the second running parameter, the kernel module can adjust it sequentially according to the order of locked state, kernel state, and running mode. That is, the parameters in the first running parameter are adjusted sequentially to the kernel locked state, initial state, and setting mode to obtain the second running parameter. The order in which the parameters in the kernel module's running parameters are adjusted under each shortcut operation can be found in the description below, and will not be specifically explained here.

[0074] In one optional embodiment, after the kernel module completes the adjustment of the current running parameters, it can send a notification message to the front-end service device indicating that the adjustment of the running parameters is complete.

[0075] Regarding step S102 above, which is to delete all quantum computing tasks scheduled and managed by the kernel module when the kernel module is under the second running parameter.

[0076] In an optional embodiment, when the kernel module is under the second operating parameter, the front-end service device can send a task clearing instruction to the task management device, so that when the kernel module in the task management device receives the task clearing instruction, it deletes all quantum computing tasks in the task queue and sends feedback information indicating the clearing status of the quantum computing tasks to the front-end service device.

[0077] Specifically, after the kernel module adjusts the current operating parameters to the second operating parameter, the front-end service device can determine that the kernel module has completed the adjustment based on the notification message sent by the kernel module. At this time, the front-end service device can trigger the kernel module to clear the quantum computing tasks it schedules and manages. That is, the front-end service device can send a task clearing command to the task management device. This task clearing command will be received by the kernel module in the task management device.

[0078] Within the kernel module, monitoring and management of quantum computing tasks are achieved through the monitoring and management of various task queues. Upon receiving the aforementioned task clearing command, the kernel module can clear all quantum computing tasks from all task queues, thus clearing the quantum computing tasks. Based on the clearing status of the quantum computing tasks, the kernel module can generate feedback information indicating the clearing status (denoted as the first feedback information) and send this first feedback information to the front-end service device.

[0079] The aforementioned task queues may include 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 scheduled and managed by the kernel module, or on the number of task queues.

[0080] In addition, the aforementioned first feedback information can indicate that the quantum computing task was successfully cleared, or it can indicate that the quantum computing task was not cleared.

[0081] In an optional embodiment, when the first feedback information indicates that the quantum computing task has failed to clear, the first feedback information may carry a brief prompt indicating the reason for the failure.

[0082] Regarding step S103 above, that is, based on the clearing status of quantum computing tasks in the kernel module, the first feedback information for the first quick operation is displayed on the front-end service page.

[0083] In this step, the front-end service device can receive initial feedback information from the kernel module indicating the status of the quantum computing task cleanup. At this point, the front-end service device can display this initial feedback information on the front-end service page.

[0084] The aforementioned initial feedback information may be displayed via pop-up windows or notification messages. No specific limitations are made regarding the method of displaying this initial feedback information.

[0085] In an optional embodiment, according to the above... Figure 1 In addition to the method shown, this application also provides a quick operation method. For example... Figure 4 As shown, Figure 4This is a second flowchart illustrating the quick operation method provided in the embodiments of this application. Figure 4 The method shown has been augmented with the following steps, namely steps S104-S105.

[0086] Step S104: When the first running parameters match the second running parameters, execute the step of deleting all quantum computing tasks scheduled and managed by the kernel module.

[0087] In this step, when the current running parameters of the kernel module match the second running parameters corresponding to the first shortcut operation, that is, when the first running parameters and the second running parameters are the same, the front-end service device can determine that the kernel module is already under the second running parameters. At this time, the front-end service device can execute the step S102 above to delete all quantum computing tasks scheduled and managed by the kernel module.

[0088] In an optional embodiment, when determining whether the current running parameters of the kernel module match the second running parameters corresponding to the first shortcut operation, the front-end service device can obtain the current running parameters of the kernel module and compare them with the second running parameters. If the first and second running parameters are the same, the aforementioned first operation instruction is sent to the task management device. If the first and second running parameters are different, the aforementioned first operation instruction is not sent, and the step of deleting the quantum computing task in step S102 is directly executed, followed by step S103.

[0089] In another optional embodiment, when determining whether the kernel module's current operating parameters match the second operating parameters corresponding to the first shortcut operation, the front-end service device can directly send the first operation instruction to the task management device. If the kernel module's current operating parameters differ from the second operating parameters, it adjusts the operating parameters; if the first and second operating parameters are the same, it does not adjust the operating parameters and directly sends the notification message.

[0090] Through the above step S104, when the kernel module's current running parameters match the second running parameters, the front-end service device directly triggers the clearing of the quantum computing task.

[0091] The steps S101 and S104 described above are steps that are executed when the kernel module's current running parameters are different. Here, the execution of steps S101 and S104 is not specifically limited.

[0092] Step S105: Adjust the second operating parameter to the first operating parameter.

[0093] The adjustment of the kernel module's corresponding running parameters in step S105 above can be done in the same way as the running parameter adjustment in step S101 above, and will not be explained in detail here.

[0094] Step S105 is executed after step S102. Here, there is no specific limitation on the execution order of steps S105 and S103.

[0095] Through the above step S105, after clearing all quantum computing tasks according to user requirements, the front-end service device can restore the kernel module's operating parameters to the first operating parameters mentioned above, that is, restore the kernel module's operating parameters to the operating parameters before the quantum computing tasks were cleared, thereby realizing the restoration of the kernel module's operating parameters.

[0096] In an optional embodiment, the task management device further includes a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks.

[0097] In an optional embodiment, according to the above... Figure 1 In addition to the method shown, this application also provides a quick operation method. For example... Figure 5 As shown, Figure 5 This is a third flowchart illustrating a quick operation method provided in an embodiment of this application. The method includes the following steps.

[0098] Step S501: When the user triggers the second shortcut operation on the front-end service page, the locking state of the kernel module is adjusted to the kernel locking state, and the thread state of all threads corresponding to the driver module at the current moment is obtained. The second shortcut operation is used to restart the driver module.

[0099] As mentioned above Figure 3 As shown, the front-end service device also provides a quick operation for restarting the aforementioned driver module (denoted as the second quick operation), namely the above... Figure 3 The button 303 shown is for automatically restarting the Qstream service. The Qstream service is the quantum computing task compilation and distribution function provided by the aforementioned driver module. When the user... Figure 3 When button 303 is triggered on the front-end service page shown, the second quick operation is triggered.

[0100] In this embodiment, the aforementioned second shortcut operation has corresponding operating parameters (denoted as the fifth operating parameter). In this fifth operating parameter, the lock state is a kernel lock state, the operating mode can be any operating mode, and the kernel state can be any kernel state. After the user triggers the aforementioned second shortcut operation on the front-end service page, the front-end service page can adjust the current operating parameters of the kernel module to the fifth operating parameter, that is, adjust the lock state in the current operating parameters of the kernel module to the aforementioned kernel lock state.

[0101] The aforementioned driver module can utilize multiple threads to compile and deploy quantum computing tasks. After adjusting the kernel module's current running parameters to the fifth running parameter mentioned above, the front-end service device can obtain the current thread state of each thread in the driver module.

[0102] For each thread, its corresponding thread state can be either idle (IDLE state) or non-idle (e.g., occupied state). Here, no specific limitations are made regarding the non-idle state of the thread.

[0103] Step S502: When the thread state corresponding to each thread is in an idle state, restart the driver module through the monitoring module.

[0104] When all threads are in the aforementioned idle state, the front-end service device can trigger a restart of the driver module. For example, the front-end service device can send a restart command to the task management device. Upon receiving the restart command, the kernel module in the task management device can forward it to the monitoring module. The monitoring module can then shut down all threads corresponding to the driver module and restart them, thus restarting the driver module.

[0105] In one optional embodiment, the monitoring module can send feedback information (denoted as the second feedback information) indicative of the driver module's restart status to the kernel module based on the driver module's restart status. The kernel module then forwards the received second feedback information to the aforementioned front-end service device.

[0106] The second feedback information mentioned above can indicate that the driver module restarted successfully or failed to restart.

[0107] In an optional embodiment, when the second feedback information indicates that the driver module has failed to restart, the second feedback information may carry a brief prompt indicating the reason for the failure.

[0108] Step S503: Based on the restart status of the driver module, display the second feedback information for the second quick operation on the front-end service page.

[0109] In this step, after receiving the second feedback information, the front-end service device can display the second feedback information on the front-end service page. The display method of the second feedback information can refer to the display method of the first feedback information, and will not be specifically described here.

[0110] In steps S501-S503 above, users can trigger a restart operation on the driver module in the task management device through the quick operation service provided by the front-end service page, thereby enabling the front-end service device and the task management device to automatically restart the driver module and effectively deal with the impact of driver module abnormality.

[0111] Step S504: When the thread state corresponding to any thread is not idle, display the third feedback information for the second shortcut operation on the front-end service page. The third feedback information is used to indicate that the driver module cannot be restarted during the execution of the quantum computing task.

[0112] In this step, for each thread corresponding to the aforementioned driver module, if the thread's current state is the non-idle state, the front-end service device can determine that the driver module is currently executing a quantum computing task. At this time, the monitoring module in the task management device can choose not to respond to the restart command sent by the front-end service device, and the monitoring module can send feedback information (referred to as the third feedback information) to the kernel module indicating that the quantum computing task cannot be restarted during execution. The kernel module forwards the received third feedback information to the front-end service device.

[0113] After receiving the aforementioned third feedback information, the front-end service device can display the third feedback information on the front-end service page. The display method of the third feedback information can refer to the display method of the first feedback information, and will not be specifically described here.

[0114] In step S504 above, when any thread in the driver module is executing a quantum computing task, the driver module is not restarted to ensure the continued execution of the quantum computing task.

[0115] Steps S502 and S504 described above are steps executed separately when the thread states of each thread in the driver module are different. Here, the execution of steps S502 and S504 is not specifically limited.

[0116] In the above embodiments, the restart process of the driver module in the task management device is described using the example of the front-end service device determining the current thread state of each thread. Alternatively, the front-end service device can directly send the restart command to the task management device. Upon receiving the restart command, the monitoring module in the task management device can determine whether to respond to the restart command, i.e., whether to restart the driver module, based on the current thread state of each thread in the driver module.

[0117] In an optional embodiment, according to the above... Figure 1 In addition to the method shown, this application also provides a quick operation method. For example... Figure 6 As shown, Figure 6 This is a fourth flowchart illustrating a quick operation method provided in an embodiment of this application. The method includes the following steps.

[0118] Step S601: When the user triggers the third shortcut operation on the front-end service page, the third running parameter of the kernel module at the current moment is adjusted to the fourth running parameter corresponding to the third shortcut operation. The third shortcut operation is used to adjust the running mode of the kernel module at the current moment to the target running mode.

[0119] As mentioned above Figure 3 As shown, the front-end service device also provides a shortcut operation (referred to as the third shortcut operation) to adjust the current running mode of the kernel module. Figure 3 The button 301 is shown for automatically switching to experimental mode, and the button 304 is shown for automatically switching to instrument mode. Users can... Figure 3 The aforementioned third shortcut operation is triggered by triggering button 301 or button 304 on the front-end service page shown.

[0120] In this embodiment of the application, the aforementioned third shortcut operation has corresponding operating parameters (denoted as the fourth operating parameter). For example, the fourth operating parameter corresponding to the third shortcut operation indicating switching to experimental mode can be: operating status, experimental mode, and kernel unlock status; the fourth operating parameter corresponding to the third shortcut operation indicating switching to instrument mode can be: operating status, instrument mode, and kernel lock status.

[0121] In an optional embodiment, when the user triggers the third shortcut operation, if the target running mode is the experimental mode that indicates the normal execution of the quantum computing task, the front-end service device can sequentially adjust the kernel state, running mode, and locked state in the third running parameters corresponding to the kernel module at the current moment to the running state, experimental mode, and kernel unlocked state.

[0122] In another optional embodiment, when the user triggers the third shortcut operation, if the target operating mode is the instrument mode that indicates support for running instrument commands and hardware layer tasks, the front-end service device can sequentially adjust the locking state, kernel state, and operating mode in the third operating parameters corresponding to the kernel module at the current moment to the kernel locking state, operating state, and instrument mode.

[0123] The adjustment process for the third operating parameter mentioned above can be referred to the adjustment process for the second operating parameter mentioned above, and will not be explained in detail here.

[0124] In an optional embodiment, after the kernel module completes the adjustment of its current operating parameters, it can send feedback information (denoted as the fourth feedback information) to the front-end service device indicating the kernel module's operating mode switching status. The front-end service device will receive this fourth feedback information.

[0125] Step S602: Based on the switching of the kernel module's running mode, display the fourth feedback information for the third quick operation on the front-end service page.

[0126] In this step, after receiving the aforementioned fourth feedback information, the front-end service device can display the fourth feedback information on the front-end service page. The display method of the fourth feedback information can refer to the display method of the first feedback information, and will not be specifically described here.

[0127] Through the above steps S601-S602, users can trigger a third shortcut operation on the front-end service page according to their own needs, thereby realizing the automatic switching of the kernel module's current running mode.

[0128] In the above embodiments, only the above-described Figure 3 The shortcut operation shown is used as an example for illustration. In addition, users can design other shortcut operations on the front-end service page according to their own needs and other factors. For example, a shortcut service to adjust the current running mode of the aforementioned kernel module to the aforementioned online mode.

[0129] Based on the same inventive concept and the quick operation method provided in the above embodiments of this application, this application also provides a front-end service device. For example... Figure 7 As shown, Figure 7 This 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 task management device includes a kernel module for quantum computing task scheduling and management. The front-end service device includes:

[0130] The first adjustment unit 701 is used to adjust the first running parameter to the second running parameter when the user triggers the first shortcut operation in the front-end service page. If the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation, the first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state and lock state corresponding to the kernel module.

[0131] Deletion unit 702 is used to delete all quantum computing tasks scheduled and managed by the kernel module when the kernel module is under the second running parameter;

[0132] The first display unit 703 is used to display the first feedback information for the first quick operation on the front-end service page based on the clearing status of quantum computing tasks in the kernel module.

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

[0134] The calling unit is used to call the above-mentioned deletion unit 702 to execute the step of deleting all quantum computing tasks managed by the kernel module scheduling when the first running parameters match the second running parameters.

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

[0136] The second adjustment unit is used to adjust the second running parameter to the first running parameter after deleting all quantum computing tasks scheduled and managed by the kernel module.

[0137] Optionally, the task management device may also include a monitoring module for monitoring and management and a driver module for compiling and distributing quantum computing tasks;

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

[0139] When a user triggers the second quick action on the front-end service page, the kernel module's locking state is adjusted to the kernel locked state, and the thread state of all threads corresponding to the driver module at the current moment is obtained. The second quick action is used to restart the driver module.

[0140] The restart unit is used to restart the driver module through the monitoring module when the thread state corresponding to each thread is in an idle state.

[0141] The second display unit is used to display second feedback information for the second quick operation on the front-end service page based on the restart status of the driver module.

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

[0143] The third display unit is used to display third feedback information for the second shortcut operation on the front-end service page when the thread state corresponding to any thread is not idle. The third feedback information is used to indicate that the driver module cannot be restarted during the execution of the quantum computing task.

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

[0145] The third adjustment unit is used to adjust the third running parameter of the kernel module at the current moment to the fourth running parameter corresponding to the third quick operation when the user triggers the third quick operation on the front-end service page. The third quick operation is used to adjust the running mode of the kernel module at the current moment to the target running mode.

[0146] The fourth display unit is used to display a fourth feedback message for the third shortcut operation on the front-end service page, based on the switching of the kernel module's running mode.

[0147] Optionally, the aforementioned fourth display unit can be used to adjust the kernel state, operating mode, and locked state in the third operating parameters corresponding to the kernel module at the current moment to the operating state, experimental mode, and kernel unlocked state if the target operating mode is the experimental mode that indicates the normal execution of the quantum computing task.

[0148] If the target operating mode is the instrument mode that indicates support for running instrument commands and hardware layer tasks, then the lock state, kernel state, and operating mode in the third operating parameters corresponding to the kernel module at the current moment will be adjusted sequentially to kernel lock state, operating state, and instrument mode.

[0149] Optionally, the first adjustment unit 701 can be specifically used to send a first operation instruction for the first shortcut operation to the task management device when the first running parameters of the kernel module at the current moment do not match the second running parameters corresponding to the first shortcut operation. This allows the kernel module in the task management device to adjust the current running parameters, including the lock state, kernel state, and running mode, to the kernel lock state, initial state, and setting mode in sequence when it receives the first operation instruction, thereby obtaining the second running parameters. The setting mode is used for configuring the parameters of the kernel module.

[0150] Optionally, the deletion unit 702 described above can be used to send a task clearing instruction to the task management device when the kernel module is under the second running parameter, so that when the kernel module in the task management device receives the task clearing instruction, it deletes all quantum computing tasks in the task queue and sends feedback information indicating the clearing status of the quantum computing tasks to the front-end service device.

[0151] When a user triggers a first quick operation corresponding to all quantum computing tasks scheduled and managed by the kernel module in the task management device, the operating parameters of the kernel module are adjusted to the second operating parameters corresponding to the first quick operation. When the kernel module is under the second operating parameters, all quantum computing tasks scheduled and managed by the kernel module are deleted. Based on the clearing status of the quantum computing tasks, the first feedback information for the first quick operation is displayed on the front-end service page.

[0152] Since the clearing of all quantum computing tasks scheduled and managed by the kernel module in the task management module is triggered by the front-end service device, after the user triggers the first quick operation on the front-end service page provided by the front-end service device, the front-end service device will directly display the first feedback information determined based on the clearing status of quantum computing tasks in the kernel module, thus realizing the quick operation of clearing all quantum computing tasks in the task management device.

[0153] Based on the same inventive concept, and according to the quick operation method provided in the above embodiments of this application, this application also provides a front-end service device, such as... Figure 8 As shown, it includes a processor 801, a communication interface 802, a memory 803, and a communication bus 804. The processor 801, communication interface 802, and memory 803 communicate with each other via the communication bus 804.

[0154] Memory 803 is used to store computer programs;

[0155] The processor 801, when executing the program stored in the memory 803, implements any of the shortcut operation method steps described above.

[0156] 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.

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

[0158] 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.

[0159] 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.

[0160] Based on the same inventive concept, and according to the shortcut operation 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 shortcut operation methods.

[0161] Based on the same inventive concept, and according to the shortcut operation 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 shortcut operation methods in the above embodiments.

[0162] 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)).

[0163] 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.

[0164] 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.

[0165] 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 quick operation method, characterized in that, A front-end service device is applied to provide front-end service pages. The front-end service device is communicatively connected to a task management device, which includes a kernel module for quantum computing task scheduling and management. The method includes: When a user triggers a first shortcut operation on the front-end service page, if the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation, the first running parameter is adjusted to the second running parameter. The first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state and lock state corresponding to the kernel module. When the kernel module is under the second operating parameter, delete all quantum computing tasks scheduled and managed by the kernel module. Based on the clearing status of quantum computing tasks in the kernel module, the first feedback information for the first shortcut operation is displayed on the front-end service page.

2. The method according to claim 1, characterized in that, The method further includes: When the first operating parameter matches the second operating parameter, the step of deleting all quantum computing tasks scheduled and managed by the kernel module is executed.

3. The method according to claim 1, characterized in that, After deleting all quantum computing tasks scheduled and managed by the kernel module, the method further includes: Adjust the second operating parameter to the first operating parameter.

4. The method according to claim 1, characterized in that, The task management device also includes a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. The method further includes: When a user triggers the second shortcut operation on the front-end service page, the locking state of the kernel module is adjusted to the kernel locked state, and the thread state of all threads corresponding to the driver module at the current moment is obtained. The second shortcut operation is used to restart the driver module. When the thread state corresponding to each thread is idle, the driver module is restarted through the monitoring module. Based on the restart status of the driver module, a second feedback message for the second shortcut operation is displayed on the front-end service page.

5. The method according to claim 4, characterized in that, The method further includes: When the thread state corresponding to any thread is not idle, a third feedback message for the second shortcut operation is displayed on the front-end service page. The third feedback message is used to indicate that the driver module cannot be restarted during the execution of the quantum computing task.

6. The method according to claim 1, characterized in that, The method further includes: When a user triggers a third shortcut operation on the front-end service page, the third running parameter of the kernel module at the current moment is adjusted to the fourth running parameter corresponding to the third shortcut operation. The third shortcut operation is used to adjust the running mode of the kernel module at the current moment to the target running mode. Based on the switching of the kernel module's running mode, a fourth feedback message for the third shortcut operation is displayed on the front-end service page.

7. The method according to claim 6, characterized in that, The step of adjusting the third running parameter of the kernel module at the current moment to the fourth running parameter corresponding to the third shortcut operation includes: If the target operating mode is an experimental mode that indicates the normal execution of the quantum computing task, then the kernel state, operating mode and locked state in the third operating parameters corresponding to the kernel module at the current moment are sequentially adjusted to the operating state, the experimental mode and the kernel unlocked state. If the target operating mode is an instrument mode that indicates support for running instrument commands and hardware layer tasks, then the lock state, kernel state, and operating mode in the third operating parameters corresponding to the kernel module at the current moment will be sequentially adjusted to the kernel lock state, operating state, and instrument mode.

8. The method according to claim 1, characterized in that, The step of adjusting the first operating parameter to the second operating parameter if the first operating parameter of the kernel module at the current moment does not match the second operating parameter corresponding to the first shortcut operation includes: When the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation, a first operation instruction for the first shortcut operation is sent to the task management device, so that when the kernel module in the task management device receives the first operation instruction, it sequentially adjusts the current running parameters including the lock state, kernel state and running mode to the kernel lock state, initial state and setting mode to obtain the second running parameter. The setting mode is used to configure the parameters of the kernel module.

9. The method according to claim 1, characterized in that, The step of deleting all quantum computing tasks scheduled and managed by the kernel module when the kernel module is under the second operating parameter includes: When the kernel module is under the second operating parameter, it sends a task clearing instruction to the task management device, so that when the kernel module in the task management device receives the task clearing instruction, it deletes all quantum computing tasks in the task queue and sends feedback information indicating the clearing status of quantum computing tasks to the front-end service device.

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 task management device includes a kernel module for quantum computing task scheduling and management. The front-end service device includes: The first adjustment unit is used to adjust the first running parameter to the second running parameter when the user triggers the first shortcut operation on the front-end service page, if the first running parameter of the kernel module at the current moment does not match the second running parameter corresponding to the first shortcut operation. The first shortcut operation is used to clear all quantum computing tasks scheduled and managed in the kernel module. The running parameters of the kernel module include the running mode, kernel state and lock state corresponding to the kernel module. The deletion unit is used to delete all quantum computing tasks scheduled and managed by the kernel module when the kernel module is under the second running parameter. The first display unit is used to display first feedback information for the first quick operation on the front-end service page based on the clearing status of quantum computing tasks in the kernel module.

Images