A device initialization method, a front-end service device and a storage medium

Abstract

Embodiments of the present application provide a device initialization method, a front-end service device and a storage medium. The scheme is as follows: a first configuration parameter is obtained, and the first configuration parameter is stored in a preset buffer, so that when a kernel module switches to a target running state, the driving module is configured with parameters according to the first configuration parameter; according to a data synchronization operation triggered by a user, chip structure data corresponding to a target quantum chip is synchronized to the kernel module, so that the kernel module detects the quantum chip based on the chip structure data during quantum computing task execution; according to a second configuration parameter set by the user for the monitoring module, a first configuration instruction carrying the second configuration parameter is sent to a task management device, so that after receiving the first configuration instruction, the monitoring module performs function configuration according to the second configuration parameter. Through the technical scheme provided by the embodiments of the present application, the initialization of the device management module is realized, which provides guarantee for the normal execution of the later quantum computing task.

Description

Technical Field

[0001] This application relates to the field of quantum computing technology, and in particular to a device initialization method, a front-end service device, and a storage medium. 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 device initialization method, a front-end service device, and a storage medium to initialize the device management module and ensure the normal execution of subsequent quantum computing tasks. The specific technical solution is as follows:

[0005] This application provides a device initialization method applied to a front-end service device. The front-end service device is communicatively connected to a task management device. The task management device includes a kernel module for quantum computing task scheduling and management, a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. The method includes:

[0006] The system obtains the first configuration parameters set by the user for the driver module and stores the first configuration parameters in a preset cache, so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache. The target running state indicates that the quantum computing task can be executed.

[0007] Based on the data synchronization operation triggered by the user for the target quantum chip, the chip structure data corresponding to the target quantum chip is synchronized to the kernel module, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of quantum computing tasks.

[0008] Based on the second configuration parameters set by the user for the monitoring module, a first configuration instruction carrying the second configuration parameters is sent to the task management device, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

[0009] This application embodiment also provides a front-end service device, which is communicatively connected to a task management device. The task management device includes a kernel module for quantum computing task scheduling and management, a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. The front-end service device includes:

[0010] An acquisition unit is used to acquire the first configuration parameters set by the user for the driver module and store the first configuration parameters in a preset cache, so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache, and the target running state indicates that it can perform quantum computing tasks.

[0011] The synchronization unit is used to synchronize the chip structure data corresponding to the target quantum chip to the kernel module according to the data synchronization operation triggered by the user for the target quantum chip, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of the quantum computing task;

[0012] The first sending unit is configured to send a first configuration instruction carrying the second configuration parameters to the task management device according to the second configuration parameters set by the user for the monitoring module, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

[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 device initialization 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 device initialization 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 execute any of the device initialization methods described above.

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

[0019] The technical solution provided in this application, for the driver module in the task management device, allows the first configuration parameters to be stored in a preset cache after obtaining them. This enables the kernel module in the task management device to retrieve the first configuration parameters from the preset cache for parameter configuration when switching to the target running state, thereby initializing the driver module in the task management device. For the kernel module, the chip structure data corresponding to the target quantum chip can be synchronized to the kernel module, allowing the kernel module to perform quantum chip detection based on the chip structure data during quantum computing task execution, thus initializing the chip structure data in the kernel module. For the monitoring module in the task management device, a first configuration command carrying the second configuration parameters can be sent to the task management device after the user sets the second configuration parameters. This allows the monitoring module to perform functional configuration according to the second configuration parameters in the first configuration command, thus initializing the monitoring module's functions. This achieves the initialization of the device management module, ensuring the normal execution of subsequent quantum computing tasks.

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

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

[0022] Figure 1 This is a schematic diagram of a first flowchart of a device initialization method provided in an embodiment of this application;

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

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

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

[0026] Figure 3-a A partial schematic diagram of the page displayed when setting the first configuration parameters provided in the embodiments of this application;

[0027] Figure 3-b for Figure 3-a A partial schematic diagram of the front-end service page shown;

[0028] Figure 4 A schematic diagram of a front-end service page during chip structure data synchronization provided in an embodiment of this application;

[0029] Figure 5 This is a second flowchart illustrating the device initialization method provided in the embodiments of this application;

[0030] Figure 6-a A schematic diagram of a front-end service page for setting water level configuration parameters as provided in an embodiment of this application;

[0031] Figure 6-b A schematic diagram of the front-end service page when setting alarm configuration parameters according to an embodiment of this application;

[0032] Figure 6-c A schematic diagram of a front-end service page when setting runtime configuration parameters as provided in an embodiment of this application;

[0033] Figure 7 This is a schematic diagram of a third process for the device initialization method provided in the embodiments of this application;

[0034] Figure 8 A schematic diagram of a front-end service page during platform information settings provided in this application embodiment;

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

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

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

[0038] To address the problems in related technologies, embodiments of this application provide a device initialization method. For example... Figure 1 As shown, Figure 1 This is a schematic diagram of a first flowchart of a device initialization method provided in an embodiment of this application. The method is applied to a front-end service device, which is communicatively connected to a task management device. The task management device includes a kernel module for quantum computing task scheduling and management, a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. Figure 1The method shown includes the following steps.

[0039] Step S101: Obtain the first configuration parameters set by the user for the driver module and store the first configuration parameters in the preset cache so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache. The target running state indicates that it can execute quantum computing tasks.

[0040] Step S102: Based on the data synchronization operation triggered by the user for the target quantum chip, the chip structure data corresponding to the target quantum chip is synchronized to the kernel module, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of the quantum computing task.

[0041] Step S103: Based on the second configuration parameters set by the user for the monitoring module, send a first configuration instruction carrying the second configuration parameters to the task management device, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

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

[0043] The aforementioned front-end service device provides a front-end service page to the user. The user can view this front-end service page on the display interface 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.

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

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

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

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

[0048] The MongoDB and Redis mentioned above can be used for data storage during tasks such as configuring device functions, configuring parameters of quantum computing measurement and control systems, and executing quantum computing tasks. The data storage process will not be described in detail here.

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

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

[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-c The 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 described above, for the driver module in the task management device, allows the first configuration parameters to be stored in a preset buffer after obtaining them. This enables the kernel module in the task management device to retrieve the first configuration parameters from the preset buffer for parameter configuration when switching to the target running state, thus initializing the driver module. For the kernel module, the chip structure data corresponding to the target quantum chip can be synchronized to the kernel module, allowing it to perform quantum chip detection based on the chip structure data during quantum computing task execution, thus initializing the chip structure data in the kernel module. For the monitoring module in the task management device, a first configuration command carrying the second configuration parameters can be sent to the task management device after the user sets the second configuration parameters. This allows the monitoring module to configure its functions according to the second configuration parameters in the first configuration command, thus initializing the monitoring module's functions. This initialization of the device management module ensures the normal execution of subsequent quantum computing tasks.

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

[0055] Regarding step S101 above, that is, obtaining the first configuration parameters set by the user for the driver module and storing the first configuration parameters in the preset cache, so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache, and the target running state indicates that it can execute quantum computing tasks.

[0056] In this embodiment, when a user launches the front-end service page through a user device, the front-end service device automatically monitors whether the task management device has completed the initialization of the kernel module, monitoring module, and driver module. If the kernel module, monitoring module, and driver module have not been initialized, the front-end service device can display the corresponding page during initialization in the front-end service page via pop-ups or other means.

[0057] When initializing the driver module in the aforementioned task management device, the user can configure parameters for the driver module on the front-end service page. The front-end service device can obtain the parameters set by the user on the front-end service page as the first configuration parameters, and store the first configuration parameters in a preset cache through the kernel module in the task management device. The preset cache can be Redis, as mentioned above.

[0058] After storing the first configuration parameters in the preset cache, if the kernel module switches to the target running state, that is, to the running state that allows the quantum computing task to be executed, the kernel module can obtain the first configuration parameters from the preset cache to configure the parameters of the driver module and realize the initialization of the driver module.

[0059] In this embodiment, the running state of the kernel module is composed of the running mode and the kernel state corresponding to the kernel module. The running mode may include setting mode, instrument mode, experimental mode, and online mode; the kernel state may include initial state, offline state, abnormal state, and running state.

[0060] The above setting mode can be used to configure kernel modules and driver modules, that is, in setting mode, users can configure parameters of kernel modules and driver modules.

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

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

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

[0064] Regarding the initial state of the kernel modules described above, the driver modules are not configured at all when the kernel modules are in their initial state. After the initialization and configuration of the kernel modules and driver modules are performed, the kernel modules can switch to other kernel states, such as the running states described above.

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

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

[0067] The above operating status indicates that the driver module has completed the corresponding configuration and can support the instrument mode, experimental mode, and online mode. When the kernel module receives the driver module's status detection request, if it determines that the driver module's status is normal, it can switch the kernel status from offline / abnormal status to running status.

[0068] In an optional embodiment, the target operating state indicates the ability to perform quantum computing tasks. For example, the target operating state can be represented as: the kernel state is in operation, and the operating mode is any one of instrument mode, experimental mode, or online mode.

[0069] In this embodiment, the aforementioned driving module is communicatively connected to the quantum computing measurement and control system, which includes multiple chassis.

[0070] In an optional embodiment, the first configuration parameters include: compilation and parsing parameters of the driver module, and system type, chassis parameters, channel parameters, address parameters, and voltage calibration data corresponding to the quantum computing measurement and control system. For details regarding the parameters included in the first configuration parameters, please refer to the description below; they will not be repeated here.

[0071] In an optional embodiment, regarding the first configuration parameter in step S101 above, when the user uploads a full configuration file for the driver module that matches the preset format on the front-end service page, the parameters in the full configuration file are obtained to obtain the first configuration parameter.

[0072] In another optional embodiment, for the first configuration parameter in step S101 above, the first configuration parameter is generated based on the user's setting operation for each configuration parameter corresponding to the driver module triggered on the front-end service page.

[0073] For ease of understanding, combined with Figure 3-a , Figure 3-b Let's take an example to illustrate. Figure 3-a This is a partial schematic diagram of the page displayed when setting the first configuration parameter according to an embodiment of this application. Figure 3-b for Figure 3-a The image shown is a partial schematic of the front-end service page.

[0074] exist Figure 3-a The displayed page includes two pages: page 301 and page 302. Page 301 is the front-end service page provided by the front-end service device, which is the page corresponding to the initialization of Qstream configuration. Page 302 is the display page of the storage location of the full configuration file. Here, Qstream represents the service functions provided by the driver module.

[0075] On page 301, users can upload the full configuration files from page 302, specifically the calibration.conf and driver.conf files in area 304, to page 301. For example, a user can click on area 303, select the address shown on page 302 to display the full configuration files, and upload them to page 301, resulting in the full configuration files shown in area 305. Alternatively, a user can open page 302, drag the full configuration files from area 304 to area 303 to upload the full configuration files, resulting in the full configuration files shown in area 305.

[0076] The above preset format is Figure 3-a The calibration.conf and driver.conf files shown above contain all the configuration parameters required for the driver module to run.

[0077] exist Figure 3-a On the front-end service page shown, users can directly obtain the first configuration parameter by uploading the full configuration file.

[0078] exist Figure 3-bOn the front-end service page shown, users can trigger function options individually, i.e., trigger... Figure 3-b The diagram shows the function options corresponding to the abnormal task reset enable (reset_enable) and the system type (qaio_type) of the quantum computing measurement and control system, as well as the triggering method of the function button, i.e., triggering... Figure 3-b The AC calibration configuration button, QAIO parameter configuration button, and other parameter configuration buttons shown enable the setting operation for each configuration parameter corresponding to the drive module, and realize the setting of the first configuration parameter.

[0079] The above-mentioned abnormal task reset enable function option is used to indicate whether to enable abnormal task reset during the execution of quantum computing tasks. The system type function option is used to switch the corresponding rack version of the quantum computing measurement and control system, such as switching between single rack version and multi rack version.

[0080] During the execution of a quantum computing task, the Arbitrary Waveform Generator (AWG) board in the quantum computing measurement and control system can provide AWG signals to the qubits and couplers participating in the quantum computing task on the target quantum chip through the z-flux channel. To avoid the impact of voltage distortion on the accuracy of the AWG signal, AC calibration can be performed during the execution of the quantum computing task. Accordingly, the relevant parameters for AC calibration are set during the initialization process, namely the voltage calibration parameters in the first configuration parameters mentioned above. Figure 3-b The AC calibration configuration button shown is used to calibrate the voltage transmitted through the z-flux channels in the quantum computing measurement and control system. The voltage calibration parameters can include an integer range of calibration mapping intervals corresponding to each z-flux channel within a preset voltage threshold range, and each integer has a corresponding AWG signal voltage.

[0081] The above Figure 3-b The QAIO parameter configuration button shown is used to set parameters such as chassis parameters, channel parameters, and address parameters for various chassis in the quantum computing measurement and control system. For example, chassis parameters may include: the chassis number used and the component configuration information for each component in each chassis. Each component configuration information includes: chassis name, IP address, port number, device number, device type, and the local oscillator channel used. Channel parameters may include: the number of first channels for each chassis and the number of second channels for each board. Address parameters may include: the address information of the central control module in the quantum computing measurement and control system, the address information for each chassis, and the address information for each DC (DC) channel. Each address information includes at least an IP address and a port number.

[0082] In an optional embodiment, each chassis in the above-described quantum computing measurement and control system may include an AWG board, an ADC board, an ADDA board, a DC board, a transmitter board, a transceiver board, and a local oscillator board. The second number of channels may include: the number of channels on an AWG board, the number of channels on an ADC board, the number of ADDA channel units, the number of channels on a DC board, the number of channels on a transmitter board, the number of channels on a transceiver board, and the number of channels on a local oscillator board. The first number of channels may include: the number of AWG channels, the number of pulse modulation (xy) channels, the number of readout units, and the total number of DC channels.

[0083] The above Figure 3-b The other parameter configuration buttons shown are used to set the compilation and parsing parameters of the driver module. For example, compilation and parsing parameters may include reset mode, valid bits of AWG waveform encoding, maximum amplitude of AWG waveform, adjacent interval time of AWG calibration instructions, AWG bias reset interval, component output enable, component output delay time, number of loops for a single quantum computing task, maximum number of loops for the quantum computing measurement and control system, thread trigger interval, number of parallel quantum computing tasks, size of the parallel buffer pool, parallel threshold, valid bits of waveform encoding, and timeout time.

[0084] In this embodiment of the application, the parameters included in the first configuration parameters are not specifically limited.

[0085] In the above Figure 3-a and Figure 3-b On the page shown, after setting the first configuration parameter, the user can trigger the execution button, such as triggering... Figure 3-a The execution button 306 shown Figure 3-b The execution buttons 307 and 308 shown, and Figure 3-b The execution button (not shown) in the subpage corresponding to each function button shown allows the front-end service device to store the first configuration parameters set by the user in the preset cache.

[0086] In an optional embodiment, when a user triggers the execute button on the aforementioned front-end service page, the front-end service device can send a first configuration parameter to the task management device. Upon receiving the first configuration parameter, the kernel module in the task management device can store it in the aforementioned preset cache.

[0087] Regarding step S102 above, that is, according to the data synchronization operation triggered by the user for the target quantum chip, the chip structure data corresponding to the target quantum chip is synchronized to the kernel module, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of the quantum computing task.

[0088] In the above Figure 3-aand Figure 3-b The front-end service page shown includes a function button (not shown) for proceeding to the next initialization step. This function button can be triggered after the user completes the initial configuration parameter settings on the front-end service page. At this point, the front-end service page will switch to... Figure 3-a The page corresponding to the synchronization chip configuration is shown below, specifically as follows: Figure 4 As shown, Figure 4 This is a schematic diagram of a front-end service page for chip structure data synchronization provided in an embodiment of this application.

[0089] In the above Figure 4 In the front-end service page shown, the user triggers... Figure 4 The synchronization button in the system triggers the data synchronization operation corresponding to the target quantum chip. When the front-end service device detects that the user has triggered the data synchronization operation, it can obtain the chip structure data corresponding to the target quantum chip at the current moment and synchronize the chip structure data to the kernel module in the task management device.

[0090] In an optional embodiment, when synchronizing the aforementioned chip structure data, the front-end service device can acquire the chip structure data of the target quantum chip and send the chip structure data to the task management device. Upon receiving the chip structure data, the kernel module in the task management device can store the chip structure data in the aforementioned preset buffer.

[0091] During the execution of a quantum computing task, when the kernel module performs quantum computing task scheduling and management, it can compare the chip structure information stored in the preset buffer with the chip structure information corresponding to the quantum chip executing the quantum computing task to determine whether the quantum chip executing the quantum computing task is the target quantum chip, thus completing the monitoring of the quantum chip during the execution of the quantum computing task.

[0092] When the front-end service device acquires the chip structure data of the target quantum chip, the data can be uploaded by the user through the front-end service page, or the user can set each parameter in the front-end service page. Here, no specific limitations are made on the chip structure data of the target quantum chip.

[0093] In this embodiment, the chip structure data may include parameters such as the quantum chip name (denoted as Sample), the test platform environment name (denoted as envName), and the shape corresponding to the target quantum chip. It may also include parameters such as channel parameters and position coordinates corresponding to each device on the target quantum chip. Devices on the target quantum chip may include qubits and couplers. Here, no specific limitations are made on the parameters included in the chip structure data.

[0094] Regarding step S103 above, that is, according to the second configuration parameters set by the user for the monitoring module, a first configuration instruction carrying the second configuration parameters is sent to the task management device, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

[0095] After synchronizing the chip structure data, users can trigger configuration operations for the monitoring module's functions on the front-end service page. This involves setting the corresponding configuration parameters for the monitoring module (denoted as the second configuration parameter) on the front-end service page. At this time, the front-end service device can send a configuration command carrying the second configuration parameters (denoted as the first configuration command) to the task management device based on the second configuration parameters.

[0096] Upon receiving the first configuration instruction, the kernel module in the task management device can forward it to the monitoring module. The monitoring module then configures the functions according to the second configuration parameters in the received first configuration instruction.

[0097] In this embodiment of the application, the second configuration parameter may include: water level configuration parameters, alarm configuration parameters, and operation configuration parameters corresponding to the monitoring module.

[0098] In an optional embodiment, according to the above... Figure 1 In addition to the method shown, this application also provides a device initialization method. For example... Figure 5 As shown, Figure 5 This is a schematic diagram of a second flowchart of a device initialization method provided in an embodiment of this application. Figure 5 The method shown above, step S103, can be further refined into the following steps, namely step S1031-step S1033.

[0099] Step S1031: Based on the first configuration operation triggered by the user on the front-end service page for the water level configuration parameters, generate a second configuration instruction including the water level configuration parameters, and send the second configuration instruction to the task management device.

[0100] In the above Figure 4 In the front-end service page shown, after the user triggers the sync button, they can trigger... Figure 4 The "Next" button shown will switch the current page to... Figure 4 The page corresponding to the OPS water level configuration is shown below, specifically as follows: Figure 6-a As shown, Figure 6-a This is a schematic diagram of a front-end service page for setting water level configuration parameters according to an embodiment of this application. OPS refers to the aforementioned monitoring module.

[0101] In one alternative embodiment, such as Figure 6-aThe front-end service page shown above includes the following water level configuration parameters: the first function option, and the corresponding normal water level level (i.e., low_wm), high water level level (i.e., alarm_wm_rate), effective time for abnormal triggering (i.e., effective_time), interval for abnormal triggering (i.e., trigger_interval), interval for monitoring and collection (i.e., collect_interval), type of abnormal alarm triggering (i.e., alarm_type), number of repeated abnormal alarm triggers (i.e., alarm_repeats), and heartbeat interval configuration (i.e., heartbeat_time).

[0102] The first function option mentioned above is used to indicate the various hardware resources associated with the task management device. (As described above...) Figure 6-a As shown, the first function option can include system CPU, system memory, system cache, system disk, Mongo disk, Mongo memory, Redis memory, and Prometheus disk. Users can select one or more options from the first function option to set the parameters for each selected option and obtain the water level configuration parameters.

[0103] In the above Figure 6-a In the front-end service page shown, after the user completes the water level configuration parameter settings for any of the first function options, it can trigger... Figure 6-a The execute button shown triggers the first configuration operation. At this time, the front-end service device can generate a configuration instruction (denoted as the second configuration instruction) that matches the first configuration operation. That is, the second configuration instruction carries the water level configuration parameters configured by the user.

[0104] The front-end service device can send the aforementioned second configuration command to the device management device. Upon receiving the second configuration command, the kernel module in the task management device can forward it to the monitoring module. Upon receiving the second configuration command, the monitoring module loads the water level configuration parameters carried in the command and implements the corresponding functional configuration.

[0105] In this embodiment, since the first functional option includes multiple options, each option has a corresponding set of water level configuration parameters. Accordingly, when the first configuration operation is triggered, the user can trigger a configuration operation once for each option. At this time, the front-end service device sends the corresponding second configuration command to the task management device. Here, the number of times the user triggers the first configuration operation on the front-end service page is not specifically limited.

[0106] Step S1032: Based on the second configuration operation triggered by the user on the front-end service page for alarm configuration parameters, generate a third configuration instruction including alarm configuration parameters and send the third configuration instruction to the task management device.

[0107] In the above Figure 6-a In the front-end service page shown, after the user completes the setting of the water level configuration parameters, they can trigger... Figure 6-a The "Next" button shown will switch the current front-end service page to... Figure 6-a The page corresponding to the OPS alarm configuration is set up in the middle, as shown in the example below. Figure 6-b As shown, Figure 6-b This is a schematic diagram of the front-end service page when setting alarm configuration parameters according to an embodiment of this application.

[0108] In one alternative embodiment, such as Figure 6-b The front-end service page shown above includes the following alarm configuration parameters: platform identifier, task alarm level, service alarm level, hardware alarm level, and alarm service connection heartbeat interval (alarm_hb_intv).

[0109] In this embodiment, the task alarm level, service alarm level, and hardware alarm level may include various alarm levels, such as: tip alarm, debug, normal alarm, info, warning, important, and crash. Here, no specific limitation is made on the alarm levels included in the task alarm level, service alarm level, and hardware alarm level.

[0110] The user in the above Figure 6-b After setting the alarm configuration parameters in the front-end service page shown, you can trigger it. Figure 6-b The "Execute" button triggers a setting operation for the alarm configuration parameters (referred to as the second configuration operation). At this time, the front-end service device can generate a configuration instruction that matches the second configuration operation (referred to as the third configuration instruction), which carries the alarm configuration parameters configured by the user.

[0111] The front-end service device can send the aforementioned third configuration command to the task management device. The kernel module in the task management device forwards the received third configuration command to the monitoring module. After receiving the third configuration command, the monitoring module loads the alarm configuration parameters carried by the third configuration command and implements the functional configuration corresponding to the alarm configuration parameters.

[0112] Step S1033: Based on the third configuration operation triggered by the user on the front-end service page for the running configuration parameters, generate a fourth configuration instruction including the running configuration parameters, and send the fourth configuration instruction to the task management device.

[0113] In the above Figure 6-b In the front-end service page shown, users can trigger alarms after completing the alarm configuration parameter settings. Figure 6-b The "Next" button shown will switch the current front-end service page to... Figure 6-b The page for configuring OPS operation is set up, as shown below. Figure 6-c As shown, Figure 6-c This is a schematic diagram of the front-end service page when setting the runtime configuration parameters provided in the embodiments of this application.

[0114] In one alternative embodiment, such as Figure 6-c The front-end service page shown above includes the following configuration parameters: a second function option (enable_collect) and a third function option (enable_alarm). The second function option indicates whether the monitoring module enables monitoring data collection, and the third function option indicates whether the monitoring module enables alarms.

[0115] In addition, the above-mentioned operation configuration parameters may also include a timer ( Figure 6-c (Not shown). This timing period is used to indicate the time interval at which the corresponding timing is activated when the second and / or third function options are enabled.

[0116] Users Figure 6-c After completing the configuration parameters settings in the front-end service page shown, you can trigger... Figure 6-c The execute button shown triggers a configuration operation for the runtime configuration parameters (referred to as the third configuration operation). At this time, the front-end service device can generate a configuration instruction that matches the third configuration operation (referred to as the fourth configuration instruction), which carries the runtime configuration parameters set by the user.

[0117] The front-end service device can send the aforementioned fourth configuration command to the task management device. The kernel module in the task management device forwards the received fourth configuration command to the monitoring module. After receiving the fourth configuration command, the monitoring module loads the runtime configuration parameters carried in the fourth configuration command and implements the function configuration corresponding to the runtime configuration parameters.

[0118] Through the above steps S1031-S1033, the front-end service device can send the configured parameters to the task management device in the form of configuration instructions based on the parameter configuration operation triggered by the user for the monitoring module in the front-end service page. This allows the monitoring module in the task management device to directly load the configuration parameters to achieve functional configuration and complete its own initialization.

[0119] In the above Figure 5 In the illustrated embodiment, steps S1031-S1033 are executed sequentially. In practical applications, the execution order of steps S1031-S1033 can be adjusted. Here, the execution order of steps S1031-S1033 is not specifically limited.

[0120] In the above embodiments, the example only illustrates the situation where the kernel module, monitoring module, and driver module have not been initialized. In addition, during the initialization process, factors such as user operations or network environment may cause some modules in the kernel module, monitoring module, and driver module to fail to be initialized. In this case, the front-end service device can display the corresponding module initialization page in the front-end service page via pop-ups or other means to facilitate user initialization. The specific process can be referred to the above description and will not be repeated here.

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

[0122] Step S701: Based on the platform setting operation triggered by the user for the target quantum chip, send the platform information corresponding to the platform setting operation to the task management device, so that the task management device can establish a correspondence between the platform information and the target platform corresponding to the target quantum chip. The platform information includes the name of the quantum chip corresponding to the target platform and the name of the test platform environment.

[0123] In this embodiment, for different quantum chips, each quantum chip has a corresponding operating platform and chip structure data. Each operating platform has corresponding platform information, which includes the quantum chip name and the test platform environment name. When a quantum chip corresponds to a certain operating platform, the chip structure data corresponding to that quantum chip includes the same quantum chip name and test platform environment name as the platform information corresponding to that operating platform.

[0124] In an optional embodiment, when a user opens the aforementioned front-end service page for the first time, the following can be displayed: Figure 8 The front-end service page shown is... Figure 8 This is a schematic diagram of a front-end service page during platform information settings as provided in the embodiments of this application. When the front-end service page... Figure 8 As shown in the default platform information area, when both Sample and EnvName are not yet set, users can... Figure 8 The modified default platform area, as shown, sets the corresponding Sample and EnvName according to the target quantum chip mentioned above, and triggers... Figure 8 The execute button shown triggers the platform settings operation. At this time, the front-end service device can obtain the platform information corresponding to the platform settings operation triggered by the user, and send the platform information to the task management device.

[0125] When the Application Programming Interface (API) in the task management device receives platform information from the front-end service device, it can generate an identifier corresponding to that platform information and bind that identifier to the target quantum chip. The API can store the binding relationship between the identifier and the target quantum chip in a preset memory, such as Mongo mentioned above, thus establishing the correspondence between platform information and the target platform corresponding to the target quantum chip.

[0126] In an optional embodiment, to ensure the accuracy and security of the platform information, the setting and modification of the aforementioned platform information can only be performed by the administrator. For example, in the above... Figure 8 When a user confirms that `ample` and `EnvName` are not yet set, a prompt message such as "Please contact the administrator to set the default platform" will be displayed on the front-end service page. At this time, the user can contact the administrator based on this prompt message, allowing the administrator to configure the platform information according to their needs. Correspondingly, once the administrator has completed the configuration, the user will directly display the above message when opening the front-end service page. Figure 3-a The front-end service page shown is... Figure 8 Initialize the page corresponding to Qstream.

[0127] Through the above step S701, the user can trigger the platform setting operation on the front-end service page, thereby establishing the correspondence between the platform information and the target platform corresponding to the target quantum chip, providing a guarantee for the user to perform quantum computing tasks using the target quantum chip in the future.

[0128] In an optional embodiment, when the administrator has the authority to set and modify the platform information, if the administrator has already pre-set the platform information corresponding to the default platform, the user may not need to display the above-mentioned information on the first launch of the front-end service page. Figure 8The front-end service page shown in the platform information settings means that step S701 is not executed, and step S702 is executed directly.

[0129] Step S702: Obtain the first configuration parameters set by the user for the driver module and store the first configuration parameters in the preset cache so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache. The target running state indicates that it can execute quantum computing tasks.

[0130] Step S703: Based on the data synchronization operation triggered by the user for the target quantum chip, synchronize the chip structure data corresponding to the target quantum chip to the kernel module, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of the quantum computing task.

[0131] Step S704: Based on the second configuration parameters set by the user for the monitoring module, a first configuration instruction carrying the second configuration parameters is sent to the task management device, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

[0132] Steps S702-S704 are the same as steps S101-S103.

[0133] In the above embodiments, taking the execution of step S701 before step S702 as an example, considering that the execution of step S701 only affects steps S703 and S704, that is, the execution of step S701 does not affect the execution of step S702. Here, the execution order of the above steps S701 and S702 is not specifically limited.

[0134] Based on the same inventive concept, and according to the device initialization method provided in the above embodiments of this application, this application also provides a front-end service device. For example... Figure 9 As shown, Figure 9 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 is communicatively connected to a task management device, which includes a kernel module for quantum computing task scheduling and management, a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. Figure 9 The front-end service equipment shown may include:

[0135] The acquisition unit 901 is used to acquire the first configuration parameters set by the user for the driver module and store the first configuration parameters in a preset cache, so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache. The target running state indicates that it can perform quantum computing tasks.

[0136] The synchronization unit 902 is used to synchronize the chip structure data corresponding to the target quantum chip to the kernel module according to the data synchronization operation triggered by the user for the target quantum chip, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of the quantum computing task;

[0137] The first sending unit 903 is used to send a first configuration instruction carrying the second configuration parameters to the task management device according to the second configuration parameters set by the user for the monitoring module, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

[0138] Optionally, the aforementioned driving module is communicatively connected to the quantum computing measurement and control system, which includes multiple chassis.

[0139] The first configuration parameter mentioned above includes: the compilation and parsing parameters of the driver module, as well as the system type, chassis parameters, channel parameters, address parameters, and voltage calibration data corresponding to the quantum computing measurement and control system.

[0140] Optionally, the aforementioned front-end service device provides a front-end service page;

[0141] The aforementioned acquisition unit 901 can be used to obtain the parameters in the full configuration file when a user uploads a full configuration file for the driver module that matches the preset format on the front-end service page, and obtain the first configuration parameter.

[0142] or,

[0143] The first configuration parameter is generated based on the user's setting operation for each configuration parameter of the driver module triggered on the front-end service page.

[0144] Optionally, the second configuration parameters mentioned above include: water level configuration parameters, alarm configuration parameters, and operation configuration parameters corresponding to the monitoring module.

[0145] Optionally, the aforementioned front-end service device provides a front-end service page;

[0146] The first sending unit 903 mentioned above can be used to generate a second configuration instruction including the water level configuration parameters based on the first configuration operation triggered by the user on the front-end service page for the water level configuration parameters, and send the second configuration instruction to the task management device.

[0147] Based on the second configuration operation triggered by the user on the front-end service page for alarm configuration parameters, a third configuration instruction including alarm configuration parameters is generated and sent to the task management device;

[0148] Based on the third configuration operation triggered by the user on the front-end service page for the running configuration parameters, a fourth configuration instruction including the running configuration parameters is generated and sent to the task management device.

[0149] Optionally, the above water level configuration parameters include: a first function option, and the normal water level level, high water level level, abnormal trigger effective time, abnormal trigger interval, monitoring and acquisition interval, abnormal alarm trigger category, repeated abnormal alarm trigger count and heartbeat interval configuration corresponding to the first function option. The first function option is used to indicate various hardware resources associated with the task management device.

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

[0151] The above-mentioned operational configuration parameters include: a second function option, a third function option, and a timer. The second function option indicates whether the monitoring module enables monitoring and data acquisition, and the third function option indicates whether the monitoring module enables alarms.

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

[0153] The second sending unit is used to send platform information corresponding to the platform setting operation triggered by the user for the target quantum chip to the task management device before synchronizing the chip structure data corresponding to the target quantum chip to the kernel module according to the data synchronization operation triggered by the user for the target quantum chip. This is so that the task management device can establish a correspondence between the platform information and the target platform corresponding to the target quantum chip. The platform information includes the name of the quantum chip corresponding to the target platform and the name of the test platform environment.

[0154] The front-end service device provided in this application embodiment allows the driver module in the task management device to store the first configuration parameters in a preset cache after obtaining them. This enables the kernel module in the task management device to retrieve the first configuration parameters from the preset cache for parameter configuration when switching to the target running state, thus initializing the driver module in the task management device. For the kernel module, the chip structure data corresponding to the target quantum chip can be synchronized to the kernel module, allowing it to perform quantum chip detection based on the chip structure data during quantum computing task execution, thus initializing the chip structure data in the kernel module. For the monitoring module in the task management device, a first configuration command carrying the second configuration parameters can be sent to the task management device after the user sets the second configuration parameters. This allows the monitoring module to configure its functions according to the second configuration parameters in the first configuration command, thus initializing the monitoring module's functions. This initialization of the device management module ensures the normal execution of subsequent quantum computing tasks.

[0155] Based on the same inventive concept, and according to the device initialization method provided in the above embodiments of this application, this application also provides a front-end service device, such as... Figure 10 As shown, it includes a processor 1001, a communication interface 1002, a memory 1003, and a communication bus 1004, wherein the processor 1001, the communication interface 1002, and the memory 1003 communicate with each other through the communication bus 1004.

[0156] Memory 1003 is used to store computer programs;

[0157] When the processor 1001 executes the program stored in the memory 1003, it implements any of the device initialization method steps described above.

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

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

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

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

[0162] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores a computer program that, when executed by a processor, implements the steps of any of the above-described device initialization methods.

[0163] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the device initialization methods described above.

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

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

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

[0167] 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 device initialization method, characterized in that, The method is applied to a front-end service device, which is communicatively connected to a task management device. The task management device includes a kernel module for quantum computing task scheduling and management, a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. The system obtains the first configuration parameters set by the user for the driver module and stores the first configuration parameters in a preset cache, so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache. The target running state indicates that the quantum computing task can be executed. Based on the data synchronization operation triggered by the user for the target quantum chip, the chip structure data corresponding to the target quantum chip is synchronized to the kernel module, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of quantum computing tasks. Based on the second configuration parameters set by the user for the monitoring module, a first configuration instruction carrying the second configuration parameters is sent to the task management device, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

2. The method according to claim 1, characterized in that, The drive module is communicatively connected to the quantum computing measurement and control system, which includes multiple chassis. The first configuration parameters include: the compilation and parsing parameters of the driver module, and the system type, chassis parameters, channel parameters, address parameters, and voltage calibration data corresponding to the quantum computing measurement and control system.

3. The method according to claim 1 or 2, characterized in that, The front-end service device provides a front-end service page; The step of obtaining the first configuration parameters set by the user for the driver module includes: When a user uploads a full configuration file for the driver module that matches a preset format on the front-end service page, the parameters in the full configuration file are obtained to obtain the first configuration parameter. or, Based on the user's setting operation for each configuration parameter of the driver module triggered on the front-end service page, the first configuration parameter is generated.

4. The method according to claim 1, characterized in that, The second configuration parameters include: water level configuration parameters, alarm configuration parameters, and operation configuration parameters corresponding to the monitoring module.

5. The method according to claim 4, characterized in that, The front-end service device provides a front-end service page; The step of sending a first configuration command carrying the second configuration parameters to the task management device according to the second configuration parameters set by the user for the monitoring module includes: Based on the first configuration operation triggered by the user on the front-end service page for the water level configuration parameters, a second configuration instruction including the water level configuration parameters is generated and sent to the task management device; Based on the second configuration operation triggered by the user on the front-end service page for the alarm configuration parameters, a third configuration instruction including the alarm configuration parameters is generated and sent to the task management device; Based on the third configuration operation triggered by the user on the front-end service page for the running configuration parameters, a fourth configuration instruction including the running configuration parameters is generated and sent to the task management device.

6. The method according to claim 4 or 5, characterized in that, The water level configuration parameters include: a first function option, and the normal water level level, high water level level, abnormal trigger effective time, abnormal trigger interval, monitoring and acquisition interval, abnormal alarm trigger category, repeated abnormal alarm trigger count and heartbeat interval configuration corresponding to the first function option. The first function option is used to indicate various hardware resources associated with the task management device. 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 second function option, a third function option, and a timer. The second function option indicates whether the monitoring module enables monitoring and data acquisition, and the third function option indicates whether the monitoring module enables alarms.

7. The method according to claim 1, characterized in that, Before synchronizing the chip structure data corresponding to the target quantum chip to the kernel module based on the data synchronization operation triggered by the user for the target quantum chip, the method further includes: Based on the platform setting operation triggered by the user for the target quantum chip, the platform information corresponding to the platform setting operation is sent to the task management device, so that the task management device can establish a correspondence between the platform information and the target platform corresponding to the target quantum chip. The platform information includes the name of the quantum chip and the name of the test platform environment corresponding to the target platform.

8. A front-end service device, characterized in that, The front-end service device is communicatively connected to the task management device. The task management device includes a kernel module for quantum computing task scheduling and management, a monitoring module for monitoring and management, and a driver module for compiling and distributing quantum computing tasks. The front-end service device includes: An acquisition unit is used to acquire the first configuration parameters set by the user for the driver module and store the first configuration parameters in a preset cache, so that when the kernel module switches to the target running state, it configures the parameters of the driver module according to the first configuration parameters in the preset cache, and the target running state indicates that it can perform quantum computing tasks. The synchronization unit is used to synchronize the chip structure data corresponding to the target quantum chip to the kernel module according to the data synchronization operation triggered by the user for the target quantum chip, so that the kernel module can perform quantum chip detection based on the chip structure data during the execution of the quantum computing task; The first sending unit is configured to send a first configuration instruction carrying the second configuration parameters to the task management device according to the second configuration parameters set by the user for the monitoring module, so that the monitoring module can perform function configuration according to the second configuration parameters after receiving the first configuration instruction.

9. A front-end service device, characterized in that, It includes 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; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the steps of the method described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1-7.

Images