Quantum computing experiment remote control system and device, quantum experiment system

Abstract

This invention discloses a remote control system and device for quantum computing experiments, and a quantum experimental system. The user application layer enables interaction with the user; the experiment management layer manages the quantum experiments, including: loading experimental code templates and blocks; instantiating parameter classes and experiment classes from the templates to obtain configured experimental parameters; the experiment implementation layer generates experimental plans based on the experimental parameters; and obtains experimental execution data based on executed instructions and experimental parameters; the experiment abstraction layer provides the basic model and data specifications for the experiments; the quantum operation abstraction layer provides basic quantum experimental operations; the connection management layer establishes a communication connection with the quantum experimental device; and data packet transmission and reception are implemented. This system, through its multi-layered architecture, enables unified management and control of quantum experiments, is applicable to various types of quantum experiments, requires no separate development, can easily generate various types of experimental plans, is easily expandable, and has strong applicability.

Description

Technical Field

[0001] This invention relates to the field of quantum computing technology, and in particular to a remote control system and device for quantum computing experiments, and a quantum experimental system. Background Technology

[0002] With the rapid development of quantum computing technology, the demand for quantum computing experiments using nuclear magnetic resonance quantum computers as experimental devices is increasing. To successfully complete these experiments, remote control equipment is typically required to manage the entire process. Currently, the remote control software used in quantum computing experiments is generally developed specifically for the chosen experiment. However, with the diversification of quantum experiment types and the increasing complexity of experiment lifecycle management, existing remote control software is no longer sufficient to meet the demands of quantum experiments. Its drawbacks are mainly manifested in the following aspects:

[0003] 1) High development and maintenance costs.

[0004] Because each type of experiment requires a separate control program, the code is highly repetitive, resulting in a bloated system and high maintenance costs.

[0005] 2) Difficult to manage.

[0006] On the one hand, due to the diversity of quantum experiment types, different quantum experiments (such as Rabi oscillation, quantum decoherence measurement, quantum gate operation, etc.) have different parameter settings, execution procedures and result formats, and existing remote control software lacks a unified management framework.

[0007] On the other hand, the lifecycle of quantum computing experiments is complex: the entire lifecycle of an experiment, from creation, parameter configuration, submission for execution, state monitoring to result acquisition, involves multiple state transitions and asynchronous message processing. Existing technologies lack a systematic management mechanism, making it difficult to plan and manage quantum computing in a unified manner.

[0008] 3) Poor applicability.

[0009] Existing quantum experimental systems often only provide a single-level operation interface (such as pure pulse operation or pure circuit operation), lacking multi-level abstraction from pulse-level operation to quantum circuit-level design. Users need to directly handle the underlying hardware parameters, which is costly to learn, error-prone, and cannot meet the needs of different application scenarios and different levels of abstraction.

[0010] 4) Poor scalability.

[0011] Since remote control software is specifically developed for certain types of experiments, adding new types of experiments requires modifying the core code. It cannot flexibly support custom experiment types, violates the open / closed principle, and leads to difficult system maintenance and poor scalability.

[0012] 5) Existing remote control systems lack a unified communication protocol and message processing mechanism, and cannot flexibly handle various types of interactive messages.

[0013] 6) The experimental results are poorly visible.

[0014] Different experiments produce data in various formats (such as time-domain data, frequency-domain data, quantum state tomography results, etc.). Existing remote control systems lack unified experimental result processing standards and cannot achieve unified visualization, resulting in a poor user experience for experimental results. Summary of the Invention

[0015] In view of the above problems, the present invention is proposed to provide a quantum computing experiment remote control system and device, and a quantum experiment system, which overcomes or at least partially solves the above problems.

[0016] This invention provides a remote control system for quantum computing experiments, comprising:

[0017] The user application layer is used to implement interaction with users, including: obtaining connection-related parameters and experiment-related parameters provided by users, and displaying experiment results to users;

[0018] The experiment management layer is used to manage quantum experiments, including: loading the corresponding experiment code template based on the experiment type provided by the user application layer; loading the code blocks related to the experiment type into the experiment code template; instantiating the parameter class and experiment class in the template based on the experiment base class and parameter base class provided by the experiment abstraction layer, generating an experiment instance and a parameter instance as an interface for experiment parameter configuration, and providing them to the user application layer; and obtaining the experiment parameters configured by the user based on the experiment instance and parameter instance.

[0019] The experiment implementation layer is used to generate an experiment plan based on the experimental parameters provided by the experiment management layer and the basic quantum experiment operations provided by the experiment abstraction layer; and to extract the configured experimental parameters from the experiment plan based on the execution instructions provided by the user application layer, generate a structured parameter dictionary, add connection parameters to the parameter dictionary, and obtain the experiment execution data.

[0020] The experimental abstraction layer provides the basic model and data specifications for quantum computing experiments, including experimental base classes, parameter base classes, result base classes, and state machine definitions.

[0021] A quantum operation abstraction layer is used to provide reusable basic operations for quantum experiments;

[0022] The connection management layer is used to establish a communication connection with the quantum experimental device based on the connection parameters provided by the user application layer; and to send experimental execution data packets in a specified format to the quantum experimental device, and to receive experimental result data packets from the quantum experimental device.

[0023] In some optional embodiments, it also includes:

[0024] The message distribution layer is used to distribute and process different types of messages, including sending experimental execution data to the communication protocol layer and providing experimental result data to the user application layer via the experimental implementation layer.

[0025] The communication protocol layer is used to realize communication between remote control devices and quantum experimental devices. It includes message serialization and deserialization, packet header encapsulation and parsing, data packet splitting and reassembly, data verification, and maintaining heartbeat keep-alive messages. It includes: encapsulating experimental execution data into experimental execution data packets of a specified format; parsing experimental result data packets and providing experimental result data to the message distribution layer.

[0026] In some optional embodiments, the user application layer includes:

[0027] The parameter configuration module is used to obtain connection-related parameters and experiment-related parameters provided by the user.

[0028] The experimental results data display module is used to present experimental results to users.

[0029] In some optional embodiments, the experimental management layer includes:

[0030] The experiment registration / deregistration module is used to obtain the experiment type specified by the user through the registration function; according to the experiment type, search the experiment code template library, obtain the corresponding experiment code template and load it; and execute the experiment deregistration operation based on the user application layer instructions to release the communication connection with the quantum experiment device.

[0031] The experiment type mapping module is used to look up the experiment code information mapping table according to the experiment type, determine the code block involved in the experiment type, and obtain the parsing path of the code block, the class object code and parameter object code involved in the code block;

[0032] The dynamic class loading module is used to dynamically load code blocks, along with the related class object code and parameter object code, into the experimental code template based on the parsed path; based on the experimental base class and parameter base class provided by the experimental abstraction layer, it instantiates the parameter class and experimental class in the template, generates experimental instances and parameter instances as experimental parameter configuration interfaces, and provides them to the user application layer; and it obtains the experimental parameters configured by the user based on the experimental instances and parameter instances.

[0033] The message dispatcher registration module is used to register, bind, and save message processors based on the generated experimental and parameter instances.

[0034] In some optional embodiments, the experimental implementation layer is used to implement various types of quantum experiments;

[0035] During the experiment registration phase: Based on the basic model and data specifications provided by the experiment abstraction layer, the experiment management layer works together to complete the instantiation of experiment classes and parameter classes;

[0036] In the experimental scheme generation phase: based on the experimental parameters provided by the experimental management layer, and using the basic quantum experimental operations provided by the experimental abstraction layer, experimental logic verification and derivation are performed to generate the experimental scheme.

[0037] In the experimental scheme implementation phase: Based on the execution instructions provided by the user application layer, the configured experimental parameters are extracted from the experimental scheme, the experimental parameters are mapped to the operation call sequence to obtain a structured parameter dictionary, and connection parameters are added to the parameter dictionary to obtain experimental execution data;

[0038] During the experimental results presentation phase: Based on the experimental information and results specifications provided by the experimental abstraction layer, the experimental results data returned by the quantum experimental equipment are processed into structured visual result objects and provided to the user application layer.

[0039] In some optional embodiments, the experimental abstraction layer is specifically used for:

[0040] During the experiment registration phase: the experiment type and its parameters / results / state machines are provided to the experiment implementation layer, and the registrable experiment descriptors are output. The experiment descriptors include type name, version, parameter mode, result mode, and state machine definition.

[0041] In the experimental scheme generation phase: Based on the parameter base class rules, the number of user input information is verified, and standardized parameter objects are generated and provided to the experimental implementation layer and experimental management layer for parameter instantiation.

[0042] In the experimental scheme implementation phase: based on the real-time status messages returned by the quantum experimental device, the quantum experimental state is recorded and provided to the user application layer for display through the experimental implementation layer;

[0043] During the experimental results presentation phase: provide experimental information and result specifications to the experimental implementation layer.

[0044] In some optional embodiments, the quantum operation abstraction layer is specifically used for:

[0045] During the experiment registration phase: a list of available operations and their capability constraints are provided to the experiment implementation layer, including: the supported set of quantum gates, pulse templates, adjustable parameter ranges, and calibration labels; and verification of whether the experimental logic of the experiment implementation layer matches the available operations;

[0046] During the experimental design generation phase: verify whether the parameters involved in the experimental design are within the allowable range of operation;

[0047] In the experimental scheme implementation phase: the quantum experimental operations involved in the experimental scheme are instantiated so that the experimental implementation layer can map the experimental parameters into an operation call sequence;

[0048] During the experimental results presentation phase: In the process of processing the experimental results data returned by the quantum experimental device into structured visual results objects at the experimental implementation layer, help information for decoding / de-nesting / baseline calibration is provided.

[0049] In some optional embodiments, the message distribution layer includes:

[0050] The message dispatcher is used to forward various messages from the experimental implementation layer, experimental management layer, and communication protocol layer, and distributes them to the corresponding target layer according to the message type.

[0051] In some optional embodiments, the communication protocol layer includes:

[0052] The packet header encapsulation and parsing module is used to parse and deserialize the network binary data stream from the quantum experimental device before providing it to the message distribution layer; and to serialize and encapsulate the data from the information distribution layer before providing it to the connection management layer.

[0053] In some optional embodiments, the communication protocol layer further includes at least one of the following modules:

[0054] The packet splitting and reassembly module is used to split data from the information distribution layer that is longer than the length that a single data packet can carry into two or more segments so that they can be encapsulated into three or more data packets for transmission; and to perform packet splitting and reassembly processing on multiple data packets from quantum experimental devices to obtain complete data.

[0055] The verification module is used to perform magic number verification and length verification on the processed data.

[0056] In some optional embodiments, the connection management layer is used to manage communication connections, send and receive messages, perform user login and authentication operations, and synchronize the device status of the quantum experimental equipment, including:

[0057] The network connection management module is used to initialize a connection object based on the connection parameters of the quantum experimental device provided by the user application layer, and to initiate a communication connection request to the quantum experimental device to establish a communication connection with the quantum experimental device; the connection parameters include network address, communication port, username and password;

[0058] The message sending and receiving module is used to send a login request message to the quantum experimental device after the communication connection is established. The login request message includes identity credential information. After receiving the authentication success message with session identifier returned by the quantum experimental device after successful authentication, the module starts a heartbeat keep-alive thread to maintain the established communication connection and realize message sending and receiving with the quantum experimental device.

[0059] This invention provides a remote control device, including the aforementioned quantum computing experiment remote control system.

[0060] This invention provides a quantum experimental system, including: a quantum experimental device and the aforementioned remote control device;

[0061] Remote control devices are used to control quantum experimental equipment to conduct quantum experiments;

[0062] Quantum experimental equipment is used to perform quantum experiments and return the results.

[0063] The beneficial effects of the above-described technical solutions provided in the embodiments of the present invention include at least the following:

[0064] The quantum computing experiment remote control system provided in this invention includes a multi-layered architecture comprising a user application layer, an experiment management layer, an experiment implementation layer, an experiment abstraction layer, a quantum operation abstraction layer, and a connection management layer. The connection management layer establishes a communication connection with the quantum experiment equipment through a unified communication interface. The user application layer, experiment management layer, experiment implementation layer, experiment abstraction layer, and quantum operation abstraction layer work together to load corresponding experiment code templates for different experiment types, import relevant code blocks based on the templates, and instantiate parameter classes and experiment classes in the templates based on preset experiment base classes and parameter base classes. Users can configure various parameters used in the experiment based on the instantiated experiment and parameter instances, and generate experiment plans based on the user-configured parameters. This eliminates the need to develop separate control programs for each experiment type. Even technical personnel without programming experience can easily configure and generate experiment plans for the required experiment types, greatly reducing repetitive code development and system maintenance costs. The user application layer, experimental management layer, experimental implementation layer, experimental abstraction layer, and quantum operation abstraction layer work together to allow users to easily configure experimental parameters. The control system, based on executed commands, extracts the configured experimental parameters from the experimental plan, generates a structured parameter dictionary, adds connection parameters to the parameter dictionary, encapsulates it into a specified message format, and sends it to the quantum experimental device. It also parses the experimental result data dictionary returned by the quantum experimental device and displays the experimental results to the user. This satisfies the different parameter setting requirements of various quantum experiments, achieves unified management and compliance, and uses a unified encapsulation format for message interaction with the quantum experimental device, facilitating flexible handling of various types of interactive messages. Furthermore, it enables visual display of experimental results, improving the user experience.

[0065] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

[0066] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0067] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings:

[0068] Figure 1 This is a general framework diagram of the remote control system for quantum computing experiments in an embodiment of the present invention;

[0069] Figure 2This is a flowchart of the remote control method for quantum computing experiments in an embodiment of the present invention;

[0070] Figure 3 This is a flowchart illustrating the establishment of a communication connection with the quantum experimental device in an embodiment of the present invention;

[0071] Figure 4 This is a flowchart of the experimental registration and dynamic loading process in an embodiment of the present invention;

[0072] Figure 5 This is a flowchart of step S14 in an embodiment of the present invention, which sends an experimental control message to the sub-experimental device based on the execution instruction.

[0073] Figure 6 This is an example diagram of the life cycle state transition of a quantum experiment in an embodiment of the present invention.

[0074] Figure 7 This is a flowchart of message processing in an embodiment of the present invention.

[0075] Figure 8 This is a schematic diagram of the quantum experimental system in an embodiment of the present invention.

[0076] Explanation of reference numerals in the attached figures:

[0077] 10. Remote control device; 100. User application layer; 200. Experiment management layer; 300. Experiment implementation layer; 400. Experiment abstraction layer; 500. Quantum operation abstraction layer; 600. Message distribution layer; 700. Communication protocol layer; 800. Connection management layer; 900. Quantum experimental equipment;

[0078] 601. Device message processor; 602. Experiment message processor. Detailed Implementation

[0079] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0080] To address the existing problems in quantum computing experiments, this invention provides a modular architecture-based remote control system for quantum computing experiments. This system is used for communication and management of quantum experiment control, enabling unified experiment lifecycle management, an scalable experiment type registration mechanism, multi-level quantum operation abstraction (pulse layer, shim voltage control layer, quantum gate layer, circuit layer), asynchronous message-driven state management, and standardized experimental result processing.

[0081] The quantum computing experiment remote control system provided in this embodiment of the invention realizes the control of quantum experiment device 900 in a remote control device. The framework of the remote control system in the remote control device is described below. Figure 1 As shown, the core architecture adopts a multi-layered design, and the remote control system for quantum computing experiments includes:

[0082] User application layer 100 is used to realize interaction with users, including: obtaining connection-related parameters and experiment-related parameters provided by users, and displaying experiment results to users;

[0083] The experiment management layer 200 is used to implement management operations for quantum experiments, including: loading the corresponding experiment code template based on the experiment type provided by the user application layer 100; loading the code blocks involved in the experiment type into the experiment code template; instantiating the parameter class and experiment class in the template based on the experiment base class and parameter base class provided by the experiment abstraction layer 400, generating an experiment instance and a parameter instance as an interface for experiment parameter configuration, and providing them to the user application layer 100; and obtaining the experiment parameters configured by the user based on the experiment instance and parameter instance.

[0084] The experiment implementation layer 300 is used to generate an experiment plan based on the experiment parameters provided by the experiment management layer and the basic quantum experiment operations provided by the experiment abstraction layer 400; and to extract the configured experiment parameters from the experiment plan based on the execution instructions provided by the user application layer 100, generate a structured parameter dictionary, and add connection parameters to the parameter dictionary to obtain the experiment execution data.

[0085] Experimental abstraction layer 400 is used to provide the basic model and data specifications for quantum computing experiments, including experimental base class, parameter base class, result base class, and state machine definition;

[0086] Quantum Operation Abstraction Layer 500 is used to provide reusable basic operations for quantum experiments;

[0087] The connection management layer 800 is used to establish a communication connection with the quantum experimental device 900 based on the connection parameters provided by the user application layer 100; and to send experimental execution data packets of a specified format to the quantum experimental device 900, and to receive experimental result data packets from the quantum experimental device 900.

[0088] In some optional embodiments, the system further includes:

[0089] The message distribution layer 600 is used to distribute and process different types of messages, including sending experimental execution data to the communication protocol layer 700 and providing experimental result data to the user application layer 100 via the experimental implementation layer.

[0090] The communication protocol layer 700 is used to realize communication between the remote control device and the quantum experimental device 900, including message serialization and deserialization processing, data packet header encapsulation and parsing, data packet splitting and reassembly processing, data verification, and maintaining heartbeat keep-alive messages; including: encapsulating experimental execution data into experimental execution data packets of a specified format; parsing experimental result data packets and providing experimental result data to the message distribution layer.

[0091] The functions implemented by each layer are described in detail below.

[0092] (I) User Application Layer 100.

[0093] User application layer 100 is used to implement interaction with the user. See [link / reference] Figure 1 As shown, the user application layer 100 includes:

[0094] The parameter configuration module is used to obtain connection-related parameters and experiment-related parameters provided by the user.

[0095] The experimental results data display module is used to present experimental results to users.

[0096] Optionally, the user application layer 100 may also provide the following functions:

[0097] 1) Editing the experimental script.

[0098] The experiment script editing module allows users to edit experiment scripts, including editing the experiment code templates corresponding to the experiment type, enabling the addition, deletion, and modification of templates for easy subsequent use; and allowing users to edit various code blocks involved in various experiment types, enabling the addition, deletion, and modification of code blocks for easy subsequent use.

[0099] 2) Parameter configuration interface.

[0100] The parameter configuration interface enables human-computer interaction, including inputting or specifying the experiment type, as well as configuring and selecting experiment parameters, and other operations.

[0101] 3) Results presentation and analysis.

[0102] The results analysis module provides a results visualization and analysis tool to display experimental results to users, including numerical and process data, and spectral displays.

[0103] (II) Experimental Management Level 200.

[0104] The experimental management layer 200 is used to manage and operate quantum computing experiments. The experimental management layer 200 includes:

[0105] The experiment registration / deregistration module enables the registration and deregistration of experiment types. This module retrieves the user-specified experiment type via a registration function call; searches the experiment code template library based on the experiment type, retrieves and loads the corresponding experiment code template; and executes the experiment deregistration operation based on instructions from the user application layer 100 to release the communication connection with the quantum experiment device 900.

[0106] The experiment type mapping module is used to implement experiment type mapping. Based on the experiment type, it looks up the experiment code information mapping table to determine the code block involved in the experiment type; and obtains the parsing path of the code block, the class object code involved in the code block, and the parameter object code.

[0107] The dynamic class loading module is used to dynamically load code blocks and related class object code and parameter object code into the experimental code template based on the parsed path; based on the experimental base class and parameter base class provided by the experimental abstraction layer 400, it instantiates the parameter class and experimental class in the template, generates experimental instances and parameter instances as experimental parameter configuration interfaces and provides them to the user application layer 100; and obtains the experimental parameters configured by the user based on the experimental instances and parameter instances.

[0108] The message dispatcher registration module is used to register, bind, and save message processors based on the generated experimental and parameter instances.

[0109] The Experimental Management Layer 200 can provide the following lifecycle management functions.

[0110] The functionality implemented in this section can be found in the subsequent descriptions of the experiment registration and dynamic loading process.

[0111] (III) Experimental Implementation Layer 300.

[0112] The Experiment Implementation Layer 300 is used to implement various types of quantum experiments, including various experiment classes, their parameters, and result implementations. Experiment types include, but are not limited to, Rabi oscillations, T1 / T2 measurements, NMR signals, decoherence, quantum algorithms, and qubits. This layer is an algorithm / experiment library layer where executable experimental instances can be assembled using the quantum fundamental operations of the quantum operation abstraction layer, such as NMR signals, Rabi oscillations, qubit characterization, decoherence, and quantum algorithms. Parameterization, serialization, verification, and resource estimation are performed here, and deployable experimental instances can be formed at this layer.

[0113] During the experiment registration phase: Based on the basic model and data specifications provided by the experiment abstraction layer 400, the experiment management layer works together to complete the instantiation of the experiment class and parameter class;

[0114] In the experimental scheme generation phase: based on the experimental parameters provided by the experimental management layer 200, and using the basic quantum experimental operations provided by the experimental abstraction layer, experimental logic verification and derivation are performed to generate the experimental scheme.

[0115] In the experimental scheme implementation phase: Based on the execution instructions provided by the user application layer 100, the configured experimental parameters are extracted from the experimental scheme, the experimental parameters are mapped to the operation call sequence to obtain a structured parameter dictionary, and connection parameters are added to the parameter dictionary to obtain experimental execution data;

[0116] During the experimental results presentation phase: Based on the experimental information and results specifications provided by the experimental abstraction layer 400, the experimental results data returned by the quantum experimental device are processed into structured visual result objects and provided to the user application layer.

[0117] (iv) Experimental abstraction layer 400.

[0118] The Experiment Abstraction Layer 400 is the model description layer, which provides the basic model and data specifications for experiments, including experiment base classes, parameter base classes, result base classes, state machine definitions, etc. It defines the lifecycle, input and output fields, and state transitions of an experiment, enabling the solutions produced by the implementation layer to be understood and orchestrated by the upper-layer management / registration / distribution / result parsing modules.

[0119] The experimental abstraction layer 400 provides various base classes and state machines defined for the experimental implementation layer 300. The experimental implementation layer 300 can inherit and implement the various base classes and state machines defined in the experimental abstraction layer. The base classes include, but are not limited to, the experimental base class (Experiment), the parameter base class (ExperimentParameter), and the result base class (ExperimentResult). The state machine definition can include standardized state machine transition logic.

[0120] Experimental abstraction layer 400, specifically used for:

[0121] During the experiment registration phase: the experiment type and its parameters / results / state machines are provided to the experiment implementation layer 300. The registrable experiment descriptors have been output, including the type name, version, parameter mode, result mode, and state machine definition.

[0122] In the experimental scheme generation phase: Based on the parameter base class rules, the number of user input information is verified, and standardized parameter objects are generated and provided to the experimental implementation layer 300 and the experimental management layer 200 for parameter instantiation.

[0123] In the experimental scheme implementation phase: based on the real-time status messages returned by the quantum experimental device, the quantum experimental state is recorded and provided to the user application layer 100 for display through the experimental implementation layer;

[0124] During the experimental results presentation phase: provide experimental information and result specifications to the experimental implementation layer.

[0125] (v) Quantum operation abstraction layer 500.

[0126] The Quantum Operation Abstraction Layer 500 is a function library layer that provides reusable basic quantum operations, such as pulse sequences, quantum gates, gradient fields, quantum circuits, and custom gates. It shields the underlying hardware differences, outputting a unified set of composable operations and parameter constraints for upper layers to select and combine.

[0127] The Quantum Operation Abstraction Layer 500 provides three levels of abstraction: Pulse, Gate, and Circuit, supporting flexible mapping from low-level pulse sequences to high-level circuit designs. Each layer implements its corresponding function; for example, the Pulse layer defines parameters such as channel width and amplitude, directly controlling the hardware. The Gate layer automatically compiles quantum gates (such as H-gates and CNOT gates) into pulse sequences. The Circuit layer supports gate sequence arrangement and intelligent time slot allocation, avoiding qubit operation conflicts.

[0128] Quantum Operation Abstraction Layer 500 is specifically used for:

[0129] During the experiment registration phase: a list of available operations and their capability constraints are provided to the experiment implementation layer 300, including: the supported set of quantum gates, pulse templates, adjustable parameter ranges, and calibration labels; and verification of whether the experimental logic of the experiment implementation layer matches the available operations;

[0130] During the experimental design generation phase: verify whether the parameters involved in the experimental design are within the allowable range of operation;

[0131] In the experimental scheme implementation phase: the quantum experimental operations involved in the experimental scheme are instantiated so that the experimental implementation layer can map the experimental parameters into an operation call sequence;

[0132] During the experimental results presentation phase: In the process of processing the experimental results data returned by the quantum experimental device into a structured visual result object, the experimental implementation layer 300 provides help information for decoding / de-nesting / baseline calibration.

[0133] (vi) Message distribution layer 600.

[0134] A message dispatcher is configured in message distribution layer 600 to handle the distribution of different message types. It can determine the message type (device message or experiment message) based on an experiment type mapping table, and then distribute it to the appropriate layer for processing. The message dispatcher can distribute various messages forwarded by experiment implementation layer 300, experiment management layer 200, and communication protocol layer 700 to the corresponding target layer according to the message type.

[0135] (vii) Communication protocol layer 700.

[0136] Communication protocol layer 700 is used to realize communication between the remote control device and the quantum experimental device 900, based on a data description language protocol, such as the binary protocol of Protobuf. Communication protocol layer 700 includes:

[0137] The packet header encapsulation and parsing module is used to encapsulate messages to be sent to the quantum experimental device 900 before sending them, and to parse messages received from the quantum experimental device 900 before providing them to the message distribution layer 600 for distribution processing. This includes parsing and deserializing the network binary data stream from the quantum experimental device before providing it to the message distribution layer; and serializing and encapsulating the data from the information distribution layer before providing it to the connection management layer 800. Message serialization and deserialization can be implemented using binary encoding.

[0138] The communication protocol layer 700 also includes at least one of the following modules:

[0139] The packet splitting and reassembly module is used to split data from the message distribution layer 600 that is longer than the length of a single data packet into two or more segments, so that they can be encapsulated into three or more data packets for transmission. It also performs packet splitting and reassembly processing on multiple data packets from quantum experimental devices to obtain complete data. This module splits longer data into multiple packets for sequential transmission. For received messages, it performs packet splitting and reassembly processing, combining multiple data packets into a single complete message.

[0140] The verification module is used to perform magic number verification and length verification on the processed data.

[0141] The communication protocol layer can also implement a heartbeat keep-alive function. This is achieved by periodically sending heartbeat messages between the device and the quantum experimental device 900 to maintain their communication connection.

[0142] (viii) Connecting to the management level 800.

[0143] The connection management layer 800 is used to manage communication connections, send and receive messages, perform user login and authentication operations, and synchronize the device status of quantum experimental equipment, including:

[0144] The network connection management module is used to initialize a connection object based on the connection parameters of the quantum experimental device 900 provided by the user application layer 100, and initiate a communication connection request to the quantum experimental device 900 to establish a communication connection with it. The connection parameters include network address, communication port, username, and password. This module can manage the communication connection with the quantum experimental device 900, such as, but not limited to, a TCP connection.

[0145] The message sending and receiving module is used to send a login request message to the quantum experimental device 900 after the communication connection is established. This login request message includes identity credentials. Upon receiving a successful authentication message carrying a session identifier from the quantum experimental device 900, the module initiates a heartbeat keep-alive thread to maintain the established communication connection and to enable message sending and receiving with the quantum experimental device 900. This includes sending messages to the quantum experimental device 900 at the communication peer and receiving messages sent by the quantum experimental device 900.

[0146] The connection to the management layer also enables device status synchronization. It can periodically synchronize the device status of the quantum experiment device 900, achieving real-time monitoring of the quantum experiment's status.

[0147] The experimental implementation layer 300, experimental abstraction layer 400, and quantum operation abstraction layer 500 play crucial roles in the registration, experimental scheme generation, and experimental scheme execution phases of quantum computing experiments. Through the cooperation of these layers, corresponding experimental schemes can be generated and executed for different types of quantum experiments. The cooperation between these layers is described below for each phase.

[0148] (a) The experimental registration phase includes the definition phase, the registration phase, and the verification and information entry phase:

[0149] 1) Definition Phase

[0150] Experiment Abstraction Layer 400: Declare the experiment type and its parameters / results / state machines, such as, but not limited to, required parameters, value range, initial / running / completion states, etc.

[0151] Quantum Operation Abstraction Layer 500: Provides a list of available operations and their capability constraints, such as, but not limited to, the supported set of quantum gates, pulse templates, adjustable parameter ranges, calibration labels, etc.

[0152] Experiment Implementation Layer 300: Based on the parameter base model of the Experiment Abstraction Layer and the operation capabilities of the Quantum Operation Abstraction Layer, it binds a specific experiment constructor (implemented by the experiment class) and declares the set of dependent operations.

[0153] 2) Registration Phase

[0154] Experiment Abstraction Layer 400: Outputs registerable experiment descriptors, such as, but not limited to, type name, version, parameter mode, result mode, state machine definition, etc.

[0155] Experiment Implementation Layer 300: Binds the experiment descriptor to the specific implementation (factory / constructor pointer) and exposes the entry point for the generation scheme.

[0156] Quantum Operation Abstraction Layer 500: Provides capability declarations to the registration process to verify whether experimental implementations match available operations. Examples include, but are not limited to, hardware not supporting a certain pulse, gate registration failure, and errors in parsing custom gate content.

[0157] 3) Verification and information entry into the database

[0158] Static verification is completed based on the parameters / state machine definition of the experimental abstraction layer 400;

[0159] Feasibility is verified using the capabilities / constraints provided by the Quantum Operations Abstraction Layer 500;

[0160] The experimental implementation layer 300 confirms the availability of dependent operations through self-checking or rapid compilation.

[0161] Upon successful registration, the registration information will be displayed in the directory / index visible to the experimental management layer 200 and the message distribution layer 600.

[0162] (ii) The experimental registration phase includes the parameter receiving and verification phase, the scheme construction and compilation phase, the product and delivery phase, and the operation and result feedback phase:

[0163] 1) Parameter reception and verification

[0164] Experimental Abstraction Layer 400: Validate user input information according to the parameter base class rules, such as but not limited to type, range, required fields, etc., and generate standardized parameter objects.

[0165] Experimental Implementation Layer 300: Receives standardized parameters and performs secondary logic verification / derives default values ​​for quantum computing experiments, such as, but not limited to, scan step size, number of repetitions, etc.

[0166] Quantum Operation Abstraction Layer 500: Verifies whether experimental parameters fall within the allowed range of operation, such as, but not limited to, pulse amplitude, duration, frequency, etc.

[0167] 2) Solution Construction and Compilation

[0168] Experimental implementation layer 300: Maps standardized parameters to operation call sequences, such as, but not limited to, gate sequences / pulse sequences / measurement configurations; may contain control structures such as loop / scan / parallel.

[0169] Quantum Operation Abstraction Layer 500: Provides quantum operation instantiation and low-level constraint checking, and degrades high-order gates / circuits into executable pulse-level sequences, outputting a sequence of operations that can be sent out and related information, such as, but not limited to, timing, channel, amplitude, phase, measurement window, etc.

[0170] Experimental Abstraction Layer 400: Records the state flow of the scheme and defines the expected structure of the results for subsequent parsing. The state flow includes, but is not limited to, pending execution, running, completed, and failed states.

[0171] 3) Products and Delivery

[0172] Output object:

[0173] Executable experimental plans, such as but not limited to pulse-level / gate-level callable sequences + timing / resource allocation, etc., are derived from the collaboration between the quantum operation abstraction layer 500 and the experimental implementation layer 300.

[0174] Experimental information from the experimental abstraction layer 400, such as, but not limited to, experiment type, parameter instance, version, calibration label, state machine initial state, etc.

[0175] Results specifications from the experimental abstraction layer 400 are used for result parsing. These specifications include, but are not limited to, result fields, statistical methods, and error metrics.

[0176] These output objects are bound into experimental instances and handed over to the experimental management layer 200 → message distribution layer 600 → communication protocol layer 700 → connection management layer 800 → quantum experimental device 900.

[0177] 4) Execution and Result Feedback

[0178] The quantum experimental device 900 returns the original measurement data after performing a quantum experiment.

[0179] The quantum operation abstraction layer 500 can provide assistance with decoding / de-nesting / baseline calibration, such as, but not limited to, measurement mapping, IQ demodulation, etc.

[0180] The experimental implementation layer 300 processes the raw measurement data into structured result objects;

[0181] The experimental abstraction layer 400 completes the state transition and result structuring based on the result specifications and state machine. Through the experimental implementation layer and experimental management layer, it returns the results to the user application layer 100 for result analysis and display.

[0182] In the implementation of the aforementioned quantum experiment, the experimental abstraction layer 400 defines the specification implementation layer assembly scheme, and the quantum operation abstraction layer 500 provides executable operations. The experimental abstraction layer 400, the quantum operation abstraction layer 500, and the experimental implementation layer 300 work together to form a closed loop that is registerable, programmable, deployable, and resolvable. Upwards, the stable interface (type, parameters, results, and status) of the experimental abstraction layer is exposed to the user application layer and the experimental management layer; downwards, the physical instructions compiled by the quantum operation abstraction layer are exposed to the quantum experimental device 900. The experimental implementation layer 300 acts as the glue, producing an experimental scheme that satisfies both business logic and can be implemented in hardware, based on the specifications of the experimental abstraction layer 400 and the operations of the quantum operation abstraction layer 500.

[0183] Based on the aforementioned remote control system architecture, remote management of the quantum experimental device 900 is achieved, including establishing network connections and authentication, dynamic registration of experimental types and configuration of structural parameters, submission of experimental tasks and management of task queues, execution and status monitoring of quantum experiments, acquisition and analysis of experimental results, resource deregistration and connection release after the experiment is completed, etc.

[0184] This invention provides a remote control method for quantum computing experiments, implemented based on the above-described system architecture, and its process is as follows: Figure 2 As shown, it includes the following steps:

[0185] S11: Establish a communication connection with the quantum experimental device 900 based on the connection parameters provided by the user.

[0186] S12: Based on the experiment type specified by the user, load the corresponding experiment code template, load the code blocks related to the experiment type into the experiment code template, and based on the preset experiment base class and parameter base class, instantiate the parameter class and experiment class in the template, generate an experiment instance and a parameter instance as an experiment parameter configuration interface and provide it to the user.

[0187] S13: Obtain the experimental parameters configured by the user based on the experimental instance and parameter instance, and generate an experimental plan based on the experimental parameters.

[0188] S14: Based on the user's execution instructions, extract the configured experimental parameters from the experimental scheme, generate a structured parameter dictionary, add connection parameters to the parameter dictionary, encapsulate it into a specified message format, and send it to the quantum experimental device 900.

[0189] S15: After parsing the experimental result data dictionary returned by the quantum experimental device 900, the experimental result data is displayed to the user.

[0190] Step S11 above establishes a secure connection and authenticates the user with the quantum experimental device 900, enabling subsequent quantum experimental operations. The process of establishing a communication connection with the quantum experimental device based on user-provided connection parameters is described in [link to documentation]. Figure 3 As shown, it includes:

[0191] S101: Obtain the connection parameters of the quantum experimental device 900 provided by the user through the human-computer interaction interface.

[0192] The user application layer 100 provides a human-computer interaction interface to the user, through which the user inputs the connection parameters of the target quantum experimental device 900 to perform the quantum computing experiment. These connection parameters include, but are not limited to, a network address, communication port, username, and password. The network address can be, for example, an IP address.

[0193] S102: Initialize a connection object based on the connection parameters, and initiate a communication connection request to the quantum experimental device 900 to establish a communication connection with the quantum experimental device 900.

[0194] Establishing a communication connection with the quantum experimental device 900 via the connection management layer 800 can be a secure TCP connection. When the connection management layer 800 establishes a communication connection, it typically requires the cooperation of the message distribution layer 600 and the communication protocol layer 700.

[0195] S103: After the communication connection is established, a login request message is sent to the quantum experimental device 900. The login request message includes identity credential information.

[0196] The remote control system in the remote control device initiates a login authentication process to the quantum experimental device 900. That is, it sends a login request message containing identity credentials to the quantum experimental device 900, requesting the quantum experimental device 900 to authenticate the identity of the experimental requester. If the authentication is successful, the quantum experimental device 900 returns an authentication success message to the remote control device. The authentication success message can carry authentication success information and a unique session identifier.

[0197] S104: After receiving the authentication success message carrying the session identifier returned after the successful authentication of the quantum experimental device 900, start the heartbeat keep-alive thread to maintain the established communication connection.

[0198] After receiving the authentication success message returned by the quantum experimental device 900, the remote control device maintains the communication connection with the quantum experimental device 900 based on the authentication identifier carried therein, and starts an independent heartbeat keep-alive thread to maintain the long-term stability of the communication connection, which signifies that the user identity authentication is successful and a secure communication session has been established.

[0199] Step S12 above registers and dynamically loads quantum computing experiments. It automatically generates corresponding experiment instances and parameter instances based on the type of quantum computing experiment the user wants to conduct, allowing the user to configure the experiment parameters. See [link to quantum computing experiment registration and dynamic loading process] for details. Figure 4 As shown. Involves Figure 1 The interaction between the user application layer 100 and the experimental management layer 200 in the system framework shown.

[0200] S201: Call the registration function for the quantum experiment.

[0201] The registration function for quantum experiments can be called to initiate the registration process for quantum computing experiments. Before executing the registration function, users should consult the documentation to obtain the supported experiment types and then call the registration function with the experiment type as a parameter. Experiment registration and deregistration can be implemented through the experiment management layer.

[0202] S202: Obtain the experiment type specified by the user by calling the registration function.

[0203] The user-specified experiment type is obtained through the registration function invoked by the user. Experiment types include, but are not limited to, Rabi oscillation, T1 / T2 measurement, NMR signal, decoherence, quantum algorithm, and qubit.

[0204] S203: Based on the experiment type, locate the experiment code template library, obtain the corresponding experiment code template, and load it;

[0205] After the remote control system obtains the experiment type specified by the user, it searches for the corresponding experiment code template in its internally stored experiment code library. This template serves as a basic framework upon which code related to the experiment can be loaded to generate the corresponding experiment plan. Users can add, modify, and delete experiment code templates from the template library through the experiment script writing module in the user application layer.

[0206] S204: Based on the experiment type, locate the experiment code information mapping table to determine the code blocks involved in the experiment type.

[0207] After loading the experimental code template, the required code can be imported into it. The code repository stores various code blocks related to quantum computing experiments. Each code block corresponds to implementing at least one quantum experimental operation, including, but not limited to, pulse sequences, quantum gates, gradient lengths, custom gates, quantum circuits, etc. Pre-edited quantum experimental operation code blocks can be stored in the code repository, and an experimental code information mapping table can be established, including the correspondence between experiment types and the involved code blocks. When a quantum experiment is needed, the relevant code blocks can be directly loaded without repeated development. Stored code blocks can be updated, modified, and deleted.

[0208] See Figure 1 The experiment type mapping module in the experiment management layer can look up the experiment code information mapping table based on the experiment type to determine the code blocks involved in the experiment type. The experiment management layer 200 uses the experiment code information mapping table to achieve dynamic code loading, thereby enabling plug-in extensions that support experiment types.

[0209] S205: Obtain the parsing path of the code block, the class object code involved in the code block, and the parameter object code.

[0210] After determining the code blocks involved in the experiment type, the parsing paths of these code blocks are further obtained. Different code blocks may target different class objects and parameter objects. The code for class objects and parameter objects can also be stored in the code repository for loading and use. Similarly, the stored class object code and parameter object code can be updated, modified, and deleted.

[0211] S206: Based on the parsing path, dynamically load code blocks, along with the related class object code and parameter object code, into the experimental code template.

[0212] See Figure 4 The dynamic code import step involves importing code blocks, along with the class object code and parameter object code involved in those blocks, into the corresponding locations in the experimental code template. The specific order and position of the code blocks in the experimental code template can be determined based on the experimental logic. Class objects can be obtained through reflection in this step.

[0213] The above steps S204-S206 implement loading the corresponding experiment code template according to the experiment type specified by the user, and loading the code blocks related to the experiment type into the experiment code template.

[0214] S207: Based on a preset experiment base class, instantiate the experiment class in the template to generate an experiment instance containing the experiment logic. When creating an experiment instance, a unique instance ID can be generated, the experiment type can be set, the experiment status can be initialized, the creation time can be recorded, etc.

[0215] S208: Based on the preset parameter base class, instantiate the parameter class in the template to generate a parameter instance that serves as the interface for configuring experimental parameters.

[0216] After importing the code into the experimental code template, two core objects need to be instantiated: an experimental instance and a parameter instance. Steps S207 and 208 above implement the experimental instance and parameter instance respectively; the execution order of these two steps is not important. The experimental instance contains the entire experimental logic, while the experimental parameter instance provides a structured interface for configuring experimental parameters.

[0217] The above S204-208 is a dynamic class loading process, which can be jointly implemented by the experimental management layer 200, the experimental implementation layer 300, the experimental abstraction layer 400, and the quantum operation abstraction layer 500.

[0218] S209: Register and bind message handlers based on the generated experimental and parameter instances.

[0219] The remote control system will register and bind specific message handling functions for this experiment to correctly parse various asynchronous messages received subsequently. Different message handling functions will process different types of messages.

[0220] S210: Save the registered information.

[0221] S211: Provide the generated experimental and parameter instances to the user.

[0222] S212: The user configures experimental parameters based on experimental instances and parameter instances. This step enables the configuration of structured parameters, and optionally, parameter verification can also be implemented.

[0223] Users set all necessary experimental parameters for the experiment using the obtained experimental parameter instances. These parameters constitute the complete configuration scheme of the experiment, including, but not limited to, physical parameters, process control parameters, and pulse sequences. Physical parameters include, but are not limited to, atomic resonance frequencies and pulse amplitude control parameters. Process control parameters include, but are not limited to, whether to generate pseudo-pure states, sampling paths, and sampling parameter selection. Pulse sequences include, but are not limited to, a series of user-defined pulse objects, each containing attributes such as detuning, pulse width, amplitude, and phase.

[0224] Optionally, during the entire parameter configuration process, the data verification model built into the remote control system (such as Pydantic) will automatically perform validity checks when parameters are assigned values, ensuring that all input parameters comply with predefined business rules and physical constraints, thereby guaranteeing the accuracy and reliability of the experimental configuration from the source.

[0225] Data validation can be implemented in the experiment implementation layer 300. If the experiment implementation layer 300 detects an error in the parameter configuration, it will report an error before the experiment runs and will not continue to transmit subsequent related messages. Users can constrain the range of parameters using the pydantic model when creating new experiment instances and experiment parameter instances.

[0226] S213: After configuring the experimental parameters, the user submits the experiment.

[0227] After an experiment is submitted, it can be sent to a quantum experimental device for execution. The process described above, from experiment registration to submission, is applicable to various types of quantum experiments. The code blocks involved in the quantum experiment can be loaded at runtime without prior import. A mapping table can decouple the experiment type from its implementation. Plug-in extensions support adding new experiment types without modifying the core code. Automatic registration of message handlers avoids manual operation and configuration, improving automation, and a unified experiment interface ensures consistency and universality.

[0228] S214: Generate an experimental plan based on the user-configured experimental parameters and execute the experimental procedure. After the experimental procedure is completed, the experimental results can be returned to the user. This step is not included in step S12 above. Step S214 includes the relevant content of subsequent steps S13, S14, and S15.

[0229] In step S13 above, the experimental parameters configured by the user based on the experimental instance and parameter instance are obtained, and an experimental plan is generated based on the experimental parameters.

[0230] In step S14 above, based on the user's execution instructions, the configured experimental parameters are extracted from the experimental scheme, a structured parameter dictionary is generated, connection parameters are added to the parameter dictionary, and the message is encapsulated into a specified message format and sent to the quantum experimental device 900. This process is described in [reference needed]. Figure 5 As shown, it includes:

[0231] S401: After receiving the user's execution command, extract the configured experimental parameters from the experimental parameter instance and assemble the extracted experimental parameters into a structured parameter dictionary.

[0232] After the experimental parameters are configured, the user issues an execution command. The remote control system first extracts and assembles all configured parameters from the experimental parameter instance to form a structured parameter dictionary. These configured parameters include, but are not limited to, physical parameters, process control parameters, and pulse sequences. Based on these parameters, the quantum experimental device 900 can be controlled to complete the experiment. This step can be implemented through the experimental management layer 200 and the experimental implementation layer 300.

[0233] S402: After adding device identifiers and user account information to the parameter dictionary, serialize the parameter dictionary into a string of the specified format.

[0234] This step, serializing the structural parameters, can be accomplished through the message distribution layer. To ensure accurate distribution to the target quantum experimental device 900, device identification information, login account passwords, and other details need to be added. The entire parameter dictionary is then serialized into a standard JSON string, which is distributed to the communication protocol layer by the message dispatcher of the message distribution layer.

[0235] S403: Encapsulate the string into a binary protocol buffer message format and send it to the quantum experimental device 900 through the established communication connection.

[0236] At the communication protocol layer 700, the message header is encapsulated, and the serialized string is packaged into a binary protocol buffer message format, which is the data packet format that can be sent. Optionally, if the string is long, it can be split into multiple packets for sequential transmission. Using the established communication connection, the message is sent to the quantum experimental device 900 through the message sending and receiving function of the connection management layer 800.

[0237] After receiving the execution message for the quantum computing experiment, the quantum experimental device 900 adds the quantum computing experiment to be executed to the task queue and schedules it for execution in sequence.

[0238] In some optional embodiments, the above method further includes:

[0239] S16: Wait for the quantum experimental device 900 to execute the quantum computing experiment and monitor the execution status of the quantum experimental device 900 until the experiment is completed. Generate an experimental progress view based on the experimental status of the quantum experimental device 900. This step can be performed periodically after S14 and before S15. The process of monitoring the execution status includes: receiving real-time status messages sent by the quantum experimental device 900, wherein the real-time status messages include the experimental status of the quantum experimental device 900, and the experimental status includes at least one of pending execution, executing, completed, and failed;

[0240] After the experiment is submitted, the remote control system enters a blocked waiting state until the experiment is completed. During this process, the remote control system continuously polls the status and asynchronously receives and processes various real-time messages from the quantum experimental device 900. Based on these real-time messages, the system obtains the experimental progress and status of the quantum experimental device 900, enabling real-time monitoring of the execution state transitions of the quantum experiment.

[0241] The experiment follows a defined state transition sequence, from "pending execution" to "in execution," and finally to "complete" or "failed." Simultaneously, the remote control system processes various types of update messages, such as step change messages, real-time data update messages, and chart data messages, which together provide a complete view of the experiment's progress. When the experiment finally transitions to "complete" or "failed," the waiting loop ends.

[0242] The execution state of a quantum experiment is part of its lifecycle, and the state transitions within the lifecycle of a quantum experiment can be referenced. Figure 6 As shown.

[0243] After the remote control system is started, the quantum experiment is in an unregistered state. Once the quantum experiment registration and dynamic class loading are completed, the experimental plan is generated and submitted to the quantum experimental device 900, entering the device's task queue, the quantum experiment is in a pending execution state. After the quantum experimental device 900 runs the quantum experiment, it sequentially goes through initialization, execution steps 1, 2, ... N, and remains in the execution state until completion. After the quantum experimental device 900 completes the experiment, it collects the experimental results, including graphs, and sends a completion message to the remote control system, at which point the experiment status changes to "Experiment Completed." The experiment can be cancelled after completion. If the experiment terminates before completion, it can also be cancelled, and the experiment status changes to "Experiment Failed."

[0244] Step S15 above involves parsing the experimental result data dictionary returned by the quantum experimental device 900 and then displaying the experimental result data to the user. This includes: parsing the experimental result data dictionary returned by the quantum experimental device 900, extracting the experimental metadata and experimental result data segments from the data result dictionary, and displaying the experimental metadata and corresponding experimental results to the user.

[0245] This step enables the acquisition and display of results. After a successful quantum experiment, the user can request the results. Upon receiving the experimental result data from the quantum experiment device 900, the remote control system extracts the structured result data dictionary and parses it. The result data dictionary contains not only meta-information about the experiment, such as unique identifiers, names, states, and timestamps, but also a dedicated experimental result data segment. This segment encapsulates both the raw and processed results of the experiment. The processed results include, but are not limited to, the real, imaginary, and magnitude values ​​of the signal, as well as arrays of chart data points directly used for visualization. Users can then perform further data analysis and visualization.

[0246] In some optional embodiments, the above method further includes:

[0247] S17: After the quantum computing experiment is completed, perform the experiment cancellation operation and release the communication connection between the experiment and the quantum experimental equipment.

[0248] This step involves deregistering experimental resources and releasing connections. After the entire experiment is completed, the user initiates a resource cleanup operation. The remote control system first performs experiment deregistration, clearing local references to the experimental instance and sending a notification to the quantum experimental device 900. Subsequently, the remote control system executes the connection disconnection process: sending a logout message, stopping the heartbeat keep-alive thread, and finally closing the underlying TCP network connection, releasing all related system resources.

[0249] The aforementioned remote control method for quantum computing experiments can achieve full-process management of quantum experiments, including connection authentication, experiment registration, parameter configuration, experiment submission, status monitoring, result acquisition, and resource release. It can be implemented using... Figure 1 The multi-layered architecture shown is implemented through a user application layer 100, an experiment management layer 200, an experiment abstraction layer 400, an experiment implementation layer 300, a quantum operation abstraction layer 500, a message distribution layer 600, a communication protocol layer 700, and a connection management layer 800. Through the cooperation between these layers, automatic configuration, automatic scheme generation, automatic execution, and automatic acquisition and display of results for various types of quantum experiments are achieved.

[0250] The above methods can be referenced for implementing various message processing procedures. Figure 7 As shown, the pulse control system and signal sampling system of the quantum experimental device can realize pulse control and signal sampling during the quantum experiment process, and send experimental results and status data to the remote control device.

[0251] The binary stream in the network is processed through the communication protocol layer 700. Specifically, after receiving information through the TCP connection with the quantum experimental device 900, header parsing, magic number verification, and length verification are performed. Packet splitting and reassembly are then performed to obtain the complete message. After protobuf parsing, the message is provided to the message distribution layer 600. The message processors in the message distribution layer 600 query the experiment type mapping table and distribute the message to the appropriate processor based on whether it is a device message or an experimental message. Device messages include, but are not limited to, device status updates, lock field data updates, parameter updates, and queue updates. Device messages are distributed to device message processor 601, while experimental messages, including experiment additions, experiment starts, function processing, and experiment data updates, are distributed to experiment message processor 602. The above message processing flow is applicable to the distribution of various messages involved in the above method.

[0252] This invention also provides a remote control device, including the aforementioned quantum computing experiment remote control system.

[0253] This invention also provides a quantum experimental system, the structure of which is as follows: Figure 8 As shown, it includes a quantum experimental device 900 and the aforementioned remote control device 10.

[0254] The remote control device 10 is used to control the quantum experimental equipment to conduct quantum experiments;

[0255] The Quantum Experiment Device 900 is used to perform quantum experiments and return the results.

[0256] The above method enables a dynamic loading mechanism and modular extensibility for experiments: An experiment type mapping table (such as EXPERIMENT_TYPE_MAP) associates experiment types with corresponding experiment code templates, as well as the parsing path, class name, and parameter class names of the code blocks to be loaded. At runtime, code blocks are dynamically imported into the templates, then classes are instantiated and message handlers are registered, achieving decoupling of experiment types and plug-in-like extensibility. Adding new experiments requires no modification to the core code, reducing maintenance costs.

[0257] The above method uses a message-driven state machine to monitor the experimental status. Experimental status transitions (including pending, in progress, completed / failed) are triggered by asynchronous messages. For example, the experiment start message updates the status to "in progress," and the completion message updates it to "completed." Furthermore, it can acquire real-time data updates, step changes, and other messages. This allows for real-time monitoring of the experiment's progress and status, enabling timely processing of tasks.

[0258] The above method can achieve multi-level abstraction of quantum operations, thus adapting to various types of experiments and different application scenarios. Users can select the operation level based on their needs, and the system can automatically abstract and generate experimental plans.

[0259] The above-mentioned communication method has the advantage of high reliability: it ensures the integrity of large data transmission through packet splicing / merging processing mechanism and reduces the risk of disconnection through heartbeat keep-alive mechanism.

[0260] The above method performs type checking at compile time and combines it with runtime verification to avoid invalid parameters being submitted to quantum experimental devices, and ensures parameter security and real-time performance, thereby improving the success rate of experiments.

[0261] The above methods are highly efficient in resource utilization, reduce memory usage through dynamic loading, reduce blocking through asynchronous message processing, and support high-concurrency experimental queue management.

[0262] Unless otherwise specifically stated, terms such as processing, calculation, operation, determination, display, etc., may refer to the actions and / or processes of one or more processing or computing systems or similar devices that represent the manipulation and conversion of data representing physical (e.g., electronic) quantities within the registers or memory of the processing system into other data similarly representing physical quantities within the memory, registers, or other such information storage, transmission, or display devices of the processing system. Information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0263] It should be understood that the specific order or hierarchy of steps in the disclosed process is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process may be rearranged without departing from the scope of this disclosure. The appended method claims provide elements of various steps in an exemplary order and are not intended to limit the scope to the specific order or hierarchy described.

[0264] In the detailed description above, various features are combined together in a single embodiment to simplify this disclosure. This approach to disclosure should not be construed as reflecting an intention that embodiments of the claimed subject matter require more features than are explicitly stated in each claim. Rather, as reflected in the appended claims, the invention is presented with fewer features than all of the features in a single disclosed embodiment. Therefore, the appended claims are hereby explicitly incorporated into the detailed description, with each claim representing a separate preferred embodiment of the invention.

[0265] Those skilled in the art will also understand that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments herein can be implemented as electronic hardware, computer software, or a combination thereof. To clearly illustrate the interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps described above are generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in alternative ways for each specific application; however, such implementation decisions should not be construed as departing from the scope of this disclosure.

[0266] The steps of the methods or algorithms described in conjunction with the embodiments herein can be directly embodied in hardware, software modules executed by a processor, or a combination thereof. The software modules can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is connected to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user terminal. Alternatively, the processor and storage medium can exist as discrete components in the user terminal.

[0267] For software implementation, the techniques described in this application can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described in this application. This software code can be stored in memory units and executed by a processor. The memory units can be implemented within the processor or outside the processor; in the latter case, they are communicatively coupled to the processor via various means, as is well known in the art.

[0268] The foregoing description includes examples of one or more embodiments. It is certainly impossible to describe all possible combinations of components or methods in order to describe the above embodiments, but those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. Therefore, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. Furthermore, the term "comprising" as used in the specification or claims is interpreted in a manner similar to the term "including," as interpreted when used as a conjunction in the claims. Additionally, the use of any term "or" in the specification of the claims is intended to mean "non-exclusive or."

Claims

1. A quantum computing experiment remote control system, characterized by, include: The user application layer is used to implement interaction with users, including: obtaining connection-related parameters and experiment-related parameters provided by users, and displaying experiment results to users; The experiment management layer is used to manage quantum experiments, including: loading the corresponding experiment code template based on the experiment type provided by the user application layer; loading the code blocks related to the experiment type into the experiment code template; instantiating the parameter class and experiment class in the template based on the experiment base class and parameter base class provided by the experiment abstraction layer, generating an experiment instance and a parameter instance as an interface for experiment parameter configuration, and providing them to the user application layer; and obtaining the experiment parameters configured by the user based on the experiment instance and parameter instance. The experiment implementation layer is used to generate an experiment plan based on the experimental parameters provided by the experiment management layer and the basic quantum experiment operations provided by the experiment abstraction layer; and to extract the configured experimental parameters from the experiment plan based on the execution instructions provided by the user application layer, generate a structured parameter dictionary, add connection parameters to the parameter dictionary, and obtain the experiment execution data. The experimental abstraction layer provides the basic model and data specifications for quantum computing experiments, including experimental base classes, parameter base classes, result base classes, and state machine definitions. A quantum operation abstraction layer is used to provide reusable basic operations for quantum experiments; The connection management layer is used to establish a communication connection with the quantum experimental device based on the connection parameters provided by the user application layer; and to send experimental execution data packets in a specified format to the quantum experimental device, and to receive experimental result data packets from the quantum experimental device.

2. The system as described in claim 1, characterized in that, Also includes: The message distribution layer is used to distribute and process different types of messages, including sending experiment execution data to the communication protocol layer. The experimental results data are provided to the user application layer through the experimental implementation layer. The communication protocol layer is used to realize communication between remote control devices and quantum experimental devices, including message serialization and deserialization, packet header encapsulation and parsing, data packet splitting and reassembly, data verification, and maintaining heartbeat keep-alive messages; including: encapsulating experimental execution data into experimental execution data packets of a specified format; Parse the experimental result data packet and provide the experimental result data to the message distribution layer.

3. The system as described in claim 1, characterized in that, The user application layer includes: The parameter configuration module is used to obtain connection-related parameters and experiment-related parameters provided by the user. The experimental results data display module is used to present experimental results to users.

4. The system as described in claim 1, characterized in that, The experimental management layer includes: The experiment registration / deregistration module is used to obtain the experiment type specified by the user through the registration function; according to the experiment type, search the experiment code template library, obtain the corresponding experiment code template and load it; and execute the experiment deregistration operation based on the user application layer instructions to release the communication connection with the quantum experiment device. The experiment type mapping module is used to look up the experiment code information mapping table according to the experiment type, determine the code block involved in the experiment type, and obtain the parsing path of the code block, the class object code and parameter object code involved in the code block; The dynamic class loading module is used to dynamically load code blocks, along with the related class object code and parameter object code, into the experimental code template based on the parsed path; based on the experimental base class and parameter base class provided by the experimental abstraction layer, it instantiates the parameter class and experimental class in the template, generates experimental instances and parameter instances as experimental parameter configuration interfaces, and provides them to the user application layer; and it obtains the experimental parameters configured by the user based on the experimental instances and parameter instances. The message dispatcher registration module is used to register, bind, and save message processors based on the generated experimental and parameter instances.

5. The system as described in claim 1, characterized in that, The experimental implementation layer is used to implement various types of quantum experiments; During the experiment registration phase: Based on the basic model and data specifications provided by the experiment abstraction layer, the experiment management layer works together to complete the instantiation of experiment classes and parameter classes; In the experimental scheme generation phase: based on the experimental parameters provided by the experimental management layer, and using the basic quantum experimental operations provided by the experimental abstraction layer, experimental logic verification and derivation are performed to generate the experimental scheme. In the experimental scheme implementation phase: Based on the execution instructions provided by the user application layer, the configured experimental parameters are extracted from the experimental scheme, the experimental parameters are mapped to the operation call sequence to obtain a structured parameter dictionary, and connection parameters are added to the parameter dictionary to obtain experimental execution data; During the experimental results presentation phase: Based on the experimental information and results specifications provided by the experimental abstraction layer, the experimental results data returned by the quantum experimental equipment are processed into structured visual result objects and provided to the user application layer.

6. The system as described in claim 1, characterized in that, The experimental abstraction layer is specifically used for: During the experiment registration phase: the experiment type and its parameters / results / state machines are provided to the experiment implementation layer, and the registrable experiment descriptors are output. The experiment descriptors include type name, version, parameter mode, result mode, and state machine definition. In the experimental scheme generation phase: Based on the parameter base class rules, the number of user input information is verified, and standardized parameter objects are generated and provided to the experimental implementation layer and experimental management layer for parameter instantiation. In the experimental scheme implementation phase: based on the real-time status messages returned by the quantum experimental device, the quantum experimental state is recorded and provided to the user application layer for display through the experimental implementation layer; During the experimental results presentation phase: provide experimental information and result specifications to the experimental implementation layer.

7. The system as described in claim 1, characterized in that, The quantum operation abstraction layer is specifically used for: During the experiment registration phase: a list of available operations and their capability constraints are provided to the experiment implementation layer, including: the supported set of quantum gates, pulse templates, adjustable parameter ranges, and calibration labels; and verification of whether the experimental logic of the experiment implementation layer matches the available operations; During the experimental design generation phase: verify whether the parameters involved in the experimental design are within the allowable range of operation; In the experimental scheme implementation phase: the quantum experimental operations involved in the experimental scheme are instantiated so that the experimental implementation layer can map the experimental parameters into an operation call sequence; During the experimental results presentation phase: In the process of processing the experimental results data returned by the quantum experimental device into structured visual results objects at the experimental implementation layer, help information for decoding / de-nesting / baseline calibration is provided.

8. The system as described in claim 1, characterized in that, The message distribution layer includes: The message dispatcher is used to forward various messages from the experimental implementation layer, experimental management layer, and communication protocol layer, and distributes them to the corresponding target layer according to the message type.

9. The system as described in claim 1, characterized in that, The communication protocol layer includes: The packet header encapsulation and parsing module is used to parse and deserialize the network binary data stream from the quantum experimental device before providing it to the message distribution layer; and to serialize and encapsulate the data from the information distribution layer before providing it to the connection management layer.

10. The system as described in claim 9, characterized in that, The communication protocol layer further includes at least one of the following modules: The packet splitting and reassembly module is used to split data from the information distribution layer that is longer than the length that a single data packet can carry into two or more segments so that they can be encapsulated into three or more data packets for transmission; and to perform packet splitting and reassembly processing on multiple data packets from quantum experimental devices to obtain complete data. The verification module is used to perform magic number verification and length verification on the processed data.

11. The system as claimed in claim 1, characterized in that, The connection management layer is used to manage communication connections, send and receive messages, perform user login and authentication operations, and synchronize the device status of quantum experimental equipment, including: The network connection management module is used to initialize a connection object based on the connection parameters of the quantum experimental device provided by the user application layer, and to initiate a communication connection request to the quantum experimental device to establish a communication connection with the quantum experimental device; the connection parameters include network address, communication port, username and password; The message sending and receiving module is used to send a login request message to the quantum experimental device after the communication connection is established. The login request message includes identity credential information. After receiving the authentication success message with session identifier returned by the quantum experimental device after successful authentication, the module starts a heartbeat keep-alive thread to maintain the established communication connection and realize message sending and receiving with the quantum experimental device.

12. A remote control device, characterized in that, include: The quantum computing experiment remote control system as described in any one of claims 1-11.

13. A quantum experimental system, characterized in that, include: Quantum experimental apparatus and the remote control device as described in claim 12; Remote control devices are used to control quantum experimental equipment to conduct quantum experiments; Quantum experimental equipment is used to perform quantum experiments and return the results.

Images